I wrote javascript that creates a dashboard filter. I want my javascript to mark which filter it created. That way, on the next refresh, it can update or delete it if needed.I've done that by creating a new property like this: dashboard.filters(choose the one I want).jaql.MyNewProperty = "true".My question is: It's working for me now, but is this solution robust long-term? Any caveats I should be aware of? Are custom properties on widgets/filters/etc. a good tool for future projects?&n...

Hi Tim , We (at RAPID BI) initially struggled to make custom properties 'stick' to items. These were metadata items as well as filter items. I remember this issue when I was extending our internal RAPID BI Hide Filters plugin, that allowed our designers to set and then hide filters on the filter shelf. I'm not sure if this is still the case in 2024.2. As a rule of thumb, we try to add custom properties to the style or options properties within a widget or dashboard. In the case of the hideFilter...

Javascript custom properties | Help and How-To

MoreDiscussions

Javascript custom properties | Help and How-To | Sisense Community