Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Functionality already exists
Created by Guest
Created on Feb 16, 2022

Need milliseconds in Source timestamp in IV

Currently in IV we have field "sourceTs":"2021-02-24T18:42:01Z" but it does not contain milliseconds in it.

What is your industry? Retail
How will this idea be used?

Omni publish parallels inventory updates and the frequency of such updates can sometimes be in milliseconds for same product . So to differentiate the latest update we need to filter it based on the milliseconds .

  • Guest
    Mar 23, 2022

    Can you try again with the ISO 8601 data format (e.g. 2022-11-07T00:25:00.073876Z)?

  • Guest
    Mar 23, 2022

    Hi @Ryan, it doesn't seem to be working in a lower environment. See attached screenshot

  • Guest
    Mar 16, 2022

    Hello Sunay. One of our engineers checked the code and even though the documentation does not reflect it, the solution should actually have the time precision to three decimal places. (e.g. "2021-02-24T18:42:01.000Z")

    Can you recheck this and confirm the behavior you are seeing?