Forum Discussion
Fail to save modifications on the server - Microsoft Dynamics 365 Dataset
- 9 years ago
Anonymous I was finally able to refresh via Power BI online. I had to remove the report and publish it again.
After that, I was able to schedule refreshes without an issue.
If it happens again, I will try your suggestion and increase the max allowd.
Thank you all for your responses!
Thanks for the reply. Im running this on a computer with 16GB of memory. I have been monitoring the RAM usage during the refresh, and seems like never goes over 50%.
Hi ,
Can you test the refresh by reducing the no. of columns or having some constraints on your transactions table.
Are you using 32 bit or 64 bit version of PBI Desktop.
- rcalvo9 years agoFrequent Visitor
Again, thank you for your responeses.
I am using the 64 bit version, and unfortunately I can't reduce the number of columns.
I tried to reduce the number of rows by filtering the field "opportunitystage" using the following expression but did not seem to work. I still get the same number of rows (95k for this entity) before and after applying the filter.
let
Source = OData.Feed("https://XXXX/api/data/v8.2/"),
opportunities_table = Source{[Name="opportunities",Signature="table"]}[Data],filter=( "opportunitystage" = "870410007")
in
opportunities_table- Anonymous9 years agoNot applicable
Hi rcalvo,
Does the error persist after you increase the size of “Maximum allowed” as shown below in Power BI Desktop?
Thanks,
Lydia Zhang- rcalvo9 years agoFrequent Visitor
Anonymous I was finally able to refresh via Power BI online. I had to remove the report and publish it again.
After that, I was able to schedule refreshes without an issue.
If it happens again, I will try your suggestion and increase the max allowd.
Thank you all for your responses!