Reporting Table Component Loses Formatting When Data Key is Changed

Hi there, I am looking for tips on how to handle a tedious problem I repeatedly encounter with the Table Component in Ignition Reporting. The problem is that when changing the Data Key property of the Table, it erases all the cell formatting (Font, Text Color, Fill Color, Border, etc)

I first Select a Data Key and then I format the cells of the table to appear as shown below.

Then after changing the Data Key, the Table Component loses all its formatting and returns to its default which makes things unnecessarily tedious. It is as if the formatting belongs solely to that selected Data Key, so replacing erases all.

Anyway, does anyone have any tips to make this process easier? Is it just a missing feature in Ignition Reporting? Or maybe I'm just altering the Data Key the wrong way?

The reports I have to make lately often re-use this table but for different data keys to display. So it would be nice if I could simply copy paste the table with all its formatting and then swap out the Data Key to make it display different rows of data without having to repeatedly do all the format changes.

Any thoughts are appreciated!

Just going by memory here, but I found that when you type in the new Data Key, either you press key or you use your mouse to click on the table itself and that keeps all your formatting and simply changes the Data Key. I think it erases when you press and then click on the table. Annoying...I know. Luckily you can also Undo if the format disappears and it will bring back the formats and keep your new Data Key.

1 Like

I see, thanks! Pressing Ctrl-Z or "Undo" after the formatting disappears seems to do the trick while keeping the new Data Key. I don't know why I didn't think to try that.
Still kinda funky that that is what I have to do.
If there is a better way to handle it I'm all ears.

Looks like something we should be able to do something about. What version is this so I can create a ticket for it?

2 Likes

This was on Ignition Platform version 8.1.41. I'll mark @drojas reply as the solution for now. Thanks

3 Likes