Fabric Link few Tables showing error

[Dinosauris]

Hello,

I am using the Fabric link for my dataverse environment. The process of initialization takes super long (already a few days) and on some of the tables an error appears when checking in PowerApps the status of the Link. When clicking on the error, nothing is shown, only a blank page. 

What can I do about it or how can I check what could be the issue? Below is a Screenshot of one table. 

This is a screenshot of the properties of the table:

[Anonymous]

Hi @Dinosauris 
Thanks for using Fabric Community.

Here are a few things you could try:

Check the size of your data:
If your data is too large, it could be causing the slow initialization. You might want to consider optimizing your data.

Check your capacity region:
Make sure that your capacity region matches the Dataverse environment. If they don’t match, you might need to create a new environment with the correct region using the Microsoft.PowerApps.Administration.PowerShell module in PowerShell.

Check your permissions:
Ensure that you have the necessary permissions to create Fabric artifacts. You might need to be a Power BI Capacity Administrator or have contributor access to a capacity within the same region as the Dataverse environment.

Check your license:
A Power BI premium license or Fabric capacity within the same Azure region as your Dataverse environment is required.

You can refer to these threads for more help:
Connection to dataverse extremely slow - Microsoft Fabric Community
Solved: Linking Power Apps to Fabric - Microsoft Fabric Community
Link your Dataverse environment to Microsoft Fabric and unlock deep insights - Power Apps | Microsof...

Hope this helps. Please let me know if you have any further questions.

[Anonymous]

Hi @Dinosauris 
We haven’t heard from you on the last response and was just checking back to see if your query got resolved. Otherwise, will respond back with the more details and we will try to help.
Thanks

[Anonymous]

Hi @Dinosauris 
We haven’t heard from you on the last response and was just checking back to see if your query got resolved. Otherwise, will respond back with the more details and we will try to help.
Thanks