Table transformer issue with column data

[Nenad Ristevski]

Dears,

I stuck with issue after applying Table Transformer macro to my table. Actually, I am using Table Toolbox macro in order to nest a few macros. Also, using Table Excerpt Include macro to parse a table from Jira issue macro.

So, here how it looks like without Table Transformer:

You can see column Vendor is populated and data is shown properly after it is published.

Also, view from Pivot Table looks good:

But, after applying Table Transformer macro, column Vandor is empty:

This all worked till yesterday and disappeared for some reason.

Maybe I am missing something, so need your help to figure out how to overcome this situation.

Thanks.

[Stiltsoft support · Accepted solution]

Hi @Nenad Ristevski ,

As you are talking about the Table Filter, Charts & Spreadsheets for Confluence app, it is better to refer to our support portal directly. The portal is confidential, so you'll be able to share more data for further investigation.

Meanwhile, I see that you have two Vendor columns in your table. One is populated, the other is empty. 

The Table Transformer macro treats source tables as mini databases, and you can't have several columns with the same name in a database. 

So, go to the original table (tables) that is wrapped in the Table Excerpt macro and rename your columns as Vendor 1 and Vendor 2. Then the macro will work as expected.

[Nenad Ristevski]

Hi,

The issue is also with that "double" column Vendor. You know that there is no option in Jira issue macro to select one column twice, so I find this as some kind of a bug.

Nevertheless, I am going to raise a ticket on your support portal.

Thanks.

[Stiltsoft support]

When referring to the portal, please take screenshots of the macro previews and the source tables.

I mean if your source table is a Jira output but you reuse it with the help of the Table Excerpt/ Table Excerpt Include macros, maybe you somehow transform this Jira output beforehand.

So, we need to see each step (starting with a "pure" Jira output without any macros - sometimes there can be several custom fields with the same name) to see where the extra column comes from.