Forum Discussion
Update PowerBI Connection from AAS to Fabric
I'm trying to change the connection details for a powerbi directquery report locally (June 2026 Power BI desktop version). 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":""}
Thankyou rajendraongole1 for Addressing the issue.
Hi PMcInnes ,Thank you for reaching out to Microsoft Fabric Community Forum, below are the few debug points which might resolve your issue.
- The error appears to be an internal Power BI Desktop issue (System.NullReferenceException in GetObjectTranslations) rather than a connection or authentication issue.
- Verify that the source and target semantic models have identical schemas, including tables, columns, measures, hierarchies, calculation groups, perspectives, and translations.
- Confirm that the target semantic model is accessible by creating a new Power BI Desktop report and connecting directly to the semantic model via the XMLA endpoint.
- Verify that the XMLA endpoint is enabled and that you have the required permissions on the target workspace and semantic model.
- Update to the latest version of Power BI Desktop, as the issue may have been addressed in a newer release.
- Clear the Power BI Desktop cache and sign out/sign back in before retrying the connection change.
- If changing only the server works but changing both the server and semantic model fails, it is likely a limitation or product issue in Power BI Desktop.
- As a workaround, create a new PBIX connected directly to the target semantic model and migrate the report pages if the model schemas are identical.
- If the issue persists after completing the above steps, collect the PBIX file, Power BI Desktop version, and diagnostic logs, and open a Microsoft Support ticket for further investigation.
Below is the link to create a support ticket.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thanks,
Chaithanya.
5 Replies
- rajendraongole1
Super User
Hi PMcInnes - Looks like a Power BI Desktop issue rather than a limitation of connecting to a Fabric semantic model. The NullReferenceException in GetObjectTranslations suggests Desktop is failing while remapping the report metadata when both the server and semantic model name are changed at the same time.
can you share more details:
is Model_V2 structurally identical to Model_V1 (same tables, columns, measures, hierarchies, calculation groups, etc.)?
check and let us know
Yes exactly the same model. Tried just renaming Model_v1 to Model_v1.1 in the pbi workspace and connecting, but same issue
v-kathullacCommunity Support
Thankyou rajendraongole1 for Addressing the issue.
Hi PMcInnes ,Thank you for reaching out to Microsoft Fabric Community Forum, below are the few debug points which might resolve your issue.
- The error appears to be an internal Power BI Desktop issue (System.NullReferenceException in GetObjectTranslations) rather than a connection or authentication issue.
- Verify that the source and target semantic models have identical schemas, including tables, columns, measures, hierarchies, calculation groups, perspectives, and translations.
- Confirm that the target semantic model is accessible by creating a new Power BI Desktop report and connecting directly to the semantic model via the XMLA endpoint.
- Verify that the XMLA endpoint is enabled and that you have the required permissions on the target workspace and semantic model.
- Update to the latest version of Power BI Desktop, as the issue may have been addressed in a newer release.
- Clear the Power BI Desktop cache and sign out/sign back in before retrying the connection change.
- If changing only the server works but changing both the server and semantic model fails, it is likely a limitation or product issue in Power BI Desktop.
- As a workaround, create a new PBIX connected directly to the target semantic model and migrate the report pages if the model schemas are identical.
- If the issue persists after completing the above steps, collect the PBIX file, Power BI Desktop version, and diagnostic logs, and open a Microsoft Support ticket for further investigation.
Below is the link to create a support ticket.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thanks,
Chaithanya.
- v-kathullac
Thankyou rajendraongole1 for Addressing the issue.
Hi PMcInnes ,Thank you for reaching out to Microsoft Fabric Community Forum,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
Chaithanya
- v-kathullac
Thankyou @rajendraongole1 for Addressing the issue.
Hi @PMcInnes ,Thank you for reaching out to Microsoft Fabric Community Forum,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
Chaithanya
