Translation parameters in Universal GUI grid

​@cvhrn We have deliberately not implemented it for Grids, since a Grid header is shown once above all Grid records. The Grid header translation is not necessarily close to the selected record (based on which a parameterized Column label translation is determined) and updating the Grid column header translation when selecting a different grid record would cause additional renders and more noise in the UI.

For what Use cases do you think this would be desired and valuable in Grids too?

Thank you for your reply, I'll explain our current use case.

We currently have a view that requires up to 5 “dynamic” columns. We implemented this using 2 fields for each “dynamic” column: one that sets the type of the column (which is a custom domain with combobox), and one for the actual value.

So table “A” has columns extra_info_type1, extra_info_type2, etc. Table B, which is linked to Table A then has extra_info_content1, extra_info_content2.

In our view we currently visualize this as follows:

If we we were able to use a parameter in the grid header translation (or some sort of subquery), we could instead render it as follows:

This would reduce the amount of columns needed to be shown and look a lot cleaner. 

​@cvhrn to clarify your Use Case: in your example the 'Type’ could vary I assume, based on the selected Combo Element, so you could have a situation like this?

And then the Grid translation in your second Table would have to be adjusted as follows based on the selected Row?

Row 1 selected:

Row 2 selected:

If so, you might want to try and create an (Editable) Cube and see if you can visualize the data the way you desire by defining the 'Type’ columns as Series and the 'Content’ as Values: 

Let me know if this helps!

Hi Arie, we are running into the same limitation.

We are building an ATP dashboard with columns like today, tomorrow, +2, +3, which we want to make dynamic. Translation parameters would fit here.

We deliberately do not use a cube, because we want to show underlying details and link tasks directly to the data.

​@Peter van Leenen To clarify your Use case: if you have Translation parameters, do you then intend to show the actual dates instead of +2/+3/…? If so, that would be an typical case to solve with an (Editable) Cube. 

Showing underlying Detail (tabs) and executing Tasks on a selected cell should in fact work for Cubes too. You currently don’t have the ability to perform Double-click tasks on a Cube field though.

Yes, correct — the intention is to show the actual dates instead of +2/+3/etc.

When we started building this, I was informed that this was not (properly) possible with cubes at the time. It may have improved since then, so I will re-evaluate that.

That said, it still feels like a useful addition regardless. Since this functionality now exists, it would make sense to also make it available for grids.