Forum Discussion
Data Pipeline Semantic Model Refresh - Tables not loading
Hello,
I am trying to set up a semantic model refresh in a data pipeline using Smenaitc Model Refresh activity. But when I fill out the settings including Connection, Workspace, Semantic model, under Table(s) option it says "No results found". The semantic model has one table and the data source is lakehouse, connected using the SQL endpoint. It doens't seem like a permission issue because I created the connection in the data pipeline activity using my own user which has Fabric Tenanat admin permissions. Tried changing different semantic models, different data sources still no luck. Any suggestion on how to figure this out?
Thanks a lot!
thanks, the 2nd option helped. The json is strcuture is like this.
@json('[{"table": "YourTableName"}]')It is a strange workround. I wonder whether there is a permanant solution for this.
7 Replies
Hi hasithae
it could be a ui issue. Try another browser ot incognito.
if nothing works ,
If the UI fails to load tables, manually specify them using dynamic JSON:@json('
{
"table": "YourTableName"
}
')This bypasses the UI dropdown and forces a refresh of the specified table
thanks, the 2nd option helped. The json is strcuture is like this.
@json('[{"table": "YourTableName"}]')It is a strange workround. I wonder whether there is a permanant solution for this.Is your table hidden?
Hi hasithae
Thank you for being part of the Microsoft Fabric Community.
As highlighted by nilendraFabric , the proposed approach appears to effectively address your requirements. Could you please confirm if your issue has been resolved?
If you are still facing any challenges, kindly provide further details, and we will be happy to assist 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.I have this exact same issue too. I can confirm the solution works, but hardcoding table names in a pipeline when you want all the tables in the model to be refreshed doesn't seem like a good practice. If a new table is added to the model, I need to remember to update the refresh in the pipeline too. Is this a known issue, I was not able to find it.
Has anyone found a reason as to why this occurs?
