Forum Discussion
Model refresh activity forgets model (dataId can not be empty)
Hello everyone,
I configure a model refresh activity in a pipeline, save it (no error), close the pipeline, reopen it, and the model selection is gone (connection and workspace selection remain). This currently, for one week now, happens consistently across users, models, pipelines and workspaces. If such a pipeline is run, the error is "dataId value can not be null or empty" (duh, you couldn't even save it like that, I suppose).
What is going on? Can anyone help me? Thanks in advance!
- Anonymous1 year ago
Hi NotebookEnjoyer ,
Thank you for reaching out to us!
The error "dataId value cannot be null or empty" when running the pipeline is a natural consequence of this, since the model selection isn’t being retained. While this issue is not currently listed in the Microsoft Fabric Known Issues, please follow the workaround to help you move forward:- After reopening the pipeline, reselect the model in the Semantic Model Refresh Activity, save it again, and run it without closing the pipeline. This may ensure the dataId is included for that session.
A similar issue has been discussed here and might provide more insights:
https://community.fabric.microsoft.com/t5/Data-Pipeline/Pipeline-doesn-t-save-changes-to-Semantic-model-refresh-Activity/m-p/4623987
If this helps,consoder accepting it as solution.
Regards,
Pallavi. - After reopening the pipeline, reselect the model in the Semantic Model Refresh Activity, save it again, and run it without closing the pipeline. This may ensure the dataId is included for that session.
4 Replies
- AnonymousNot applicable
Hi NotebookEnjoyer ,
Thank you for reaching out to us!
The error "dataId value cannot be null or empty" when running the pipeline is a natural consequence of this, since the model selection isn’t being retained. While this issue is not currently listed in the Microsoft Fabric Known Issues, please follow the workaround to help you move forward:- After reopening the pipeline, reselect the model in the Semantic Model Refresh Activity, save it again, and run it without closing the pipeline. This may ensure the dataId is included for that session.
A similar issue has been discussed here and might provide more insights:
https://community.fabric.microsoft.com/t5/Data-Pipeline/Pipeline-doesn-t-save-changes-to-Semantic-model-refresh-Activity/m-p/4623987
If this helps,consoder accepting it as solution.
Regards,
Pallavi. - After reopening the pipeline, reselect the model in the Semantic Model Refresh Activity, save it again, and run it without closing the pipeline. This may ensure the dataId is included for that session.
- jagdishwagh0909Helper I
When I ran the semantic model refresh using a Fabric Data Factory activity by directly passing the semantic model name, it worked fine. However, when I try to pass the semantic model name as a dynamic content parameter, it doesn’t work.This is working without any issuehere I am passing as dynamic content as semantic model name but its not working
- NotebookEnjoyerAdvocate II
Interesting find, but in my situation the pipeline forgets an un-parameterized model.
- jagdishwagh0909Helper I
Dynamic Content Error – datasetId value should be in a valid GUID format.
I identified the issue: when I pass dynamic content for the semantic model name using Lookup and ForEach, the input for the semantic model activity appears as follows:
json
{ "method": "post", "waitOnCompletion": true, "commitMode": "Transactional", "operationType": "SemanticModelRefresh", "groupId": "7eaf3bc1-1d0c-43d9-bcbf-13b1195cb9a5", "datasetId": "sm_sales_reporting" }
However, when I pass a single model name as a hardcoded value, the datasetId is a valid GUID:json
{ "method": "post", "waitOnCompletion": true, "commitMode": "Transactional", "operationType": "SemanticModelRefresh", "groupId": "7eaf3bc1-2d0c-43d9-bcbf-12b1195cb9a5", "datasetId": "06ef7ab3-2b0d-4ef7-8772-2a94ed817a2e" }
So, the error occurs because the dynamic content is providing the semantic model name instead of its GUID (which is required for datasetId). You'll need to ensure the GUID of the semantic model is retrieved and passed dynamically, not the name.