CMS Application - Current Version - Unexpected Results - Bad deployment path for some deployed packages

Description

When examining the deployment path of the deployed packages, sometime, the deployment path of some deployed packages is wrong as below example :

In the above example, the deploy path is S:\Sources\SAMS, and for two deployed packages, the deploy path is S:\Sources\SAMS_13782

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Step by Step Scenario

Package the source code
Deliver
Accept and set as current version
Check the deployment path of the deployed packages

Action Plan

Deploy sources and set as current version
Quit CAST-MS
Run a SQL session using pg-admin
Configure and execute the following query :

update <XXX_MNGT>.cms_portf_application set deploypath = replace(deploypath, ‘<ORIGINAL_PATH>’, ‘<NEW_PATH>’) –<XXX_MNGT> is the management schema name. –<ORIGINAL_PATH> is the path which has to be changed. –<NEW_PATH> is the deployment path.

5. Ensure the 2 paths are ending with '\' (folder separator) to avoid having issues with substring folder names.

   **Example**

   For the below example, the query will be :

   ![](https://doc-data.castsoftware.com/TG/attachments/566532517/566532516.png)

update <XXX_MNGT>.cms_portf_application set deploypath = replace(deploypath, ‘S:\Sources\SAMS 13782', ‘S:\Sources\SAMS')

6. Open CAST-MS and check that the deployment path of the deployed packages are now correct.
7. If the above points do not help you solve the issue, contact [CAST Technical Support](https://help.castsoftware.com/hc/en-us/requests/new) with the [relevant input](/export-v2/tg/technical-guides/technical-guides-by-cast-aip-component/cms-application-component/) in order to reproduce the issue.

**Notes/comments**

Ticket # 6602

**Related Pages**