on
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
RE:
Interesting idea. I've voted for it because I would like Microsoft to look more closely at the user experience when creating report-level measures. Evidently, this defaulting of report-level measures to the Decimal Number / Double data type does cause a bit of confusion. See this Idea: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=e79a9593-09d7-ee11-a73e-00224855381eI think the reason that thin (live connected) reports require report-level measures to have their data type set explicitly, is that it is unable to reliably infer expression data types without direct access to a local model and all of the column data types. Hopefully in the future, thin reports will be able to get more information about the remote model to make this possible.
RE:
I need to read endorsements using the SDK Microsoft.PowerBI.ApiIts slightly confusing, because on this page in the docs it says its available:https://learn.microsoft.com/en-us/dotnet/api/microsoft.powerbi.api.models.report.endorsementdetails?view=azure-dotnetHowever the SDK nuget *seems* to be using the REST API, which does not provide that property in the docs:https://learn.microsoft.com/en-us/rest/api/power-bi/reports/get-reports-in-group#report