I am attempting to dynamically set the label of a tag option in the table element based on whether or not a value in another query exists in the table. The issue I am having is that CurrentSourceRow does not exist at this level. This solution does work with SelectedSourceRow, but the table needs to have multiple updates made to it at any given time, so this option does not work. How else can I isolate the row index to make this dynamic?
{{
GetCurrentMonthCampaigns.data.Campaign_ID.find(id =>
id === CurrentSourceRow.CampaignID
)
}}
@Developers_Octane You could use mapped options where you could connect data source and then use item as a replacement for currentSourceRow. Here is a mockup example of it, but hope it helps with the logic
The column is editable and I am trying to set the options dynamically. Unfortunately I still can not filter based on CurrentRow if I try to map the options, and I do not have space to add another query to this app.
Currently, the tags options will be the same for every row We are tracking requests for this feature in our backlog. I'll reach out if we are able to ship this feature!
We use a lot of the Tag options (color/icon/etc) and it's more or less perfect for our use case, but we are hampered because only certain Tags apply to certain rows.
All of the current workarounds involve some kind of loss of function (values for other rows depopulate or lose their color, etc) and it would basically be flawless if we could just reference currentSourceRow here.
Currently, I have the full account info coming up in a Split Pane where they can edit it correctly in a dropdown, but I get asked a lot - how come we can't edit Tags on the table like Priority and Assignees?
I ended up using selectedSourceRow to populate the values of the dropdown when clicked, and then turned on the custom options dropdown. Basically the dropdown options are re-assessed each time a new row is selected, and once something is selected, it retains the option in the changeset array. It takes away my ability to do tag options, but it does prevent me from needing to use more elements to accomplish the same outcome.
It is very far from perfect, but if you can work with values and not colors or icons, it might work for you as well.
@Tess is we can get currentSourceRow as an option, that would be fantastic, but what I have in place now works.
My CRM unfortunately kinda looks like a Bloomberg terminal - information overload - so the color/icon consistency is critical for a decent user experience.
We are tracking requests for this feature in our backlog. I'll reach out if we are able to ship this feature!
