Forum Discussion
[Unable to combine data]
Update.
Cautiously glad to report that the issue appears to be resolved. What seems to work is to remove reference to all queries and bring them all into one "monolithic" query. No compaints since that the query is referencing other queries or steps.
Thank you all for jumping in with tips and references. They were very helpful.
Cheers, and have a great weekend!
Hi ckkrish ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.
Verify the privacy level settings for your data source in the Power BI service.
If you're using a personal gateway, ensure the privacy level is configured as "Organizational" to enable efficient data combination.
Make sure the tables you are attempting to combine have compatible structures.
If the tables have varying column names or data types, consider applying the necessary transformations to align them before combining.
If you're dealing with a large number of DUNS numbers, consider using techniques Divide the list of DUNS numbers into smaller chunks and process them in batches.
Develop a dedicated function to manage API calls, extract data, and perform initial data shaping for a single DUNS number. This enhances both the readability and maintainability of the code.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
Hi v-menakakota,
Thanks for your response.
Privacy settings are "Organizational".
The tables should have identical structures as they are data items resulting from identical calls. Moreover, I have not noticed any discrepancies in desktop version. Do you think if one of the responses (to API calls) results in fewer data elements than others it can cause an issue? I am thinking that could be a possibility. Anyway, again the desktop version doesn't seem to have any trouble with it. Refresh on service is the one unhappy with something in it.
DUNS numbers are not too large. Its about 140-150, and is well within rate/quota limits.
>>Develop a dedicated function to manage API calls, extract data, and perform initial data shaping for a single DUNS number.
A dedicated function manages the API calls. Any other improvements, could you be kind enough to review the code and make specific modifications or suggestions? I am really not an expert in this. Are there any references (books/urls) that you can suggest to enhance myself - over longer term, of course.
Thank you again for your suggestions.
Regards.