Run a query against a dataset using power automate

It seems like you're encountering an issue with fetching a large amount of data from a Power BI dataset via Power Automate and not getting the expected number of rows in the CSV file. Let's break this down to address the discrepancy:

1. TOPN and Limit Parameters:

- When using the TOPN function in Power BI, it specifies the number of records to be retrieved based on a specific criteria.

- The Limit set in your case might be influencing the query results by limiting the number of rows returned.

2. Data Retrieval Limitation:

- Even though you've set the TOPN to 500000, the actual data returned could vary due to limitations imposed by the service.

- Power Automate or Power BI may have restrictions on the number of rows that can be retrieved in a single query.

3. Possible Solutions:

- To address the issue of not getting the expected 60K rows in your CSV file, you can explore the following options:

- Check if there are any restrictions or throttling limits on the number of rows that can be retrieved in a single query.

- Consider breaking down the data retrieval into smaller chunks or batches to avoid hitting any limits.

- Review the query parameters and ensure they align with your data retrieval requirements accurately.

4. Further Troubleshooting:

- You might need to dive deeper into the specific configuration of your query, especially how the TOPN and Limit parameters are interacting with the dataset and Power Automate.

- Experiment with different combinations of parameters to see if there's a more optimal way to retrieve all 60K rows successfully.

By reviewing and adjusting the parameters, considering data retrieval limitations, and potentially splitting the data retrieval into smaller parts, you should be able to troubleshoot the issue and improve the data retrieval process. If you encounter any specific error messages or have additional details, they could provide further insights into the issue. Let me know if you need more guidance or have any specific questions!

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Netaji Junghari1y ago
Thank you for your kind response!

I have checked, In power automate, with single query we can fetch only 1000 row data. And if you are using query against dataset the it will extend till 100000.

So I have changed from 500000 to 100000 in TOPN function still same . There exactly count we are getting everytime. It's not increasing or decreasing
0
Emily Foster1y ago
It seems like you're encountering an issue with fetching a large amount of data from a Power BI dataset via Power Automate and not getting the expected number of rows in the CSV file. Let's break this down to address the discrepancy:

1. TOPN and Limit Parameters:

- When using the TOPN function in Power BI, it specifies the number of records to be retrieved based on a specific criteria.

- The Limit set in your case might be influencing the query results by limiting the number of rows returned.

2. Data Retrieval Limitation:

- Even though you've set the TOPN to 500000, the actual data returned could vary due to limitations imposed by the service.

- Power Automate or Power BI may have restrictions on the number of rows that can be retrieved in a single query.

3. Possible Solutions:

- To address the issue of not getting the expected 60K rows in your CSV file, you can explore the following options:

- Check if there are any restrictions or throttling limits on the number of rows that can be retrieved in a single query.

- Consider breaking down the data retrieval into smaller chunks or batches to avoid hitting any limits.

- Review the query parameters and ensure they align with your data retrieval requirements accurately.

4. Further Troubleshooting:

- You might need to dive deeper into the specific configuration of your query, especially how the TOPN and Limit parameters are interacting with the dataset and Power Automate.

- Experiment with different combinations of parameters to see if there's a more optimal way to retrieve all 60K rows successfully.

By reviewing and adjusting the parameters, considering data retrieval limitations, and potentially splitting the data retrieval into smaller parts, you should be able to troubleshoot the issue and improve the data retrieval process. If you encounter any specific error messages or have additional details, they could provide further insights into the issue. Let me know if you need more guidance or have any specific questions!
0