Hi Ruth, I believe you can choose to Edit permissions in the Data Source Settings window which will allow to change the privacy level. At least that's what I thought you meant.
Thanks for the video! I believe that this feature is not a security or a data protection feature. It is just an alert or a reminder for the user that creates the query that some piece of data is sensitive and he should be careful. Anyone can change the privacy level so in my opinion it gives us no protection at all. Just a reminder... Am I right?
Hi! If you combine a public source with a private one, power query can send data from the private to the public to make it more effective: th-cam.com/video/72beG_VHufU/w-d-xo.html That is a security risk if you private data is sensitive. Hope this clarifies! /Ruth
Good to understand that Power Query for efficiency purposes resend data to the source. If one source is online and the other local data from own computer, by combining them some private data might be sent to the online source. This part is clear. Now, if I am using Power Query only on one local file from my own computer, why would I get this Error? Because of multiple queries being built upon the results of each other? Since it is the same source, I would like to understand the error message.
@@CurbalEN Thanks for the quick response. I created a parameter function to use multiple times. Even if I call the function on the original data, I get this privacy error. I could ignore my local privacy but somehow I shouldn't have to since I am using the same source.
If you are importing the same file multiple times, Power bi doesn’t necessarily know that it is the same source and therefore it asks you to verify the privacy rules. You don’t need to ignore the privacy, just set the rules and depending on what you set them to, the message will disappear. /Ruth
Possible Settings: - Data Source (None, Organisation, Private or Public), - Local ( Each source or Ignore), - Global (Each source, Each file or Ignore) which adds up to 24 Settings possibilities. My Parameter query has the following M.Code: (Parameter as text)=> Let Source=Folder.Files(local path). The only Settings that work are Global: "Each File", Local:"Ignore", Data Source:"They all work". So I have no Settings where I don't have to use "Ignore" locally. Now if data is sent back to the source which is local on my Computer then I have no data leak and I can use the Settings: Global: "Each file", Local:"Ignore" and Data Source: "Any, doesn't make a difference". Are there any other Settings possibilities? Thanks
Hi my source are excel workbooks on a network drive only a few individuals know about and have read write access to. I do not want this pop up appearing for each new user on first try, if I set it to public what does that "do" just prevent data mixing with high levels?
Thanks a lot for your explanation. I have found your video as I was searching for a clear explanation on what the exact difference is in the Global privacy settings between "Always combine data according to your Privacy Level settings for each source" and "Combine data according to each file's Privacy Level settings". I have understood the concept of Privacy levels and prepared a manual on this; also I know how to change Privacy levels for each data source individually - the only thing I am not clear is a that difference - also I have not found any explanation anywhere.... could you help bring light on this? Thanks very much.
Just wanted to quickly share, what I have found. I guess the chosen wording could have been chosen a bit better. "... for each source..." and "...to each file's..." was a bit misleading for me, as I thought they were both referring to data sources, the latter in form of files..... but fact is, th term "...to each file's..." actually means Excel workbook, as am working in Excel. So chosing that option, I am free to handle the situation for each workbook individually. Maybe the term "file" was chosen due to pbix-files? Hope am on the right track here :-). cheers.
That is very good content. Even better would be the turn around (the safe way of merging outsource information). I will check out the another video you said
Nice Video, and a good explanation of the background. What might be missing is a good example where the privacy settings give a useful result. E.g. you have a list of stock symbols you want to buy, and a public database. By downloading your stock symbols, you disclose to the database what you are interested in.
Does these data privacy settings matter when we have only single data source? I am using single datasource and I want to understand if I have to modify the data privacy setting for the current file and what are its consequences.
Hi Ruth. Thanks for the video. Good Job. Everyone out there on the internet just "tell"' to go and ignore the privacy levels and your video was the first one that I found explaining the real thing so each one of us can make an informed decision depending on the data that we are dealing with. Do you know what is at stake here when we are merging two different data sources? Is it the tables involved in the process or the entire dataset? I have a table with addresses which I'm trying to use R to help with data cleanup. I don't have any sensitive data on the table with the addresses so my level of concern with that table is very low, but I have other tables in the same data source with sensitive data. My guess would be that the exchange of information is only between the two “tables” in the process (In my case the address table might be used by R Script), but I would like to know it for sure. Thanks Ayrton
Interesting video, thank you! I work with sensitive medical data so data privacy is very important. I'm trying to use R scripts to transform my data from an on-premise SQL server database but i keep getting the error about the privacy levels when i wan't to run R scripts on one of the tables. Do you know if there's a way of doing this without changing the privacy settings of the database tables to public?
Privacy levels are required for you to use online services - like the Enterprise or Personal gateways. This is explained nowhere. Each query, when using privacy enabled, is only able to use it's own steps. And it is also confined to using one specific source. Only tables like those in Excel do not seem to be affected by these limitations.
Hi Ruth, I believe you can choose to Edit permissions in the Data Source Settings window which will allow to change the privacy level. At least that's what I thought you meant.
This was useful! My merges would often break and I have no idea why
Yeah, frustrating when you don’t know what it is causing it!
/Ruth
Thanks.. Now I am clear the use of this privacy in powerBI.. Thanks a lot again...
Glad it is clear now :)
/Ruth
Thanks for the video!
I believe that this feature is not a security or a data protection feature. It is just an alert or a reminder for the user that creates the query that some piece of data is sensitive and he should be careful.
Anyone can change the privacy level so in my opinion it gives us no protection at all. Just a reminder... Am I right?
Hi!
If you combine a public source with a private one, power query can send data from the private to the public to make it more effective:
th-cam.com/video/72beG_VHufU/w-d-xo.html
That is a security risk if you private data is sensitive.
Hope this clarifies!
/Ruth
Good to understand that Power Query for efficiency purposes resend data to the source. If one source is online and the other local data from own computer, by combining them some private data might be sent to the online source. This part is clear. Now, if I am using Power Query only on one local file from my own computer, why would I get this Error? Because of multiple queries being built upon the results of each other? Since it is the same source, I would like to understand the error message.
Hoy shouldn’t get that error with one single source.
/Ruth
@@CurbalEN Thanks for the quick response. I created a parameter function to use multiple times. Even if I call the function on the original data, I get this privacy error. I could ignore my local privacy but somehow I shouldn't have to since I am using the same source.
If you are importing the same file multiple times, Power bi doesn’t necessarily know that it is the same source and therefore it asks you to verify the privacy rules.
You don’t need to ignore the privacy, just set the rules and depending on what you set them to, the message will disappear.
/Ruth
Possible Settings: - Data Source (None, Organisation, Private or Public), - Local ( Each source or Ignore), - Global (Each source, Each file or Ignore) which adds up to 24 Settings possibilities. My Parameter query has the following M.Code: (Parameter as text)=> Let Source=Folder.Files(local path). The only Settings that work are Global: "Each File", Local:"Ignore", Data Source:"They all work". So I have no Settings where I don't have to use "Ignore" locally. Now if data is sent back to the source which is local on my Computer then I have no data leak and I can use the Settings: Global: "Each file", Local:"Ignore" and Data Source: "Any, doesn't make a difference". Are there any other Settings possibilities? Thanks
Those settings are good, go for it!
/Ruth
Hi my source are excel workbooks on a network drive only a few individuals know about and have read write access to. I do not want this pop up appearing for each new user on first try, if I set it to public what does that "do" just prevent data mixing with high levels?
Thanks a lot for your explanation. I have found your video as I was searching for a clear explanation on what the exact difference is in the Global privacy settings between "Always combine data according to your Privacy Level settings for each source" and "Combine data according to each file's Privacy Level settings". I have understood the concept of Privacy levels and prepared a manual on this; also I know how to change Privacy levels for each data source individually - the only thing I am not clear is a that difference - also I have not found any explanation anywhere.... could you help bring light on this? Thanks very much.
Hi Giuseppe, I will try to make a new video to clarify.
Also, I have blocked and reported Rami. Apologies for the harassment!
@@CurbalEN wow, you are very fast in replying - highly appreciate it. Thanks a lot
Just wanted to quickly share, what I have found. I guess the chosen wording could have been chosen a bit better. "... for each source..." and "...to each file's..." was a bit misleading for me, as I thought they were both referring to data sources, the latter in form of files..... but fact is, th term "...to each file's..." actually means Excel workbook, as am working in Excel. So chosing that option, I am free to handle the situation for each workbook individually. Maybe the term "file" was chosen due to pbix-files? Hope am on the right track here :-). cheers.
That is very good content. Even better would be the turn around (the safe way of merging outsource information). I will check out the another video you said
Nice Video, and a good explanation of the background. What might be missing is a good example where the privacy settings give a useful result. E.g. you have a list of stock symbols you want to buy, and a public database. By downloading your stock symbols, you disclose to the database what you are interested in.
Does these data privacy settings matter when we have only single data source? I am using single datasource and I want to understand if I have to modify the data privacy setting for the current file and what are its consequences.
Hi Ruth. Thanks for the video. Good Job. Everyone out there on the internet just "tell"' to go and ignore the privacy levels and your video was the first one that I found explaining the real thing so each one of us can make an informed decision depending on the data that we are dealing with. Do you know what is at stake here when we are merging two different data sources? Is it the tables involved in the process or the entire dataset? I have a table with addresses which I'm trying to use R to help with data cleanup. I don't have any sensitive data on the table with the addresses so my level of concern with that table is very low, but I have other tables in the same data source with sensitive data. My guess would be that the exchange of information is only between the two “tables” in the process (In my case the address table might be used by R Script), but I would like to know it for sure.
Thanks
Ayrton
I believe it is only the concerned tables that can leak, to be sure ask for an official answer at community.powerbi.com
Interesting video, thank you! I work with sensitive medical data so data privacy is very important. I'm trying to use R scripts to transform my data from an on-premise SQL server database but i keep getting the error about the privacy levels when i wan't to run R scripts on one of the tables. Do you know if there's a way of doing this without changing the privacy settings of the database tables to public?
Same happened to me when trying with Python. But I don't really see the consequences if I set it to Public
Did you find the answer to that? Use R or Python only to public dataset it's kind of very limited.
Just set the privacy levels correctly and you should be fine.
Good stuff. Really appreciate it.
Thanks:)
/Ruth
Privacy levels are required for you to use online services - like the Enterprise or Personal gateways. This is explained nowhere.
Each query, when using privacy enabled, is only able to use it's own steps. And it is also confined to using one specific source.
Only tables like those in Excel do not seem to be affected by these limitations.
Thanks for sharing ! :)
/Ruth
Even if i set my both sources to public i still get the error.