ContributionsMost RecentNewest TopicsMost LikesSolutionsRe: Means to tag dashboards to enable search Hi DRay, yes - please move it. Thank you Means to tag dashboards to enable search We have a large number of dashboards and at the moment, find the navigation process for our stakeholders is not ideal as they can only "find" a dashboard if they know what words are used in the title. For example, if a stakeholder searches for complaints but the dashboard title they need is called feedback ... It won't come up as a suggestion. A solution like having the ability to tag dashboards would massively help Thank you Re: Ability to link a live connection and elasticube into the same widget Thank you DRay my ideas would be: 1. Potentially pre-fix metrics with elasticube or live e.g. User_Id_live or User_Id_elasticube 2. Not sure on the best practice but the benefit I can see if that we can use the elasticube connection for data which only changes daily to compare to a metric which changes more frequent and hence is more appropriate to get from a live connection ... the benefit being cloud processing cost saving Ability to link a live connection and elasticube into the same widget The idea of this is so you could show the elasticube data on the primary axis, and then potentially low latency data on a secondary axis - allowing easy comparison of live vs historical data Ability to separately change the caching period for each Live model At the moment, the caching period of live models is set for the whole instance which removed flexibility where you'd want the caching period to be different for exceptionally large models. For example, we have a table we have to ingest via a live connection as it is too big for elasticubes - but wouldn't want the caching period for this live connection to be too "low" as it would cost a lot via AWS. However, we would want a low caching period for low latency reporting