OutSystems works wonders when the API schema is stable, but many modern APIs return dynamic keys or partially populated objects, especially in integration-heavy and AI-driven scenarios. This creates friction because developers end up relying on custom JavaScript or complex workarounds just to render data cleanly in UI. 

What developers do today (pain): 

• Build custom logic to extract unique keys 
• Normalize JSON manually (fill missing attributes) 
• Use JS to reshape payloads before JSONDeserialize 
• Manage fragile UI rendering patterns for dynamic columns 

What I’d love to see improved in the platform: 

• A native Dictionary/Map type for both client and server 
• JSON tooling that supports deserialization into Maps for unknown keys 
• A standard UI binding pattern (even without Data Grid) that allows dynamic columns safely 

This would reduce dependency on custom code and make OutSystems a stronger fit for modern API patterns. 

Curious, how are others handling dynamic keys today, and where do you see the biggest friction?