Forum Discussion
Formula.Firewall: Query references other queries or steps
Hi Anonymous,
I have un-checked the "Parellel loading of Tables" and the online refresh gives me the same error:
[Unable to combine data] Section1/Datos/AutoRemovedColumns1 is accessing data sources that have privacy levels which cannot be used together. Please rebuild this data combination.
The refresh works on my desktop but online It doesn't work.
Thanks for the answer!
Hi Mozasf
Can you confirm if you managed to solve the issue re refreshing JIRA data via the Power BI service?
I have an identical situation using JIRA data - i.e. loads OK via PBI Desktop but not PBI Service - and am struggling to find a solution.
Any help appreciated.
Thanks
- tuken8 years agoFrequent Visitor
I'll do it.
Regards.
- Anonymous8 years agoNot applicable
Hi ayup,
For the moment I haven't found a solution.I refer you to another post where we are looking for an answer:
https://community.powerbi.com/t5/Service/Unable-to-combine-data-accessing-data-sources-that-have-privacy/m-p/283033#M33748 - Anonymous8 years agoNot applicable
What is the error that is getting thrown when the refresh fails in service? Also, can you mention the duration once the refresh triggered and failed? you might get useful lnformation if you can do a fiddler trace once you start the refresh and share the details with Microsoft through a support ticket.
FYI , If you are pro user, you can raise a support ticket .
- ayup8 years agoHelper I
Hi Anonymous
Thanks for replying. The error I'm getting is "Message[Unable to combine data] Section1/Issue List/AutoRemovedColumns1 is accessing data sources that have privacy levels which cannot be used together. Please rebuild this data combination."
The scenario I have is the same as Anonymous where I make a first call to the JIRA API to retrieve the issue records I'm interested in; then loop through these records to make a second call to query additional info associated with each issue. In the second call, the URL path is dynamic as it includes the id of the record being queried.
Based on the commentary provided by @mithrandir in the thread referenced by Anonymous, it sounds like there's nothing that can be done to work around this other than manually refreshing data in PBI Desktop,
- tuken8 years agoFrequent Visitor
OK, thank you for your answer.
In case I find a solution or workaround, I'll let you know.
- Anonymous8 years agoNot applicable
Hi tuken!
I'm still thinking about the problem but I'm afraid there's no solution at the moment.
If you find any solution, please share it with us.
Thanks!