Forum Discussion
Using a parameter to dynamically restrict number of rows in semantic model not working
Hi,
https://www.youtube.com/watch?v=_zYvybVMk7k
I have been using the above video to try and set up a way of doing all of my DAX calculations on a limited amount of rows, pubish the dashboard and update the semantic model through the service so that the dashboard and visuals are applied to all my data. I am trying to do this because I would have millions of row and upon trying to do simple DAX in PowerBI desktop on all the data, I ran out of memory. I am on the Pro version of PowerBI
The trick seems to work fine directly in PowerBI desktop. I set up a CountRows measure card to see if the parameter changes and it looks like I am indeed able to change from 10,000 rows to all of them directly in the desktop mode.
However, when I click publish and go to the service, changing the parameter in the semantic model's settings does not seem to do anything because that CountRows card never changes values.
Is there anything that I missing that would explain why this is not working as expected?
Let me know if there is any other information you might need to help me figure this out!
- Anonymous2 years ago
Thanks for the reply from blopez11 ., please allow me to provide another insight:
Hi,Anonymous
Have you found a solution? If you have found a solution, you are welcome to share it with us, which will be helpful to other members of the community who have the same problem.According to the error screenshot you provided, we speculate that you may not get the desired result because of the refresh failure. The time for you to successfully display the refresh is longer than the time for you to refresh the error, and what you provided is the success of OneDrive refresh. Please check whether your planned refresh is successful:
1.Please check that your gateway configuration is correct and that the credentials are valid when configuring the data connection:
Test single sign-on (SSO) configuration - Power BI | Microsoft Learn
2.You can also check to see if the credentials are valid in powerbi Settings.
3.Finally, you can also check if the file has moved, causing the refresh to fail.
4.Here is the relevant documentation:
Configure scheduled refresh - Power BI | Microsoft Learn
5.Here are some directions for troubleshooting:
Through the local gateway application to check: export the gateway connection log, which saves a lot of gateway information, including the cause of the error report
Best Regards,
Leroy Lu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
3 Replies
- blopez11
Super User
Did you refresh your model after making this change?
- AnonymousNot applicable
I did click on reload for both the semantic model and for the dashboard's visuals. However I am confused because of the above. I manually refreshed but if the error above is a normal result of manually refreshing or if it failed.
- AnonymousNot applicable
Thanks for the reply from blopez11 ., please allow me to provide another insight:
Hi,Anonymous
Have you found a solution? If you have found a solution, you are welcome to share it with us, which will be helpful to other members of the community who have the same problem.According to the error screenshot you provided, we speculate that you may not get the desired result because of the refresh failure. The time for you to successfully display the refresh is longer than the time for you to refresh the error, and what you provided is the success of OneDrive refresh. Please check whether your planned refresh is successful:
1.Please check that your gateway configuration is correct and that the credentials are valid when configuring the data connection:
Test single sign-on (SSO) configuration - Power BI | Microsoft Learn
2.You can also check to see if the credentials are valid in powerbi Settings.
3.Finally, you can also check if the file has moved, causing the refresh to fail.
4.Here is the relevant documentation:
Configure scheduled refresh - Power BI | Microsoft Learn
5.Here are some directions for troubleshooting:
Through the local gateway application to check: export the gateway connection log, which saves a lot of gateway information, including the cause of the error report
Best Regards,
Leroy Lu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.