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 Not under consideration
Created by Guest
Created on Apr 3, 2018

Event Manager and Entity Manager need to work in coordination to prevent update and merge timing issue.

Based on our findings and the confirmation from IBM support we have submitted this RFE to address this problem.

We found an issue in MDM event notification which can impact downstream systems that rely on MDM EID. This is a timing issue and only occurs when an update (MemPut) to a member is followed by a merge (MemMerge) to same member within few seconds. What we see in an update event message is the new EID assigned by Merge transaction, this update event message fails in downstream system as they are not aware of this new EID assigned to the member. The merge message has the Previous entrecno and New entrecno which makes them know the EID change but since update was done before merge this breaks the flow. Detailed scenario is mentioned in Use Case below. Currently seems like Entity Manager and Event Manager work independently as a separate process which seem to be causing this issue. Some type of work co-ordination has to happen to prevent this issue.

We identified this issue in Case TS000111960.
  • Admin
    Marcus Boone
    May 16, 2019

    Thank you for submitting this request.  We will take this under consideration as part of the modernization of MDM currently underway.