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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Functionality already exists
Created by Guest
Created on Jan 21, 2020

Unlimited field length for MDM

Client has MDM and EPIC. They have already extended the field length once but changes in EPIC mean they are sending fields with more characters than MDM supports so they get truncated. The request is to allow for unlimited field length in MDM. They are on 11.6.0.8

  • Admin
    Marcus Boone
    Feb 27, 2020

    Hi Carine

    We have enabled users to roll in their own custom models under different names than mpi_memname. For example they can see mpi_pername in party template and they may change the columns to any reasonable length of their choice.

    If you want to increase the length of some columns in mpi_memname, you would need to define a custom segment (let’s say mpi_customename), according to your need. Then perform an ETL to move their current data from mpi_memname to that new table.

    We have a number of services options from IBM and business partners that could assist with this and other enhancements if it is something your team is not comfortable implementing directly.

  • Guest
    Feb 26, 2020

    Hi Marcus,

    This RFE is for those hardened proprietary model tables. Our new business requirement is  to increase field length on names on mpi_memname and mpi_memelig and address information on mpi_memaddr.

  • Admin
    Marcus Boone
    Feb 25, 2020

    Hi Carine,

    Virtual MDM offers model-driven deployment, in which the users will specify the column size, along with other specifications. Please note this same flexibility will not apply to the hardened proprietary model (like mem_attr, mem_date, etc…), due to their generic implementation. Using MDM workbench, you will have the option to define your data model specification, according to your specific requirements.

  • Guest
    Feb 17, 2020

    Is this supported for MDM standard (i.e. virtual)?

    We are currently using Virtual MDM.

  • Admin
    Marcus Boone
    Feb 17, 2020

    HI Carine

    This is already supported, clients can modify the column size to fit their data, see the link in KC:

    https://www.ibm.com/support/knowledgecenter/SSWSR9_11.6.0/com.ibm.mdmhs.dev.platform.doc/concepts/c_customizingcolumnsizefortextdata.html

    If the request is to make the size unlimited length, that is not a best practice for relational databases.

  • Guest
    Jan 22, 2020

    EPIC is allowing unlimited characters for name fields "last name and first name" and we would like to be able to configure the length of these fields to avoid truncating our data.

    We also have the same issue with address fields - we sometimes get more characters for long stline1 than what MDM supports and the data gets truncated.

    We would like to have an option to configure the length of these fields as needed to meet business requirements.