Power BI DirectQuery Model - AAS connection update -> Fabric

Question

Power BI DirectQuery Model - AAS connection update -> Fabric

Anonymous

Trying to change the connection details for a powerbi directquery report locally. If I swap out the long asazure// address from the old Analysis Service url, with the new powerbi// address for the model I want in fabric, I can change the server name successfully, so I can connect to a semantic model called the same name as my AAS cube name. But If I try and change the server & database name at the same time, i.e. update the model name from Model_V1 to Model_V2, I get an issue. Is this resolvable?

Error Message:

PowerBINonFatalError:

{"AppName":"PBIDesktop","AppVersion":"2.155.756.0","ModuleName":"Microsoft.PowerBI.Modeling.Engine.dll","Component":"Microsoft.PowerBI.Modeling.Engine.DataModel.Utilities.DataModelExtensions","Error":"System.NullReferenceException","MethodDef":"GetObjectTranslations","ErrorOffset":"6","ErrorCode":""}

Srikanth Chavithina 265 Reputation points Microsoft External Staff Moderator

2026-07-12T13:22:41.6166667+00:00

Hi @Anonymous
I hope you had a chance to review the information shared earlier and found it helpful.

If you still have any questions or need further clarification, please let us know in the comments so we can assist you further.

We look forward to hearing from you.
Anonymous

2026-07-12T13:46:46.7566667+00:00

Hi Srikanth,

I can connect directly to Model_V2 and have confirmed it is the schema as Model_V1.

I've tried doing the repoint server and saving the pbix and closing. Then repointing to the new Model_V2. But that just gives me the same error message in my original post.

This is a composite report. If I try doing this just on a live connection, to convert from AAS Model_V1 xmla endpoint to Fabric Model_V2 report I don't get any issues.

I think this is genuine bug in Desktop
Srikanth Chavithina 265 Reputation points Microsoft External Staff Moderator

2026-07-12T14:36:48.02+00:00

Hi @Anonymous ,

Thank you for confirming the additional details.

Since the issue is reproducible only with the composite model, while the same AAS-to-Fabric repointing works successfully with a live connection, this does appear to be unexpected Power BI Desktop behavior rather than a connectivity or target semantic model issue.

However, the GetObjectTranslations stack trace alone is not sufficient to confirm the exact root cause or classify it as a confirmed product bug.

Could you please confirm whether you are using the latest version of Power BI Desktop? If so, please also share whether the issue can be reproduced with a newly created composite model using the same Model_V1 to Model_V2 repointing scenario. This will help further isolate whether the behavior is specific to the existing PBIX or reproducible across composite models.

I hope this helps.
Anonymous

2026-07-12T15:42:31.0233333+00:00

I've tried Jan, May & June 2026 (latest) releases of Power BI desktop.

I have tested creating completely new DirectQuery report from AAS, then repointing. Still same issue. It's something about the model name that is baked into the schema sync step. If not the same model name it's not being synced correctly
Srikanth Chavithina 265 Reputation points Microsoft External Staff Moderator

2026-07-13T08:53:54.3766667+00:00

Hi @Anonymous
Thank you for validating this across multiple Power BI Desktop versions and for testing with a newly created DirectQuery report.

Based on your findings, the issue does not appear to be related to a specific Desktop release or the original PBIX file. Since repointing succeeds when the target semantic model retains the same name but fails when both the server and model name change, the model-name change appears to be a key factor in reproducing the issue.

Given the consistent reproduction and the NullReferenceException occurring during model metadata processing, this appears to be unexpected behavior in the composite model repointing/schema synchronization workflow. However, the available information is not sufficient to confirm whether this is a current product limitation or a defect.

As a practical workaround, if possible, you can keep the target Fabric semantic model name aligned with the original AAS model name when repointing the report, since the server-only change succeeds in your testing.

Thank you for providing the detailed reproduction results. I hope this helps
Srikanth Chavithina 265 Reputation points Microsoft External Staff Moderator

2026-07-20T08:32:18.18+00:00

Hi Peter McInnes,
I hope you had a chance to review the information shared earlier and found it helpful.

If you still have any questions or need further clarification, please let us know in the comments so we can assist you further. We look forward to hearing from you.

2 answers

Your answer

Srikanth Chavithina 265 Reputation points Microsoft External Staff Moderator

2026-07-12T13:22:41.6166667+00:00

Hi @Anonymous
I hope you had a chance to review the information shared earlier and found it helpful.

If you still have any questions or need further clarification, please let us know in the comments so we can assist you further.

We look forward to hearing from you.
Anonymous

2026-07-12T13:46:46.7566667+00:00

Hi Srikanth,

I can connect directly to Model_V2 and have confirmed it is the schema as Model_V1.

I've tried doing the repoint server and saving the pbix and closing. Then repointing to the new Model_V2. But that just gives me the same error message in my original post.

This is a composite report. If I try doing this just on a live connection, to convert from AAS Model_V1 xmla endpoint to Fabric Model_V2 report I don't get any issues.

I think this is genuine bug in Desktop
Srikanth Chavithina 265 Reputation points Microsoft External Staff Moderator

2026-07-12T14:36:48.02+00:00

Hi @Anonymous ,

Thank you for confirming the additional details.

Since the issue is reproducible only with the composite model, while the same AAS-to-Fabric repointing works successfully with a live connection, this does appear to be unexpected Power BI Desktop behavior rather than a connectivity or target semantic model issue.

However, the GetObjectTranslations stack trace alone is not sufficient to confirm the exact root cause or classify it as a confirmed product bug.

Could you please confirm whether you are using the latest version of Power BI Desktop? If so, please also share whether the issue can be reproduced with a newly created composite model using the same Model_V1 to Model_V2 repointing scenario. This will help further isolate whether the behavior is specific to the existing PBIX or reproducible across composite models.

I hope this helps.
Anonymous

2026-07-12T15:42:31.0233333+00:00

I've tried Jan, May & June 2026 (latest) releases of Power BI desktop.

I have tested creating completely new DirectQuery report from AAS, then repointing. Still same issue. It's something about the model name that is baked into the schema sync step. If not the same model name it's not being synced correctly
Srikanth Chavithina 265 Reputation points Microsoft External Staff Moderator

2026-07-13T08:53:54.3766667+00:00

Hi @Anonymous
Thank you for validating this across multiple Power BI Desktop versions and for testing with a newly created DirectQuery report.

Based on your findings, the issue does not appear to be related to a specific Desktop release or the original PBIX file. Since repointing succeeds when the target semantic model retains the same name but fails when both the server and model name change, the model-name change appears to be a key factor in reproducing the issue.

Given the consistent reproduction and the NullReferenceException occurring during model metadata processing, this appears to be unexpected behavior in the composite model repointing/schema synchronization workflow. However, the available information is not sufficient to confirm whether this is a current product limitation or a defect.

As a practical workaround, if possible, you can keep the target Fabric semantic model name aligned with the original AAS model name when repointing the report, since the server-only change succeeds in your testing.

Thank you for providing the detailed reproduction results. I hope this helps
Srikanth Chavithina 265 Reputation points Microsoft External Staff Moderator

2026-07-20T08:32:18.18+00:00

Hi Peter McInnes,
I hope you had a chance to review the information shared earlier and found it helpful.

If you still have any questions or need further clarification, please let us know in the comments so we can assist you further. We look forward to hearing from you.

Answer 1

hi Peter McInnes(Unifeye) & thx for sharing urs issue here at Q&A portal,

stack trace points to Power BI Desktop failing while synchronizing model translations after both the server and semantic model name are changed. That looks like a Desktop bug or a metadata mismatch, not a normal connection error. Try changing only the server first, save and reopen the PBIX, then change the database/model name. If that still fails, confirm that Model_V2 has the same table, column, measure, hierarchy, and translation metadata expected by the report. Changing the connection won’t remap objects when the target model schema differs. The exception is inside TranslationCollectionSynchronizationStep, removing stale translations from the PBIX or target semantic model may work around it. Testing with the latest Power BI Desktop build is also important.

Look at Microsoft’s AAS migration guid https://learn.microsoft.com/power-bi/guidance/migrate-azure-analysis-services-to-power-bi If Model_V1 and Model_V2 are schema-compatible and the latest Desktop still throws the same null reference, this should be reported as a Power BI Desktop bug with the PBIX, Desktop version, and a sanitized copy of both model schemas.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/

Anonymous

2026-07-10T14:51:06.2+00:00

There are no stale translations in the model. That seems to be erroneous error messaging. I have two models in the fabric workspace, 1 named the same as AAS cube Modelv1, and 1 Modelv2 which has the new naming convention I need. These two models are identical.

If I try and update the server name first, this succeeds, as it points to the same naming convention as the other one. But then if I then try and change the name the name, it no longer is the AAS connection type, it opens the OneLake Explorer, and it still gives me an error even if I now try to connect to new naming convention Modelv2

Answer 2

Hi Peter McInnes,

Thank you for sharing the details.

Since changing only the server endpoint from asazure:// to powerbi:// works, basic connectivity to the Fabric workspace appears to be working. The System.NullReferenceException at GetObjectTranslations is not a typical connection or authentication error; however, the stack trace alone is not enough to confirm a translation issue or Power BI Desktop defect.

I recommend updating Power BI Desktop to the latest version, testing a new PBIX connection directly to Model_V2, and verifying that the target model contains the objects required by the existing report. You can also try changing the server first, saving and reopening the PBIX, and then rebinding to Model_V2 separately instead of changing both values simultaneously.

If the issue persists, could you confirm whether this is a live connection or composite model, whether Model_V2 is a migrated copy of Model_V1, and whether a new PBIX can connect successfully to Model_V2?

This will help determine whether the issue is related to model compatibility, the connection-change scenario, or requires further Power BI Desktop investigation.

For reference, please see:

Migrate Azure Analysis Services to Power BI: https://learn.microsoft.com/en-us/power-bi/guidance/migrate-azure-analysis-services-to-power-bi
Connect to Analysis Services from Power BI Desktop: https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-analysis-services-tabular-data
Use composite models in Power BI Desktop: https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-composite-models

Hope this helps. If you have any questions or need further clarification, please let us know.