Privacy Level setting is reset in Data Gateway after failed attempt to set up a dataflow

Status: New
by DP86 Visitor on ‎11-27-2018 06:42 AM

Privacy setting for a data source in the data gateway is reset to "None" whenever I cancel a process of setting up a dataflow entity with the data source and the gateway. I have not been successful in setting up a connection with any data sources at this time, so I do not know what would happen if I DON'T cancel the process. I am able to recreate the condition every time. This appears to be a bug, but I would like a confirmation that I am not doing something wrong to cause this.

by Moderator v-qiuyu-msft
on ‎11-27-2018 11:57 PM

Hi @DP86,


I'm not very clear about the issue, would you please share more information, eg: detail steps to reproduce the issue, some screenshots? 


You can take a look at this article to learn how to create a dataflow entity:


By the way, please ensure you are running the latest on-premise data gateway.  


Best Regards,
Qiuyun Yu 

by mwc360 Frequent Visitor
on ‎11-28-2018 08:15 AM

This same exact thing is happening to me. All of my gateway data sources are set to organizational. Whenever I try to create a dataflow off of one of these sources it resets the gateway privacy level setting to none and the next time all of our production reports refresh, they fail. I have yet to actually save a dataflow for these affected data sets so I also cannot confirm if this happens when the dataflow is fully set up. 


I would love to take advantage but right not even experimenting with them is causing production issues which is a huge barrier to testing them.



by DP86 Visitor
on ‎11-28-2018 10:38 AM

Qiuyun Yu,

The following are my steps:


  • This is what it looks like in the Gateway before the process:
  • Step 1:
  • Step 2:
  • Step 3:
    This is where it errors out for some reason.
  • Now the Gateway looks like this:
    The privacy level can easily be manually set to the original state, but 

I hope this helps you understand the condition.

Let me know if I need to suppy more information.

by Moderator v-qiuyu-msft
on ‎12-11-2018 09:48 PM

Hi all, 


I have reported this issue internally: CRI 94422090. Will update here once I get any information. 


Best Regards,
Qiuyun Yu 

by Moderator v-qiuyu-msft
on ‎12-13-2018 05:38 PM

Hi all, 


The fix should be released around January 5th. 


Best Regards,

Qiuyun Yu