Start a conversation
  1. ACRM Support
  2. ACRM - Articles
  3. Public Articles

CRM.interface 15.18+: Localized Numeric Formatting in XML <code>value="..."</code> Attributes When Using <code>internalfields=1</code>

Contents

Overview

In CRM.interface 15.18+, XML queries executed with internalfields=1 can return localized numeric strings inside XML value="..." attributes instead of an invariant/internal numeric representation. This can appear as thousand separators, locale-specific decimal separators, and percent signs (for example value="2,000.00", value="2 000,00", or value="100%") where invariant values are expected (for example value="2000.00" and value="100").

This behavior was confirmed as a product regression (not caused by configuration such as NoDigitGroupSymbol=true) and requires an engineering fix. The fix is planned for the Aurea CRM 15.25.4 maintenance release, with an interim patch available for earlier validation.

Solution

How to recognize the issue

When requesting internal values via CRM.interface using internalfields=1, numeric fields (decimal/currency/percent) can appear in the XML value="..." attribute using localized formatting rather than invariant formatting.

Incorrect examples (symptoms):

<NetListPrice value="1,430.08">1 430,08</NetListPrice>
<NetTotal value="2 000,00">2 000,00</NetTotal>
<ProbabilityP value="100%">100%</ProbabilityP>

Expected behavior (invariant internal numeric value in value attribute):

<NetListPrice value="1430.08">1 430,08</NetListPrice>
<NetTotal value="2000.00">2 000,00</NetTotal>
<ProbabilityP value="100">100%</ProbabilityP>

Important notes

  • The localized display value (element inner text) can remain localized; the fix targets the invariant/internal value emitted in the value="..." attribute.
  • Date value="..." attributes were observed to remain correct (for example YYYYMMDD).

Affected versions

  • Confirmed regression starting in CRM.interface 15.18+
  • Reproduced/observed in builds including 15.24.2.xxxx and 15.25.23174

Root cause classification

  • Defect/regression in product behavior: configuration review showed NoDigitGroupSymbol=true (intended to suppress digit grouping) and no relevant overrides, yet value="..." attributes still contained thousand separators and localized formatting.

Resolution options

Permanent fix (recommended)

  • Upgrade to Aurea CRM 15.25.4 maintenance release (or later) once available.
  • This release includes the fix restoring invariant formatting for numeric value="..." attributes when internalfields=1 is used.

Interim mitigation (when upgrade cannot wait)

  • Apply the interim patch package for CRM.interface, then validate output formatting.
  • If your environment uses multiple CRM.interface nodes (for example, behind a load balancer), apply the patch consistently to all nodes to avoid inconsistent responses.

Diagnostics / Data Collection

If you need to capture evidence for comparison (before/after) or to confirm the behavior in your environment, use the steps below.

  1. Enable detailed CRM.interface logging
    • Set in mm.ini (commonly under <crm_interface_install>\web\system\sys\):
  2. log_all=1
log_level=7
  3. Reproduce the issue
    • Run an XML query with internalfields=1 including:
    • A decimal/currency value > 999.99
    • A percent field
  4. Collect diagnostics
    • u8_interface.log
    • u8_iis_interface.log
    • settings.xml (from <crm_interface_install>\web\)
    • System settings file from the /system/ directory (if used in your deployment)
    • Exact CRM.interface version/build (for example 15.25.xxxxx)
  5. Confirm configuration intent
    • Verify NoDigitGroupSymbol=true is present (this should suppress grouping, but in this defect it does not correct the value="..." attributes).

Post-fix Verification

After upgrading to 15.25.4 (or later) or applying the interim patch, validate the results using the checklist below.

  1. Re-run the same CRM.interface query with internalfields=1.
  2. Confirm numeric value="..." attributes are invariant:
    • Decimal/currency: value="2000.00" (no thousand separator; dot as decimal separator)
    • Percent: value="100" (no % sign)
  3. Confirm element inner text remains localized as expected (depending on your locale settings).
  4. Confirm date value="..." attributes remain YYYYMMDD.

Frequently Asked Questions

1. How do I know I’m affected by this CRM.interface regression?

If an XML query using internalfields=1 returns numeric value="..." attributes like value="2,000.00", value="2 000,00", or percent values like value="100%" instead of invariant forms such as value="2000.00" and value="100", your system is affected.

2. Is this caused by locale settings or NoDigitGroupSymbol=true configuration?

This behavior can occur even when configuration indicates grouping should be suppressed (for example, NoDigitGroupSymbol=true) and no formatting overrides exist. In confirmed cases, it was a product regression requiring an engineering fix.

3. Which versions are affected and where is it fixed?

The regression was confirmed in CRM.interface 15.18+ (observed in builds including 15.24.2.xxxx and 15.25.23174). The fix is planned for the Aurea CRM 15.25.4 maintenance release (or later).

4. What should I validate after upgrading or applying the patch?

Re-run a query with internalfields=1 that includes (1) decimal/currency values > 999.99 and (2) percent fields. Verify that XML value="..." attributes are invariant (for example value="2000.00" and value="100"), while the element text may remain localized.

5. What if I have multiple CRM.interface servers behind a load balancer?

Apply the interim patch (or upgrade) to all CRM.interface nodes and validate responses from each node to prevent mixed behavior depending on which node serves the request.

Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments