on
RE:
This is a singificant limit to the data enquiry functionality, and we've bumped up against it several times in our implementation
RE:
We customised to create a single list page of lines requiring approval - and it was the difference between the count approval functionality being unusable versus it being very useful
RE:
The way this is presented currently is very confusing to pickers and leads to frequent picking errors in a fast-paced picking environment
RE:
When an item gets deleted (Lakehouse, Warehouse, Notebook, Report, Pipeline, etc.) it should go to a recycle bin first.It should stay there for some days before it gets completely deleted. I suggest 14 days as a good time period. Or it can be adjustable time period.This way, if someone accidentally deletes an item, it will be possible to recover the item and it's data.It should also be possible to delete an item from the recycle bin to completely delete the item, in order to avoid unnecessary storage costs.There should be a recycle bin for each workspace. The workspace members can recover items from the recycle bin.If a workspace gets deleted, it should be possible for the Fabric Admin or Capacity Admin to recover the workspace.
RE:
In order to prevent security incidents where users with the same name are accidentally shared, it would be beneficial to add a function that warns users when sharing/sending outside the tenant. SharePointOnline and ExchangeOnline already have this implemented.It would also be a good idea to add a setting that allows administrators to control sharing to guest accounts for each environment.
RE:
And also: Please note that the historical data like sold and deducted transactions are not taken into consideration when you want to setlle demand forecast. MS Ticket: TrackingID#2409200050000005
RE:
Any news on this topic?I can't see it on road map (as other pointed out) but is October 2024 still the expected date?This would be great as it would allow so many ways to interact programmatically with the entire Fabric environment.
RE:
The scenario I'm working with is data-level language translations. I've got all the work done to swap out the column for the correct language based on a slicer/language table, but what I want is to be able to default that slicer to the USERCULTURE value in a DAX measure. That way when a es-ES user visits the page it automatically sets the filter and they do not have to choose a data-translation language. Metadata translations work fine via Translation Builder, but the data-level one seem to require the user specifically choosing a language. Having this feature completed would solve this issue I think.