Semantic mode connection issue

[Anonymous]

Hi everybody! 
I've 2 reports (Report A & Report B), with following semantic models (Semantic A & Semantic B).
I connected to my Report B to Semantic A (storage mode: mixed, direct query).
But after publishing it users receiving following error (for visuals which use columns\rows\measures from Semantic A):

But if I send users link to Report A, they open it, and after that error in Report B disappears. 

Both Report shared with 'People in your organization' read and reshare.

I'm trying to build efficient workspace, with minimum duplication of data, which I believe can be achivied with reusing data and connect all my future reports to already exist Semantic models. Could you please advise what I need to do, to be able to create new reports with connection to existing Semantic models without sending them links to used semantic models. 

THank you in advance! 

[v-prasare]

@Anonymous, Thanks for reaching out Microsoft community Support,

in addition to @Poojara_D12 mentioned.

Please consider below points while connecting Report B to Semantic A:

• Ensure the structures of Semantic Model A and Semantic Model B (tables, fields, measures) align with the needs of both reports. If they don’t align, you might need to update the reports or extend the models.
• If a report uses a measure or field that doesn’t exist in the new semantic model, those visuals may break and need to be updated.
• If Report A and Report B require data from both Semantic Model A and Semantic Model B, consider using DirectQuery for Power BI Datasets to combine the models within the report.

The issue you're describing indicates a dataset permission or initialization problem when using Semantic A in Report B. The fact that opening Report A (which directly connects to Semantic A) resolves the issue temporarily suggests that Semantic A’s dataset permissions or initialization needs to be properly configured for Report B. Can you please try below steps:

Grant Explicit Access to Semantic A Dataset

1. Go to Power BI Service and locate Semantic A in the workspace.
2. Click on the ellipsis (...) next to the dataset and choose Manage Permissions.
3. Ensure that all users who need access to Report B have explicit permissions for Semantic A

 Update the Report’s Dataset Permissions

1. Open Report B in Power BI Desktop.
2. Navigate to File > Options and Settings > Data Source Settings.
3. Select the connection to Semantic A, click Edit Permissions, and ensure that credentials match what is used to access Semantic A.

Once the above steps are done:

1. Test if users can open Report B directly without errors.
2. Confirm they can use all visuals that rely on Semantic A.
3. Check if they can build new reports connected to Semantic A without issues.

To minimize duplication and ensure efficient workspace management:

• Create a dedicated workspace for your semantic models (e.g., Data Models Workspace).
• Publish all semantic models (like Semantic A and Semantic B) to this workspace.
• Share the models with all users or groups who need access.
• Build reports in a separate workspace and connect them to these shared datasets.

This approach centralizes the models, improves management, and avoids permission conflicts.

Did I answer your question? Mark my post as a solution, this will help others!

If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 

Thanks,
Prashanth Are

[Poojara_D12]

Hi @Anonymous 

Please try the below points:

1. Grant Permissions on Semantic A:

   • Ensure users of Report B have view access to Semantic A in the Power BI Service.
   • Go to Semantic A > Manage Permissions, and explicitly share with users or groups.

2. Enable Build Permissions (Optional):

   • If users might create reports based on Semantic A, grant Build permissions under Manage Permissions.

3. Keep Reports in the Same Workspace:

   • Publish Report B and Semantic A in the same workspace to simplify access.

4. Use Power BI Apps:

   • Package reports into a Power BI App for easier access and automatic permission inheritance.

5. Test User Access:

   • Use a test account to ensure users can open Report B directly without errors.

This will eliminate the need to send links for users to initialize access.

Did I answer your question? Mark my post as a solution, this will help others!

If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂

Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Please Subscribe my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS 

[Anonymous]

Dear Poojara,
Already checked everything you meantionted above, some errors

[v-prasare]

Hi @Anonymous,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution i provided for your issue worked? or let us know if you need any further assistance here?

Your feedback is important to us, Looking forward to your response. 

Thanks,

Prashanth Are

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query.

[Anonymous]

Hi Prashanth! 
Unfortunately no. 
Users need to open Report A, and only after that eror disappear

[v-prasare · Accepted solution]

Hi @Anonymous,

Sorry for delayed response here. since, your issue still persists.

please raise a support ticket here with Fabric Power BI team: How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thanks,

Prashanth Are

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query.

[v-prasare]

@Anonymous, from above discussion this seems like by design, dataset permission or initialization problem when using Semantic A in Report B and opening Report A (which directly connects to Semantic A) resolves the issue temporarily it suggests that Semantic A’s dataset permissions or initialization. 

if you are not satisfied with answer, please raise a support ticket here with Fabric Power BI team

Thanks,

Prashanth Are

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query.