Forum Discussion
Refresh error: Reason: PrivacySetting - "Information is needed in order to combine data"
Hi Anonymous and everyone else.
I think I have narrowed the changes of Privacy Settings in Gateway data source list down to the launch of Dataflows which happened same week.
The way Dataflows currently work has some unwanted sideeffects on Gateway Data source settings. If I add a Dataflow from Source A it will automatically change Source A privacy settings to "None" in the Gateway settings.
If I then change Source A back to "Organisational" in my Gateway settings my Schedules Refresh works again. Untill next time I go and fiddle around with a Dataflow from Source A resulting it to change back to "None" in Gateway settings.
... in addition, let's say you don't have a Source B in your Gateway source list yet. The moment you add a Dataflow from Source B it will automatically add Source B to your Gateway source list resulting in potentially unwanted sources in the Gateway....
Nearly all of our production reports failed at this same time too with this same error...its almost like just this week the privacy setting feature started working as intended... Why no notification from Microsoft if they are going to make production changes that have brought many peoples reports down with no insight into how to fix???
Hi Anonymous and everyone else.
I think I have narrowed the changes of Privacy Settings in Gateway data source list down to the launch of Dataflows which happened same week.
The way Dataflows currently work has some unwanted sideeffects on Gateway Data source settings. If I add a Dataflow from Source A it will automatically change Source A privacy settings to "None" in the Gateway settings.
If I then change Source A back to "Organisational" in my Gateway settings my Schedules Refresh works again. Untill next time I go and fiddle around with a Dataflow from Source A resulting it to change back to "None" in Gateway settings.
... in addition, let's say you don't have a Source B in your Gateway source list yet. The moment you add a Dataflow from Source B it will automatically add Source B to your Gateway source list resulting in potentially unwanted sources in the Gateway....
This isn't solved.
I think you are right that this can all be tied back to dataflows being deployed but we need an actual answer from Microsoft here.
I have had every datasource that was working fine without privacy setting issue fail on me in the last two weeks. A couple of them I did create a dataflow with. One in particular that started throwing a privacy setting error a couple days ago has never been set up with dataflows (Teradata insn't supported yet), did fail in the last couple weeks and at the gateway level was set to organizational, and somehow got switched back to None even though no one on our team did this.
The answer I need from Microsoft is, what update was deployed that made all of our production reports fail, what was the purpose, why have data gateway privacy settings reverted back to none, even without dataflows being used.
Mardin Thank you so much for solution. Half a day spent going crazy until i found your solution!
Thank you! This solution was helpful for us today. we also implemented Dataflows and then immediately had this error.
can we get a moderator or admin to look into this issue, this issue isn't solved, this is a defect of deploying dataflows. All that has been identified is the root area that the issue stems from. This needs to be fixed by MSFT, it was never communicated that by trying out a new feature it would break all production reports in the service.
We are also getting this error. Datasets that were previosly refreshing fine are now getting the error
Microsoft.Data.Mashup.MashupSecurityException.Reason: PrivacySetting I have changed all Gateway data sources to None but this has not helped. Has anyone found a solution.
We have also started to use Dataflows and I am sure that this triggered the error.
Thanks for this. My scheduled refresh works now.
