on
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
RE:
I've got a prospective client that would greatly benefit from this feature working for PostGresSQL - any further timeline updates?
RE:
Our current client is currently between a rock and a hard place without this feature. Has to stay with MRP functionality, but needs the performance of PO. Please consider making this a priority for an upcoming release.
RE:
Yes this would take pro dev experience to the next level. Thanks for submitting
RE:
Bundles really needs the capability to ship different parts of the bundles on different loads/shipments. This process appears to work then is blocked at delivery note posting. Would be useful also to have options around how the sales price is apportioned, options to have this based on cost or the ability to leave all the value at the parent level would be useful.
RE:
This is a great idea. Instead of defaulting the Description field to blank, the default value of the Description field could be controlled in Purchases & Payables, with blank as one of the options..
RE:
I am staggered that MS still dont have this essential functionality within their Roadmap for Realtime, surely this fuctionality to be able to create a .CSV or .XLS is not difficult to create and code, yet is the most requested Segmentation feature following the abandonment of Outbound, and no feedback or comments about it from them.