Forum Discussion
Semantic model refresh pipeline activity
I have a pipeline which is as follow:
app refers to staging layer
ptf refers to bronze layer
ent refers to silver layer
vis to gold
Currently the screenshot is from test worksapce , but the "connection" used in semantic model activity is the one I created in dev workspace. I see it works and pipeline run successfully, hence we need not to create seperate connections for the semantic model refresh activity for each dev - test- prod workspace respectively. Beacuse in prod I created a seperarte connection for it.
Hi IAMCS
The semantic model refresh activity uses the same connection that was set up during configuration. If that connection has the right permissions in all your dev, test, and prod workspaces, it can be used across environments without any issue. That’s why your pipeline runs successfully in the test workspace using the dev connection.
However, creating a separate connection for production, as you did, is a smart choice. It keeps your environments isolated, helps avoid accidental refreshes, and makes managing access much easier. So yes, one connection can technically work everywhere, but keeping a separate one for prod is definitely the better and safer setup.
1 Reply
Hi IAMCS
The semantic model refresh activity uses the same connection that was set up during configuration. If that connection has the right permissions in all your dev, test, and prod workspaces, it can be used across environments without any issue. That’s why your pipeline runs successfully in the test workspace using the dev connection.
However, creating a separate connection for production, as you did, is a smart choice. It keeps your environments isolated, helps avoid accidental refreshes, and makes managing access much easier. So yes, one connection can technically work everywhere, but keeping a separate one for prod is definitely the better and safer setup.