The user encountered an issue where zero decimal parts in numeric values were being truncated in the transform message when using Mule runtime 4.5 and above. This behavior violated API contracts that required double-type numbers to retain trailing zeros, such as 10.00 or 180.00.
The root cause of the issue is a change introduced in Mule 4.5 runtime and above, where the DataWeave component was updated to trim trailing zeros in numeric values. This behavior aligns with the JSON specification for the number data type, which does not preserve insignificant trailing zeros.
Reference: Mule 4.5 Release Notes
"Trailing zeroes after the decimal point are now removed by default for JSON, YAML, CSV, and DataWeave formats."
1. Use a runtime argument to retain trailing zeros by setting the following property: -Dcom.mulesoft.dw.stripTrailingZeroes=false.
2. Set 'minMuleVersion' to '4.4.0' in artifact.json to retain DataWeave behavior from version 4.4, even when running on newer runtimes.
005208317

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.