cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
ashutosh28gupta Frequent Visitor
Frequent Visitor

Power BI dashboard has suddenly stopped loading with in CRM

Power BI dashboard not visible from within Dynamics 365  Power BI dashboard page anymore. The error is showed below.  I had a power BI dashboard configured to be accessed from within CRM which was working fine until this morning. Though, I can access the report and dashboard through the Power BI service link. 

Kindly suggest, what is wrong with the service. Thank You. 

 

 Power BI Error.png

1 ACCEPTED SOLUTION

Accepted Solutions
Community Support Team
Community Support Team

Re: Power BI dashboard has suddenly stopped loading with in CRM

Hi @ashutosh28gupta,

 

Is there any particular on your power bi contents? I haven't found any similar issues which other user submitted.

Can you please share more detailed information about you scenario?

 

Regards,

Xiaoxin Sheng

Community Support Team _ Xiaoxin Sheng
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.



For learning resources/Release notes, please visit: | |
2 REPLIES 2
Community Support Team
Community Support Team

Re: Power BI dashboard has suddenly stopped loading with in CRM

Hi @ashutosh28gupta,

 

Is there any particular on your power bi contents? I haven't found any similar issues which other user submitted.

Can you please share more detailed information about you scenario?

 

Regards,

Xiaoxin Sheng

Community Support Team _ Xiaoxin Sheng
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.



For learning resources/Release notes, please visit: | |
ashutosh28gupta Frequent Visitor
Frequent Visitor

Re: Power BI dashboard has suddenly stopped loading with in CRM

Hi @v-shex-msft

 

The whole power BI dashboard link in Dynamics 365 was not accessible from CRM only though it was available from Power Bi service. Anyway, the issue got resolved automatically. It seems MS support team took some action at their end to resolve the error. 

 

Thank you for your response.