Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

FillColor problem in table

Avatar

Former Community Member

Sorry for my English is not my native language.
I have a table where I insert rows each time that I need to add a new record. In some rows I have to change the fillcolor of the fields and created a button that does it, but it is always in the first row of data in the table and not in others insert.
My question is how I can change the fill color of some rows not to do so in the first row of the table.
I appreciate any ideas and I thank everyone in advance.
  

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Thank you very much, your help has been crucial and has saved me a lot of work.

View solution in original post

2 Replies

Avatar

Level 10

I created a sample for you. Contact me at nith.igate@gmail.com

Few options:

1. You can use relative reference to the fields in the row. This cause the right field to be filled with color.

2. You can identify the current instance index and then locate the field to update it's fill color

I followed the first approach in the sample.

Nith

Avatar

Correct answer by
Former Community Member

Thank you very much, your help has been crucial and has saved me a lot of work.

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----