Skip to main content
Announcements
Qlik Connect 2025! Join us in Orlando join us for 3 days of immersive learning: REGISTER TODAY

Jobs with same ID were not loaded into Talend Studio

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Uma_Ganesh
Support

Jobs with same ID were not loaded into Talend Studio

Last Update:

Sep 23, 2024 3:19:01 AM

Updated By:

Shicong_Hong

Created date:

Sep 23, 2024 4:33:18 AM

After merging feature branches into the main branch in Talend Studio, several Jobs are not displayed correctly. Some Jobs are missing, while others contain incorrect files. Additionally, when importing Jobs with the same ID into Talend Studio, the following error message is displayed.

The 2 following items have the same ID, please unselect one of them:

import_items_error.png

 

Cause

Upon comparing the properties files of two Jobs, it was discovered that both Jobs contain the same ID. Talend Studio is unable to import Jobs with the same ID.

properties.png

 

Resolution

Please do not attempt to manually change the ID as it may lead to other dependency issues. Instead, follow the steps below to import these two Jobs that have the same ID.

  1. Import the first Job to avoid the duplicate error.import_first_job.png
  2. Then, right-click on the Job and select "Duplicate" to create a duplicate Job.duplicate.pngduplicate_job.png
  3. Delete the original Job.delete_job.png
  4. Empty the Recycle bin.recycle_bin.png
  5. Import the second Job.import_second_job.png
  6. Rename the duplicated Job back to its correct name.rename_duplicated_job.png
  7. Now, the two Jobs have different ID.different_id.png

 

Environment

Labels (2)
Comments
MattE
Creator II

We're trying to do this but the conflict is happening with 100s of files, too many to do via this manual method. Any advice on what to do? Talend studio 8.0.1 R2024-10

Xiaodi_Shi
Support

Hello @MattE 

Normally with Studio, if any item has conflict,  Studio will go to talend conflict view and let user handle the merge. Then studio can handle the resign of artifact(.item) automatically.

Note: We only support the merge in studio right now, not outside of studio with manual PR and conflicts should be transparent for final user as long as it's merged inside studio and not in other tool.

Here is online documentation about:

https://help.qlik.com/talend/en-US/studio-user-guide/8.0-R2024-10/resolving-conflicts-between-branch...

Hope it helps.

Best regards

Sabrina