Pipline update semantic model failed

[Si3rco]

In a pipeline the Semantic model is not updating, it’s failed.

The new field dropdown in Table(s) are loading in loop and show no content. Please help.

[v-karpurapud]

Hello @Si3rco 

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[Si3rco · Accepted solution]

Hey Problem is resolved.

I had to remove the connection and log in again.

Unfortunately, there was no clear error message for this behavior.

Thank you.

[v-karpurapud]

Hi @Si3rco

Thanks for reaching out to Microsoft Fabric Community Forum.

To address the issue of a pipeline failing to update the semantic model, follow these troubleshooting steps:

1. Check Connection Strings:

    Ensure that the connection strings used in the pipeline are correctly configured. The error suggests that the          pipeline cannot resolve the connection, which may be due to incorrect credentials.

2. Data Source Permissions:

   Confirm that the user account running the pipeline has sufficient permissions to access the data source. This includes read permissions on the data and at least Contributor or Owner access to the workspace and model.

3. Address Table Dropdown Loading Issue:

    Ensure that the Semantic Model is published and accessible. Refresh the connection in the pipeline settings.

4. Schema Issues:

    If the dropdown still doesn’t load, check for schema issues in the semantic model.

5. Reconfigure Pipeline Activities:

   Remove and then re-add the refresh activity for the semantic model.

If you continue to experience issues after following all the troubleshooting steps, consider raising a Microsoft support ticket as recommended by @Anonymous .

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.

Thank You.

[Anonymous]

You would need to open a support case with microsoft to get this resolved.