IBM Data & AI

 Welcome to the IBM Data & AI Ideas Portal for Clients! 

We welcome and appreciate your feedback on IBM Data & AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.  If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback  and suggestions you have for improving our offerings / products!  This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.
  • If you have not registered on this portal please click on the following link and register.  To complete registration you will need to open the email you will receive from Aha to confirm your identity.
Additional Information:
  • The shorter URL for this site is:
  • To view our roadmaps:
  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

MDM AE : Performance overhead due to timestamp field format

As per the Bank's service contract, timestamp must have 'T' in the data to comply the contract validation. (Ex: 2012-03-25T00:00:00.002).

But on IBM MDM service response, this T is not available on timestamp which leads to contract validation failure.

Currently this issue is handled in middleware by overlaying ‘T' on timestamp field which is incurring an overhead. (Ex: 2012-03-25 00:00:00.002).

  • Guest
  • Mar 31 2020
  • Need More Information
Why is it useful?
Who would benefit from this IDEA? As a customer, i want to reduce the overhead caused by doing transformation on the time spent which should have been a standard format.
How should it work?

As per the Bank's service contract, timestamp must have 'T' in the data to comply the contract validation. (Ex: 2012-03-25T00:00:00.002).

Performance overhead of milliseconds is there due to the workaround we have implemented.

Idea Priority Urgent
Priority Justification Idea should be ranked HIGH because we are not able to meet SLA due to the workaround we have put in place.
Customer Name Nedbank Limited
Submitting Organization
Submitter Tags
  • Attach files
  • Admin
    Marcus Boone commented
    31 Mar 02:30pm

    Eric - thank you for the sumission. We are reviewing the information you have provided and will post an update here or to you directly. Was the workaround you have in place something provided by IBM Support or something you/your solution provider implemented? Perhaps you could send me details on the workaround to Thanks again.

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions