RE:
Agree. Current features don't really work: Dashboards have terrible visualization options, Auto-refresh reports need build access (so anyone can Explore the data from the office PCs!). We must be able to simply refresh the report, fetching the data from the underlying semantic model. This should be one of the most basic features possible.
RE:
So this is probably about changing the Date fields to Date Formula fields.I personaly do not like the enum variant, because it's far more restricted than a Date Formula.Alternatively we could have a background task to do the monthly switch.Advantage: It's still a clear date within the restriction fields.Disadvantage: We need a proper running task.Or we have the current Date fields & new Date Formula Fields. But then we still need the task.Advantage: Some users (finance department) usually have different Date (Formulas).
RE:
This is a "Must" feature ! Having a recycle bin would make the collaboration safer !
RE:
suggesting to change the design of "New Look" dropdown's for case type and case priority as same as "Old Look".
RE:
Is there any progress on this missing capability? I read, that the roadmap for CY2024 will contain mirroring of PostgresSQL db's?
RE:
Much Needed feature.
RE:
See Report Level Measures Data Type to default based on return value: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=e582477a-a276-ee11-a81c-6045bdbdefa6
RE:
It is actually possible to use report-level measures for conditional formatting. The problem appears to be that report-level measures need to have their data type set explicitly – and unfortunately the data type defaults to Decimal number (Double). The measure having a non-text data type is the reason why it can't be used as a Field value. But after changing the Data type to Text in the Measure Tools ribbon tab (after selecting the measure from the Data pane in the Report view), you should be able to use it for conditional formatting. In contrast, measures in a semantic model have their data type inferred from the DAX code and the data types of the columns and other measures that the DAX code references. Therefore, if you write a measure that constructs a text/string value, the Analysis Services engine will almost always infer that the measure has a Text data type. You can actually see these inferred data types in Tabular Editor.
RE:
https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=e79a9593-09d7-ee11-a73e-00224855381e
RE:
Because the link in my previous comment doesn't seem to be working. Here it is:Allow use of report-level measures for conditional formattinghttps://ideas.fabric.microsoft.com/ideas/idea/?ideaid=e79a9593-09d7-ee11-a73e-00224855381e