Forum Discussion
Helper ISemantic model refresh pipeline activity
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.
Super UserHi 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.