on
RE:
Renewing this idea, it would be great if something can be done.Many tables, including custom tables, are set up with list and card page relationships where the list page is not editable and the card page is editable. It allows us to provide a better user experience. Now, when the user goes to delete a record from the list page and there are checks on the record preventing it from being deleted (e.g., it has related records) it is not ideal for the user to be presented with "There are unsaved changes on the page. Do you want to discard these changes?" and then needs to choose No to see why they cannot delete the record, or if they choose Yes it just returns them to the list page and they don't see the reason why they cannot delete the record.
RE:
I think this is a similar ask to this one: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=24f6d4b9-ef05-ee11-a81c-6045bd847b50
RE:
I think this idea asks for a similar approach https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=6bd2453c-3eed-ee11-a73d-000d3a7c5b9a
RE:
This would be huge for our business!
RE:
Having this button on the same page as the job would help streamline our tasks and allow better efficiency. Having to open multiple tabs/windows slows our process down and sometimes causes delays in having accurate information.
RE:
Voted!MS should also consider that the financial dimension needs be selectable for the fixed asset(s) to be capitalized, rather than inheriting it from the WIP account's linked dimension which now can only be updated via general journal.
RE:
We are in synapse right now and use delta lake with serverless sql for all our use cases. It would be extremely important for us to have this feature in Fabric. Thanks again for your efforts to have this in Fabric.
RE:
Longer term road map???? DO IT NOW
RE:
This default color bug is driving me crazy and it has been 5 years now since the first request made.. please sort it out asap..
RE:
He use OpenRowset in all our projects.Allow usImplement data Virtualization, and avoid Staging tablesGrant access to data that is in the LZ but not in the User SQL tables with Views_LZImportant to haveThe ALDS / OneLake must be under firewall ==> Private endpoint compatible (**)Use SAS or Acces Keys . . .., But compatible with AAD (User MI or System MI) (**)Most of the Cases we use Authentication SQL Storage: Delegation / ImpersonateIn some cases for audit purpolses we need use Pass-Through Authentication, thus the AAD SQL user will appear on ADLS logsThe T-SQL Openrowset must be able to compile on Azure Data studio & Azure DevOps, currently is not able to do it and block all CI/CD progress (**)Format files (FMT) are really obsolete, need maintenance and are not part of Database Project / GIT, need to find a 2024 replacement (**)We hope that Select disctinct (col_1) [for Dim Tables] On parquet will be faster than on CSV, but sometimes is not (**)This Synapse "sugar" is very appreciatee: '*/*/*/myfile*.parquet'Currently select from openrowset INTO #Temptable is not supported (**)All the others: AGG pushdown, Metadata, Vertipaq / V-Order, PurView , , . . . future??(**) Hugo Queiroz knows about these issues and some of them are ACK by Azure support