Skip to Main Content

This is an IBM Automation portal for Integration products. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Workspace App Connect
Created by Guest
Created on Jan 8, 2016

Parser option for decimal numbers in JSON

The JSON parser in IIB unconditionally parses fractional numbers as floats. This is not always desirable, because
a) a floating point number cannot accurately represent the original fractional decimal value, so precision is lost when the value is copied or written in another format. This looks like data corruption to a downstream application.
b) calculations performed on the floating point number ( in the message flow ) will yield incorrect results. This is particularly problematic when dealing with monetary values, which are always expressed as decimal values.

Proposed solution:
The JSON parser can be instructed to parse all numbers as DECIMALs instread of FLOATs, but it requires the setting of two environment variables:

I think the JSON parser should expose properties that allow these options to be set explicitly in the message flow.

Idea priority Low
RFE ID 82248
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Feb 2, 2021

    RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate status. As part of our standard approach to RFEs we regularly re-assess those in Uncommitted Candidate status for continued relevance. This area of the product behaviour is undergoing enhancement as part of our next major engineering release, so we will look into the feasibility of storing these environment settings (and other JSON resource manager configuration) as part of the server.conf.yaml file. Status of the RFE is updated to Planned for Future Release.

  • Guest
    Jan 12, 2016

    Thanks for raising this RFE, and for the excellent description of the use case and links to discussions. As you acknowledge in the posts, the desired behaviour is achievable using the referenced Environment Variables - which are available in all in-service releases of the product (WMBv7, WMBv8, IIBv9 and IIBv10)... However making the configuration more user friendly and explicit in the flow would be beneficial, for example via settings on both relevant Input nodes and also invocations of the parser within other computational nodes (eg CREATE with PARSE clause and variants etc. across programming languages) etc. Status of this RFE is updated to Uncommitted Candidate.