Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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

Post 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 product management 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 notification 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Planned for future release
Created by Guest
Created on Nov 17, 2020

Request for addition of Group Processing Functionality in Virtual MDM at

We had discussed in past on the availability of group processing functionality and IBM MDM Advocate: Effy Wu confirmed that this functionality no longer exist in MDM version11.6.0.11.

We would like to get IBM's recommendations on the alternative possible approach for this. Below is the use case for our application :

1. We are moving our system from daily batch feeds to real time event based transactions. We are utilizing Event Notification framework for the member/entity changes in MDM and sending to downstream.

2. We usually get member add/update transactions from our source systems. We don’t have much issue with Member update as MDM just generates only one event.

3. We are seeing 3 events getting generated if a new member gets enrolled in MDM (Member created, Member Updated and Member Linked). Most of the time the data on these 3 events are same except the member event type.

4. Our down streams are complaining of duplicate messages from MDM because of scenario explained in step # 3

5. We also see this as a major concern because if MDM gets 1 Million member added to its DB then MDM will generate 3M events for downstream and that’s going to take time to get processed by our downstream systems.

Needed by Date Dec 31, 2020
  • Admin
    MAY LI
    Nov 24, 2020

    Hi Ashok,

    IBM's long time partner IMT has created a post-entity management handler that cleans up the multiple events generated from a single incoming transaction.

    Please feel free to reach out to Mark - I have shared his contact information below.

    Mark D. Holmes

    VP Solutions Engineering


    +1 519 615 1067

    Thank You

  • Guest
    Nov 20, 2020

    This is a problem we see all the time at IMT. You should indicate if you need this for synchronous or asynchronous entity management as that changes the complexity of the solution.

    The thing is that there was nothing wrong with the Group Processing implementation they had before. We used it for many clients. It's unfortunate IBM said they removed it because they said they were not aware of anyone who used it.

    Without group processing we cannot determine what happened in MDM to send a single message outbound.

    We have solved this internally using custom handlers but custom code is more difficult for customers to maintain.

  • Admin
    MAY LI
    Nov 19, 2020

    Thank you, Ashok, for submission. We will investigate and follow up here with status.