Planning Analytics

Hi all, 

I wanted to raise a point regarding the deployment process in PAW's Lifecycle Management, specifically regarding the database mapping section. When deploying a snapshot, it's not entirely clear which databases correspond to the source and target sides. While I assume that the source is on the left and the target on the right, the process and outcome remain somewhat ambiguous.

It would be beneficial to provide clearer guidance or labeling within this section. For instance, explicitly stating the roles of the databases and what actions they trigger during deployment would enhance user understanding and confidence in the process.

Thank you for considering this suggestion for increased clarity in the deployment panel.

Cheers, Asgeir

Hi all, 

I wanted to raise a point regarding the deployment process in PAW's Lifecycle Management, specifically regarding the database mapping section. When deploying a snapshot, it's not entirely clear which databases correspond to the source and target sides. While I assume that the source is on the left and the target on the right, the process and outcome remain somewhat ambiguous.

It would be beneficial to provide clearer guidance or labeling within this section. For instance, explicitly stating the roles of the databases and what actions they trigger during deployment would enhance user understanding and confidence in the process.

Thank you for considering this suggestion for increased clarity in the deployment panel.

Cheers, Asgeir

Why is both the source and target environment called 'Default'?  That doesn't make sense.  Is this an on-premises deployment? 

Hi all, 

I wanted to raise a point regarding the deployment process in PAW's Lifecycle Management, specifically regarding the database mapping section. When deploying a snapshot, it's not entirely clear which databases correspond to the source and target sides. While I assume that the source is on the left and the target on the right, the process and outcome remain somewhat ambiguous.

It would be beneficial to provide clearer guidance or labeling within this section. For instance, explicitly stating the roles of the databases and what actions they trigger during deployment would enhance user understanding and confidence in the process.

Thank you for considering this suggestion for increased clarity in the deployment panel.

Cheers, Asgeir

Yes, this is an  on-premises deployment, PAW 2.0.95.

Why is both the source and target environment called 'Default'?  That doesn't make sense.  Is this an on-premises deployment? 

Hi all, 

I wanted to raise a point regarding the deployment process in PAW's Lifecycle Management, specifically regarding the database mapping section. When deploying a snapshot, it's not entirely clear which databases correspond to the source and target sides. While I assume that the source is on the left and the target on the right, the process and outcome remain somewhat ambiguous.

It would be beneficial to provide clearer guidance or labeling within this section. For instance, explicitly stating the roles of the databases and what actions they trigger during deployment would enhance user understanding and confidence in the process.

Thank you for considering this suggestion for increased clarity in the deployment panel.

Cheers, Asgeir

Are you sure you are not trying to deploy to the same environment the snapshot was created in?  Lifecycle Management allows you to deploy to the same environment you used to create the snapshot in order to allow you to duplicate content against a different database.  

Did you try changing the environment name to something other than Default?

Yes, this is an  on-premises deployment, PAW 2.0.95.

Why is both the source and target environment called 'Default'?  That doesn't make sense.  Is this an on-premises deployment? 

Hi all, 

I wanted to raise a point regarding the deployment process in PAW's Lifecycle Management, specifically regarding the database mapping section. When deploying a snapshot, it's not entirely clear which databases correspond to the source and target sides. While I assume that the source is on the left and the target on the right, the process and outcome remain somewhat ambiguous.

It would be beneficial to provide clearer guidance or labeling within this section. For instance, explicitly stating the roles of the databases and what actions they trigger during deployment would enhance user understanding and confidence in the process.

Thank you for considering this suggestion for increased clarity in the deployment panel.

Cheers, Asgeir

I intended to create a copy of the life for testing, both the PAW user interface and the TM1 model/server. 
All TM1 models Test/Live run on the same Windows 2016 server. 

I created the snapshot just before I deployed and it worked fine. 
I did not try to change the environment name. 

Are you sure you are not trying to deploy to the same environment the snapshot was created in?  Lifecycle Management allows you to deploy to the same environment you used to create the snapshot in order to allow you to duplicate content against a different database.  

Did you try changing the environment name to something other than Default?

Yes, this is an  on-premises deployment, PAW 2.0.95.

Why is both the source and target environment called 'Default'?  That doesn't make sense.  Is this an on-premises deployment? 

Hi all, 

I wanted to raise a point regarding the deployment process in PAW's Lifecycle Management, specifically regarding the database mapping section. When deploying a snapshot, it's not entirely clear which databases correspond to the source and target sides. While I assume that the source is on the left and the target on the right, the process and outcome remain somewhat ambiguous.

It would be beneficial to provide clearer guidance or labeling within this section. For instance, explicitly stating the roles of the databases and what actions they trigger during deployment would enhance user understanding and confidence in the process.

Thank you for considering this suggestion for increased clarity in the deployment panel.

Cheers, Asgeir