This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
adarshhs
Level 2
‎Sep 28, 2023 06:25 AM

[Code Insight 6.x] Issue with Updating Existing Project on Palamida Tool Using Java API createOrUpdateProject

Dear Support,

I'm encountering an issue with the Palamida tool's Java API createOrUpdateProject. Instead of updating the 'teamName' in an existing project, it's creating a new project with the same name and new 'teamName'. This is causing project duplication and workflow disruption.

Could you please assist in resolving this issue? What I need is a way to change teamName of an existing project through JavaAPI.

Code Snippet:

aSrv.createOrUpdateProject(projectName, projectDescription, teamName, ownerUserName)

Only teamName is changed each time and rest of the parameters are kept same

Screenshot for reference:

 
 

error.JPG

 

 

Labels (1)
Labels

(2) Replies
adarshhs
Level 2
‎Sep 28, 2023 06:28 AM

@tphamda This is a follow-up issue from this ticket - https://community.flexera.com/t5/Code-Insight-Forum/Code-Insight-6-x-How-to-change-Team-of-a-project-using-rest-APIs/m-p/292411#M411 

Would you be able to help me on this.

0 Kudos
tphamda
Level 6 Flexeran
Level 6 Flexeran
In response to adarshhs
‎Oct 06, 2023 06:01 PM

Hi @adarshhs,

Apologies for the delay. I was able to reproduce the same behavior you are seeing. Unfortunately, this looks to be either a documentation issue or a bug with the API. Currently, updating the project with the API works if you keep the project name AND the team name the same. 

As Code Insight v6 will be reaching the end of its standard lifecycle before the end of the year, we will unlikely be able to address this issue as our main focus for v6 would only be to address critical issues. If you believe this is a critical issue for you, please open a support case with us for further assistance. Otherwise, we would recommend planning to migrate to Code Insight v7.