Forum Discussion
Table 'LocalDateTable_2a2cf38a' with ShowAsVariationsOnly property set to '1' must be a target of
I am stuck with one of my reports. The model in my pbix is a mix of Excel Files and MySQL database tables. I created a query table using Union/Selectcolumns from these tables and it was all working fine. Now if I try and make any change to the table query it starts popping this error
Table 'LocalDateTable_2a2cf38a-7f01-4d5d-a76f-30eba6ecc9f3' with ShowAsVariationsOnly property set to '1' must be a target of a variation when variation notation is enabled.
I tried everything including one previously shared solution from 2018 that suggests turning off Auto Date/Time in file Data Load and turning it on. When I turn it on I get the similar error message that mostly quotes the error mentioned above with "Unable to make changes to server"
Have put in a lot of effort into this file already and am kinda stuck here for a day now.
Cheers
Pranshu
6 Replies
I got this error when I was trying to change the dataset (Salesforce Report) in a premade report. I was also changing the Table Name in the prosess for consistancy and clarity. I believe this was causing this issue. Once I left the Table Name as what it was originally I was able to refresh the data without getting the error.
If I try to change Table Name outside the QueryEditor the error appears again.
Hope this helps someone.Hi PranshuJ
try a solution from here https://community.powerbi.com/t5/Desktop/Data-Modeling-Help-ShowAsVariationOnly-Error/td-p/226859
do not hesitate to give a kudo to useful posts and mark solutions as solution
tried this one and was able to unselect the "Auto Date Time" but when I turn it on I get the same error message and that it is unable to make changes to the server
hi PranshuJ
Please update your Power BI desktop to the latest version to try it again. If the issue still occur, kindly create a support ticket for help of you are a pro user.
https://powerbi.microsoft.com/en-us/support/
Regards,
Lin
I had a similar error. I solved it by removing the source that uses DirectQuery. Apparently the table was updated in it, and because of this an error occurred
