-
Navigating the CBPR+ November 2025 Deadline: A Technical Guide to Schema Validation and Data Transformation
The global payments landscape is transforming due to the ISO 20022 standard, with SWIFT’s CBPR+ program phasing out legacy MT messages by November 2025. This transition involves complex challenges requiring a deep understanding of XML-based MX formats, schema validation, data mapping, and specialized tools to ensure compliance and data integrity throughout the migration process.
-
Converting xs:any defined XML data to JSON data
Converting XML to JSON can be challenging, especially with xs:any types, as their output can vary between single objects and arrays based on input. Liquid XML Objects and Data Binder provide solutions to streamline this process, including better support for XSD and JSON serialization.
-
Important Update for C++ JSON Serialization
A bug has been identified in the Liquid C++ Runtime libraries causing random invalid results in JSON serialization. Customers should upgrade to Liquid XML Data Binder 20.7.0 or later. The issue stems from an uninitialized enum value leading to unnecessary Array creation. C# and Java versions are unaffected due to sensible defaults.
-
Do your XML tools support JSON?
Liquid XML originally focused on XML tools but has since expanded to include JSON support. The content provides links to various JSON-related resources on their website, such as editors, schema documentation, data mapping, and data binding instructions in multiple programming languages.
-
JSON Data Binding with Liquid XML 2018 – Update 1
Liquid XML Data Binder facilitates data interchange between XML and JSON for nearly 20 years, introducing FromJson and ToJson methods to the Liquid Runtime API for serialization and deserialization. It supports C++, C#, Visual Basic .Net, and Java, enabling effective data handling from backend systems to mobile devices.
-
CDATA processing in XML Data Binding
The default behavior for processing CDATA is to remove the CDATA tags, allowing for easier display and usage of the contained values. To retain the tags, set StripCDATA to false in the XmlSerializationContext, though you’ll need to handle tag removal manually for presentation. This applies to both simple and extended string elements.
-
Error E2001 – The schema does not contain any ‘elements’ so will not generate any classes
Error E2001 in the Liquid XML Data Binder indicates that a schema lacks elements, preventing the generation of C#, C++, Java, VB .Net, or Visual Basic 6 classes. To resolve this, define elements within the schema, as they are necessary for class generation and valid XML document validation.
-
Visual C++ 11.0 XP Liquid Runtime
Liquid XML Runtime for Visual C++ 11.0 XP is now part of the Liquid XML 2013 point release (11.0.12). Visual Studio 2012 Update 1 introduces an option for targeting XP in C++ builds, requiring DLLs to be built with the XP flag. Manual adjustments to project settings and specific runtime file selections are necessary.
-
Adding xml to an ‘Any’ Element
This content explains how to integrate an XML fragment into another XML document, particularly in constructing a SOAP request in C#. It outlines two methods: building a string value to include an XML fragment or using an ‘Any’ element from a Liquid XML generated Object Model to insert the XML message part effectively.
-
XML Nillable (and xs:nil) Support in C++, C#, VB.Net, Java and Visual Basic 6 XML Data Binding
Liquid XML Studio 2010 now supports XML Nillable (and xs:nil) across multiple languages, including C++, C#, VB.Net, Java, and Visual Basic 6. This enhancement addresses a longstanding request for users of the XML Code Generator, particularly those working with XML standards that include the Nillable attribute in their schemas.
