IBM Sterling Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Job Status >>> Job Item Summary enhancement for failed codelist due to duplicate entries

We have request from customers like VF Services to update new codelist entries (more then 100 +) for an already existing codelist .

For such request Support/PER/Implementer would normally take the back up of the existing codelist (XML) and merge the new entries into the already existing codelist (XML)and try to deploy consolidated codeist (XML) in config center.

During this process it was observed if there are any duplicates in the consolidated codelist (XML) the import fails and Job >> Job Item Summary shows only one entry as duplicate, But it would not reflect all the duplicate entries present in the consolidated codelist (XML) and to remove these duplicates becomes tedious process.

For any codelist import failure due to duplicates If Job Item Summary can reflect list of all duplicate entries in the consolidated codleist (XML) then it would be easy to remove these entries and upload to config center.

This Job Item Summary enhancement would avoid frequent failures on config center and their by reducing load on the server. It would help Support/PER/Implementer to save time and address customer request at the earliest.

Note: In Sterling Integrator we have this feature, During import if there are any duplicates it would reflect all the duplicates present in the codelist xml.



  • Guest
  • Jun 28 2021
  • Not under consideration
What is your industry? Retail
How will this idea be used?

We have request from customers like VF Services to update new codelist entries (more then 100 +) for an already existing codelist.

For such request Support/PER/Implementer would normally take the back up of the existing codelist (XML) and merge the new entries into the already existing codelist (XML)and try to deploy consolidated codeist (XML) in config center.

During this process it was observed if there are any duplicates in the consolidated codelist (XML) the import fails and Job >> Job Item Summary shows only one entry as duplicate, But it would not reflect all the duplicate entries present in the consolidated codelist (XML) and to remove these duplicates becomes tedious process.

For any codelist import failure due to duplicates If Job Item Summary can reflect list of all duplicate entries in the consolidated codelist (XML) then it would be easy to remove these entries and upload to config center.

This Job Item Summary enhancement would avoid frequent failures on config center and their by reducing load on the server. It would help Support/PER/Implementer to save time and address customer request at the earliest.

Note: In Sterling Integrator we have this feature, During import if there are any duplicates it would reflect all the duplicates present in the codelist xml.



  • Admin
    Jim Luneke commented
    22 Sep 05:03pm

    Thank you for submitting this request. To date this has not been targeted as an enhancement that will be delivered in the near-term and as a result we are closing this request.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.