Skip to Main Content
InterSystems Ideas

Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.

The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.

💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.

🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.

Start by sharing what could be better - the community and our teams will help take it from there.

Status Will not implement
Created by Ashok Kumar T
Created on Jun 30, 2025

Enhance JSON Adaptor with Case-Insensitive Field Mapping

The current JSON adaptor implementation, the property name or %JSONFIELDNAME is treated as a constant and case-sensitive when importing JSON into an object. This means the JSON key must match exactly or match with the xData Mapping.

To improve flexibility, introduce a new parameter, %JSONFIELDCASE, which allows developers to override this default behavior and perform case-insensitive mapping during import.

Example:

Property Name As %String(%JSONFIELDCASE = 0);

This property would accept any of the following JSON keys: "Name", "name", "nAMe", etc.

Property Description As %String;

This would only map successfully to the exact key "Description" in the JSON.

This enhancement would help reduce JSON parsing errors and support more flexible integrations.

  • ADMIN RESPONSE
    Aug 27, 2025

    Thank you for submitting the idea. Based on information from our experts the status of your idea was changed to "Will not implement". Please look for details in the comments on the idea. Good luck!

  • Evgeny Shvarov
    Jun 30, 2025

    In addition, if no %JSONFIELDNAME is provided, allow Case-insensitive behaviour for data import. It is really strange that now import is Case-sensitive, as class properties are not Case-sensitive by its nature.