on
RE:
Hi KasperCould you elaborate on your thoughts for implementing this?Some years back when we published the app language apps on AppSource we did discuss a potential implementation, that included an "Allowed languages" page/list for an admin to specify on a given environment. In essence, if language would be specified there, this list would filter the visible languages in the language selector in My Settings.Does this correspond to your thinking?If so, would you be open for contributing such solution via Github if we decide to create this as an issue there?ThanksSøren Alexandersen
RE:
This would prevent a lot of frustration!
RE:
When Organization is selecting DWH Option. Keeping Source/Landing tables in One workspace. Target Dimensions and Facts in Different workspace. Cross Workspace querying is not allowed. In Order to load validate that data of Source/Landing is loaded into Target, we are unable to write T SQL Scripts. Shortcut in DWH will allow test team to write T SQL Scripts by querying Different workspace tables and confirm data in Target layer in different workspace.
RE:
We have this issue now. Our lakehouse owner left and now we're seeing errors in the lakehouse itself. The source dataflow was easily transferred to me, but that's clearly not enough. MSFT should escalate this issue.
RE:
This should be escalated. I am seeing errors in our lakehouse related to ownership changes. Our original owner no longer works for the company, but I need to be able to take it over. I was able to takeover the source dataflow without a problem but I can't refresh the preview in the Lakehouse itself.
RE:
Adding my support for this, Microsoft please do this!
RE:
This is definitely needed for our app... it updates some tables as item ledgers post, and if a user manages to post while the app is uninstalled, the tables need to be updated upon reinstallation. This would allow us to store the last ledger entry number on uninstall and shore up the data that was posted in between on reinstall.
RE:
over 5 years?!