Hi All, 

If a field is of type DECIMAL with length and scale as 10,2 and if the value is like 12345789.02 then in MIF it is getting exported in scientific notation like 1.234578902E7. Is there a way where we can export value in real number(12345789.02) itself without e notation?
Checked mxe.int.usescientific system property but it is not working !! Is there a way to change this ??

------------------------------
Kalaiselvan Matheswaran
------------------------------

#Maximo
#AssetandFacilitiesManagement

Hi Kalaiselvan,

Can you can confirm if you are using XML or JSON?  The JSON parser is strong typed, so we have less control than with XML.  Also, is there a Salesforce Case for this (no need to add one yet if none created, we shall see where this goes)?

------------------------------
Steve Hauptman
------------------------------

Hi Steve,

Thank you !! We are using JSON.
Could see similar APAR and fix for IBM BPM but not for Maximo. Have raised a case also with IBM.

JR48757: DECIMAL IS CONVERTED TO SCIENTIFIC NOTATION DURING WEB SERVICE REQUEST

mxe.int.usescientific system property is working for XML but not for JSON.

------------------------------
Kalaiselvan Matheswaran
------------------------------

Original Message:
Sent: Wed September 14, 2022 08:10 AM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan,

Can you can confirm if you are using XML or JSON?  The JSON parser is strong typed, so we have less control than with XML.  Also, is there a Salesforce Case for this (no need to add one yet if none created, we shall see where this goes)?

------------------------------
Steve Hauptman
------------------------------

Hi Kalaiselvan, that is the issue.  We cannot control the JSON.  That APAR is also addressing XML and not JSON.  Question: JSON is typically machine to machine and handle scientific notation.  So, can you help me understand the use case for needing it different?

------------------------------
Steve Hauptman
------------------------------

Original Message:
Sent: Wed September 14, 2022 09:05 AM
From: Kalaiselvan Matheswaran
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Steve,

Thank you !! We are using JSON.
Could see similar APAR and fix for IBM BPM but not for Maximo. Have raised a case also with IBM.

JR48757: DECIMAL IS CONVERTED TO SCIENTIFIC NOTATION DURING WEB SERVICE REQUEST

mxe.int.usescientific system property is working for XML but not for JSON.

------------------------------
Kalaiselvan Matheswaran
------------------------------


Original Message:
Sent: Wed September 14, 2022 08:10 AM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan,

Can you can confirm if you are using XML or JSON?  The JSON parser is strong typed, so we have less control than with XML.  Also, is there a Salesforce Case for this (no need to add one yet if none created, we shall see where this goes)?

------------------------------
Steve Hauptman

Hi Steve,

Thank you !!

If external system cannot consume message over an API and if we need to change it to different format like file, DB Scripts etc., using middleware then it will have an impact right ?

------------------------------
Kalaiselvan Matheswaran
------------------------------

Original Message:
Sent: Wed September 14, 2022 01:36 PM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan, that is the issue.  We cannot control the JSON.  That APAR is also addressing XML and not JSON.  Question: JSON is typically machine to machine and handle scientific notation.  So, can you help me understand the use case for needing it different?

------------------------------
Steve Hauptman
------------------------------


Original Message:
Sent: Wed September 14, 2022 09:05 AM
From: Kalaiselvan Matheswaran
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Steve,

Thank you !! We are using JSON.
Could see similar APAR and fix for IBM BPM but not for Maximo. Have raised a case also with IBM.

JR48757: DECIMAL IS CONVERTED TO SCIENTIFIC NOTATION DURING WEB SERVICE REQUEST

mxe.int.usescientific system property is working for XML but not for JSON.

------------------------------
Kalaiselvan Matheswaran


Original Message:
Sent: Wed September 14, 2022 08:10 AM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan,

Can you can confirm if you are using XML or JSON?  The JSON parser is strong typed, so we have less control than with XML.  Also, is there a Salesforce Case for this (no need to add one yet if none created, we shall see where this goes)?

------------------------------
Steve Hauptman

Hi Kalaiselvan,

Can you use XML instead of JSON?  In XML you can have it without scientific notation.

------------------------------
Steve Hauptman
------------------------------

Original Message:
Sent: Thu September 15, 2022 02:28 PM
From: Kalaiselvan Matheswaran
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Steve,

Thank you !!

If external system cannot consume message over an API and if we need to change it to different format like file, DB Scripts etc., using middleware then it will have an impact right ?

------------------------------
Kalaiselvan Matheswaran
------------------------------


Original Message:
Sent: Wed September 14, 2022 01:36 PM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan, that is the issue.  We cannot control the JSON.  That APAR is also addressing XML and not JSON.  Question: JSON is typically machine to machine and handle scientific notation.  So, can you help me understand the use case for needing it different?

------------------------------
Steve Hauptman


Original Message:
Sent: Wed September 14, 2022 09:05 AM
From: Kalaiselvan Matheswaran
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Steve,

Thank you !! We are using JSON.
Could see similar APAR and fix for IBM BPM but not for Maximo. Have raised a case also with IBM.

JR48757: DECIMAL IS CONVERTED TO SCIENTIFIC NOTATION DURING WEB SERVICE REQUEST

mxe.int.usescientific system property is working for XML but not for JSON.

------------------------------
Kalaiselvan Matheswaran


Original Message:
Sent: Wed September 14, 2022 08:10 AM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan,

Can you can confirm if you are using XML or JSON?  The JSON parser is strong typed, so we have less control than with XML.  Also, is there a Salesforce Case for this (no need to add one yet if none created, we shall see where this goes)?

------------------------------
Steve Hauptman

Hi Steve,

Thank you !! We will validate the feasibility accordingly.

------------------------------
Kalaiselvan Matheswaran
------------------------------

Original Message:
Sent: Thu September 15, 2022 03:50 PM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan,

Can you use XML instead of JSON?  In XML you can have it without scientific notation.

------------------------------
Steve Hauptman
------------------------------


Original Message:
Sent: Thu September 15, 2022 02:28 PM
From: Kalaiselvan Matheswaran
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Steve,

Thank you !!

If external system cannot consume message over an API and if we need to change it to different format like file, DB Scripts etc., using middleware then it will have an impact right ?

------------------------------
Kalaiselvan Matheswaran


Original Message:
Sent: Wed September 14, 2022 01:36 PM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan, that is the issue.  We cannot control the JSON.  That APAR is also addressing XML and not JSON.  Question: JSON is typically machine to machine and handle scientific notation.  So, can you help me understand the use case for needing it different?

------------------------------
Steve Hauptman


Original Message:
Sent: Wed September 14, 2022 09:05 AM
From: Kalaiselvan Matheswaran
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Steve,

Thank you !! We are using JSON.
Could see similar APAR and fix for IBM BPM but not for Maximo. Have raised a case also with IBM.

JR48757: DECIMAL IS CONVERTED TO SCIENTIFIC NOTATION DURING WEB SERVICE REQUEST

mxe.int.usescientific system property is working for XML but not for JSON.

------------------------------
Kalaiselvan Matheswaran


Original Message:
Sent: Wed September 14, 2022 08:10 AM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan,

Can you can confirm if you are using XML or JSON?  The JSON parser is strong typed, so we have less control than with XML.  Also, is there a Salesforce Case for this (no need to add one yet if none created, we shall see where this goes)?

------------------------------
Steve Hauptman

Hi Steve,


     Did this ever get an APAR for JSON. We are having this issue as well.

Thanks,

------------------------------
Gina Barry
------------------------------

Original Message:
Sent: Thu September 15, 2022 03:50 PM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan,

Can you use XML instead of JSON?  In XML you can have it without scientific notation.

------------------------------
Steve Hauptman
------------------------------


Original Message:
Sent: Thu September 15, 2022 02:28 PM
From: Kalaiselvan Matheswaran
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Steve,

Thank you !!

If external system cannot consume message over an API and if we need to change it to different format like file, DB Scripts etc., using middleware then it will have an impact right ?

------------------------------
Kalaiselvan Matheswaran


Original Message:
Sent: Wed September 14, 2022 01:36 PM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan, that is the issue.  We cannot control the JSON.  That APAR is also addressing XML and not JSON.  Question: JSON is typically machine to machine and handle scientific notation.  So, can you help me understand the use case for needing it different?

------------------------------
Steve Hauptman


Original Message:
Sent: Wed September 14, 2022 09:05 AM
From: Kalaiselvan Matheswaran
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Steve,

Thank you !! We are using JSON.
Could see similar APAR and fix for IBM BPM but not for Maximo. Have raised a case also with IBM.

JR48757: DECIMAL IS CONVERTED TO SCIENTIFIC NOTATION DURING WEB SERVICE REQUEST

mxe.int.usescientific system property is working for XML but not for JSON.

------------------------------
Kalaiselvan Matheswaran


Original Message:
Sent: Wed September 14, 2022 08:10 AM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan,

Can you can confirm if you are using XML or JSON?  The JSON parser is strong typed, so we have less control than with XML.  Also, is there a Salesforce Case for this (no need to add one yet if none created, we shall see where this goes)?

------------------------------
Steve Hauptman

Hi Gina, there is no APAR for JSON.  The information I have from the integration team is that we have no control over JSON like we do with XML. 

------------------------------
Steve Hauptman
------------------------------

Original Message:
Sent: Thu April 06, 2023 03:58 PM
From: Gina Barry
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Steve,


     Did this ever get an APAR for JSON. We are having this issue as well.

Thanks,

------------------------------
Gina Barry
------------------------------


Original Message:
Sent: Thu September 15, 2022 03:50 PM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan,

Can you use XML instead of JSON?  In XML you can have it without scientific notation.

------------------------------
Steve Hauptman


Original Message:
Sent: Thu September 15, 2022 02:28 PM
From: Kalaiselvan Matheswaran
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Steve,

Thank you !!

If external system cannot consume message over an API and if we need to change it to different format like file, DB Scripts etc., using middleware then it will have an impact right ?

------------------------------
Kalaiselvan Matheswaran


Original Message:
Sent: Wed September 14, 2022 01:36 PM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan, that is the issue.  We cannot control the JSON.  That APAR is also addressing XML and not JSON.  Question: JSON is typically machine to machine and handle scientific notation.  So, can you help me understand the use case for needing it different?

------------------------------
Steve Hauptman


Original Message:
Sent: Wed September 14, 2022 09:05 AM
From: Kalaiselvan Matheswaran
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Steve,

Thank you !! We are using JSON.
Could see similar APAR and fix for IBM BPM but not for Maximo. Have raised a case also with IBM.

JR48757: DECIMAL IS CONVERTED TO SCIENTIFIC NOTATION DURING WEB SERVICE REQUEST

mxe.int.usescientific system property is working for XML but not for JSON.

------------------------------
Kalaiselvan Matheswaran


Original Message:
Sent: Wed September 14, 2022 08:10 AM
From: Steve Hauptman
Subject: Maximo MIF - Scientific notation for decimal fields with large values

Hi Kalaiselvan,

Can you can confirm if you are using XML or JSON?  The JSON parser is strong typed, so we have less control than with XML.  Also, is there a Salesforce Case for this (no need to add one yet if none created, we shall see where this goes)?

------------------------------
Steve Hauptman