on
RE:
Great would be a Fabric "stand alone" secret store on workspace level:secret names have to be identical in release pipeline coupled workspaces (dev-test-prod-...), the deployment should replace the store references only on deploymenta mirror of a Azure Key Vault stores (like databricks does it) into a Fabric secret store would be nice
RE:
Filters do have a "hiding" option. Bookmarks must have the same option!!
RE:
oh yes it would be great !!
RE:
A major client is asking for this functionality, and will be a blocker for their adoption of Fabric. It seems odd that a key feature is being excluded from CI/CD to be honest. Should be an easy enough to allow the .json file to be incorporated into source control, surely?
RE:
for example: F&O table BudgetActivityMeasure
RE:
It would be great if we could create views of "records shared with me" across ALL entities, including bespoke. Historically, this was possible by querying the Principal Object Access table via custom FetchXML, however we understand from our Microsoft support ticket that this is no longer possible. (see https://vishalgrade.com/2018/01/07/how-to-view-shared-records-with-a-user-in-dynamics-crm/ for details of how this used to be possible). It feels like a step backwards to no longer be able to do this.
RE:
The General Ledger has to include the check number. It is a listing of billings and payments. The deposit number has no meaning to customers, employees, or auditors.
RE:
Please add dynamic filtering also to be handed over to dashboards.eg: if dynamic filter of last 5 month is set on visual and pinned to a dashboard, this 5 days are converted to static filter :(
RE:
This is especially useful when you have a dev, a test and a prod workspace for data engineers, but you don't want to have equivalents for all business domains. Having lifecycle management on report user/business domain workspaces would lead to 50+ workspaces for my customer, making it difficult to oversee. However, the business domain workspaces are useful for granting access on groups of reports. The current alternative is using the data engineering prod workspace for all reports. The reports are grouped in folders to make it easier to oversee, but we grant access to Entra ID groups report by report.In the Fabric deployment pipeline, we would still see all those reports and other artifacts ungrouped, which looks quite messy as well.
RE:
This feature will save storage cost for the customer.