References should keep styling from original data list

[lusebille]

Today when I create a list in a table and I use it in another table / widget as a reference/or multiple reference, style is not keeped. For exemple if my orginal list is a choice list with colored tags it tooked me time to do, I will loose all benefit of that landing with a white or grey list.

Notice than in a few days already 4 users complain about it ( 5 including myself ).

I'm joining screenshot and a Grist file. In the exemple 'Tags' column is used a a references for 'Keyword' column.Styling references_OK.grist.zip

[lusebille]

@vviers here the content for the ticket to move to French Administration Board with the good way to write a ticket I suppose

[RogerPenna]

I wouldn´t say SHOULD keep the styling. But the OPTION to keep the styling would be indeed welcomed.

[lusebille]

Hi @RogerPenna, I would be interested to know in which cases it's interesting not to keep the styling of references.

[RogerPenna]

A referenced value might appear in multiple tables or widgets, each with its own formatting rules to maintain visual coherence. For example, a budget column might show categories in colors within one table, but those colors might clash with or confuse the design of a summary table or dashboard.

Some users may prefer to reduce visual noise when presenting summarized or aggregated data. In such cases, a plain or neutral format can make the report cleaner and easier to read.

In certain roles or widgets, styling may not be relevant. For example, technical staff reviewing raw data in a control table might not need the same visual cues as management, where formatting emphasizes priority or status.

What is highlighted in one table (e.g., priorities with colors) may not need to be highlighted in another. For instance, a table for detailed tasks might use bold or color-coded tags for urgency, but when those tasks are referenced in a high-level overview, such styling might distract from other key metrics.

Again, notice I never said I am against it. I am saying it should be an OPTION, not something by default.

[tayflo]

Hoi 👋 I might add that I may also come handy for properties retrievals more broadly, e.g. through lookup and not only through reference.

For instance, I have a table A with a "Type" column (which could have the nature "unique choice" for instance), with style set on each type/choice. Then in a table B I retrieve the item.Type property somehow through formulas. Having the option to import both the value (here, the string of the given type) and the styling of the property could be nice.

[lusebille]

Hi, I added mocks to this ticket , so new user story will be :

• As a user, I may like to keep style from my original data list when I use it as reference because it's can be helpful for reading / understanding. It should be an option because in some cases I prefer not keeping it (some comments above) : https://www.figma.com/design/wcpetFt6aOKzTszcvPPWLQ/%5B05%2F24%5D-Grist-Design?node-id=2969-47969&t=mPi60Fw6o4Aurmbb-1