cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Best Approach for Changing Connection from Quality to Production in SAP Analytics Cloud

kastolia
Explorer
0 Kudos
480
Hello everyone,  
 
I would like your advice on the following issue. We have a customer with only one SAP Analytics Cloud (SAC) tenant, the production one, without a test environment.  
 
We started implementing some dashboards using S/4 data, based on the Quality system connection. As a result, we built the data models and corresponding stories using the Quality connection.  
 
Now that we are in the UAT phase, we are wondering what the best approach would be to change the connection from Quality to Production without having to create the models and stories from scratch. Ultimately, we aim to have two versions of the stories, one with Quality data and another with Production data.  
 
Any guidance or best practices would be greatly appreciated!  
 
Thank you in advance.
View Entire Topic
William_Yu1
Product and Topic Expert
Product and Topic Expert
0 Kudos

If the vision to have two set of stories for quality and production data separately, you definitely need to set of models as well. Try this: 

  1. Create two live models on two different connections, one to quality and one two production. 
  2. Create copy of test story to production story 
  3. Replace model in production story with production model. 

 

 

kastolia
Explorer
0 Kudos

Hello William,

Thank you for your reply.

However, it seems that it dosen't work for us 😞

I forgot to mention that the data models are not live but reply on an import connection that includes various transformations. There are more than 30 data modes, so it would be an overhead to recreate them all from scratch. Also, copying the model wouldn't help because queries are not transferred in the copy.

Is there any other idea?  

William_Yu1
Product and Topic Expert
Product and Topic Expert

Ok, import connection is a bit different story. If you don't want to recreate all the import job, maybe the only option is to swap the system URL information in the connection used by import jobs. But in this case, you will always have only one set of objects( models, stories) at a time, either quality or production.