The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have a Data Pipeline in which I created a semantic model refresh activity and set up everything so all the required fields are set, i.e. the semantic model field. I also checked the json version of the pipeline and datasetId seems to be correctly set. Now, when I close the Data Pipeline and reopen it again, I see that the semantic model field is blanked out and I have pending changes to save. Also, the json version is now missing the datasetId field. I am opening this in a fresh incognito window so I don't think it is a browser cache issue.
Solved! Go to Solution.
Hi @dcrnojevac
I wanted to share some context and a possible workaround for the issue where the Semantic Model Refresh activity in a Data Pipeline appears to lose its configured semantic model after saving or reopening.
After setting up the activity (including the semantic model selection), everything seems fine at first. But once the pipeline is closed and reopened, the semantic model field shows up blank, and the datasetID also disappears from the JSON. Even opening the pipeline in an incognito browser didn’t prevent this.
From what I’ve observed, this seems to be a known behavior—possibly a UI bug or a syncing issue where the configuration doesn’t persist properly.
Here’s what helped in my case:
After selecting the semantic model, try clicking outside the component to let the UI register the change.
Then save the pipeline, publish it, and only then close the pipeline tab.
If the field still resets, you can open the pipeline in JSON view and re-add the datasetID manually, then re-save and publish.
If this still doesn’t work, an alternate approach is to trigger the semantic model refresh using a notebook or REST API call. It gives you more control and avoids depending on the UI entirely.
Hope this helps someone else facing the same problem. And if the issue continues, I’d recommend opening a support case with the Fabric team and sharing the pipeline export + screenshots—they’ll likely want to look into it deeper.
Happy to help further if needed!
Best Regards,
Cheri Srikanth
Hi @dcrnojevac
Thanks for your response.
If the issue has been resolved, can you mark the post as resolved? If you're still experiencing challenges, please feel free to let us know and we'll be happy to continue to help!
Best Regards,
Cheri Srikanth
Hi @dcrnojevac
We haven't heard from you since last response and just wanted to check whether the solution provided has worked for you. If yes, please Accept as Solution to help others benefit in the community.
Thank you.
If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
Best Regards,
Community Support Team _ C Srikanth.
Hi @dcrnojevac
I wanted to follow up since I haven't heard from you in a while. Have you had a chance to try the suggested solutions?
If your issue is resolved, please consider marking the post as solved. However, if you're still facing challenges, feel free to share the details, and we'll be happy to assist you further.
Best Regards,
Cheri Srikanth
Hi @dcrnojevac
I wanted to share some context and a possible workaround for the issue where the Semantic Model Refresh activity in a Data Pipeline appears to lose its configured semantic model after saving or reopening.
After setting up the activity (including the semantic model selection), everything seems fine at first. But once the pipeline is closed and reopened, the semantic model field shows up blank, and the datasetID also disappears from the JSON. Even opening the pipeline in an incognito browser didn’t prevent this.
From what I’ve observed, this seems to be a known behavior—possibly a UI bug or a syncing issue where the configuration doesn’t persist properly.
Here’s what helped in my case:
After selecting the semantic model, try clicking outside the component to let the UI register the change.
Then save the pipeline, publish it, and only then close the pipeline tab.
If the field still resets, you can open the pipeline in JSON view and re-add the datasetID manually, then re-save and publish.
If this still doesn’t work, an alternate approach is to trigger the semantic model refresh using a notebook or REST API call. It gives you more control and avoids depending on the UI entirely.
Hope this helps someone else facing the same problem. And if the issue continues, I’d recommend opening a support case with the Fabric team and sharing the pipeline export + screenshots—they’ll likely want to look into it deeper.
Happy to help further if needed!
Best Regards,
Cheri Srikanth
Hi @dcrnojevac
Sorry for the late response and inconvenience caused.
Could you please follow the below points that might resolve your issue.
If the above information helps you, please give us a Kudos and marked the Accept as a solution.
Best Regards,
Community Support Team _ C Srikanth.
Hi,
Sorry for the late response,
I tried the suggested fix, i.e. I created a test semantic model from scratch and a new Data Pipeline. Created a Semantic Model Refresh activity in it. Saved that and exited. Upon opening the pipeline again the Semantic Model Refresh activity has the 'Semantic Model' field blanked out again. The only difference now is the 'Semantic Model' field seems to be now a required field which won't allow me to save in this state and that is good.