Forum Discussion
SSAS Tabular Model has been changed to AtScale model automatically
Posting the root cause and fix here. Please refer to this Issue. The fix has been confirmed with a customer.
SSAS Tabular Models converted to AtScale Automatic... - Microsoft Fabric Community
Root Cause
This issue was identified and fixed last year. We realized we were incorrectly classifying SSAS models as AtScale. The bug was in production for 1-2 months before being fixed and any live connected reports created during that time were being classified as AtScale. Up until AtScale integration was finished ~1-2mo ago, we were treating AtScale virtually the same as SSAS with no parameters added to the connection string - so no change in report behavior. Some of these reports could have been holding onto the AtScaleDatabaseLive connection type for the last year, and now after republishing, they're unfortunately catching the new WSID connection string parameter. This lines up with the the inability to reproduce the issue today and why new reports are working as normal, but the customer republishing existing reports causes the WSID property to appear and failure in gateway.
FixSaving the file as a .pbip (PBI Project) file, exposing the metadata for the connection and change it there (something you can't do in the PBI Desktop UI.) Saving as a zip file, changing the Connection file there, and then resaving as PBIX just ends up as a corrupted file so that is not an available fix.
Update per dato_Niall : When saving the PBIP file type, this exposes an extra folder (with the meta data @Greg_Deckler mentions) called [ReportName].Report where the PBIP file was saved. Within this folder is a file called 'definition'. This if opened in notepad is where the datasource can be edited. Once this is edited you can then save the report back to PBIX file and this fixes the issue.
Hi Greg, this great! When you say change the meta data? Could you eloborate a little more? Is this in the additional files that are created upon saving? Is there a particular file name that holds this meta data for us to change?
Update: When saving the PBIP file type, this exposes an extra folder (with the meta data Greg_Deckler mentions) called [ReportName].Report where the PBIP file was saved. Within this folder is a file called 'definition'. This if opened in notepad is where the datasource can be edited. Once this is edited you can then save the report back to PBIX file and this fixes the issue.
In our scenario, we didn't alter the PBIX in anyway. We made few measure edits as normal, saved the pbix and published it only to find that it saved itself with a Datasource connector of Atscale rather then SQL Analysis Services. We have no idea as to why but the fix identified by Greg_Deckler saved us a heap of time recreating the report! Thank you!
dato_Niall Thanks, I should have included that detail in the answer. I have edited my post with the extra detail information you provided.