Forum Discussion
Downloading/Exporting PBIX via API/cmdlet that contains incremental refresh
Anonymous As the old security mantra goes "If you don't want them to steal your data, don't show them your data".
Anyone with access to the app or the workspace can use XMLA to pull not just the data but also the meta data. I have used that to great comedic effect when I connected to someone else's dataset in DAX Studio and disproved their claim that they had disabled Auto Date/Time hierarchies.
It seems like you're the only one who ever knows anything about what I'm doing haha.
Ok that's helpful, thanks. I'm actually wondering about ways to secure a dataset and all of its associated assets from clients if for whatever reason I needed to publish it to their service and I didn't want them to be able to access the data model, power query, etc.
Any way of preventing them from being able to use the XMLA clients on that dataset? Would the APIs or cmdlets still let them export it?
Anonymous As the old security mantra goes "If you don't want them to steal your data, don't show them your data".
Anyone with access to the app or the workspace can use XMLA to pull not just the data but also the meta data. I have used that to great comedic effect when I connected to someone else's dataset in DAX Studio and disproved their claim that they had disabled Auto Date/Time hierarchies.