Bravo, @Vitaliy Serdtsev ! 

But I cannot set true and false in advance before any interaction with JSON/%Dynamic Object/%Dynamic Array.

Or can? )

For JSON, it's essential to support true and false, as it is expected by the majority of Web and mobile UI frameworks. So IRIS can recieve a lot of JSON llike:

{"p1":true,"p2":false}

And should be able easily response with;

{"p1":false,"p2":true}

, and not:

{"p1":$$$NO,"p2":$$$YES}

Set dObj={"idea":(true), "doubt":(false)}

Do you think this is better? ;)

Actually, my another proposal is to have true and false as part of the language, where true=1 and false 0 or similar for booleans.

Submitted one 

Thank you, @Julius Kavay !

Sounds like a great idea of enhancement, thanks for sharing, @Julius Kavay !

Thank you, @Steve Pisani ! Thanks for sharing your experience! Yes, there can be different tools and combinations that provide results of decent quality - some friends of mine also consider Antigravity (and Gemini) or Claude Code with Cursor. I hope we'll end up with several working recipes to speed up the development of usual things x100 times.

Thank you, @Stephen Canzano ! That's interesting!

Thank you, Vitaly!

I see. And in my case some sets of parameters cause an anomaly, and it is not very effective to investigate it one-by-one

Thank you, @Vitaliy Serdtsev !

If enabled auditing gives the ability to see parameters, or the ability to copy/paste into SQL query tool a ready/made sql query that has been running in the system?

BTW, the global indeed contains the history! Thank you!

Thanks @David Hockenbroch ! Introduced an idea to get such a history as a system feature.

Thank you, @Robert Cemper ! Looks... complicated(?) to get an SQL query that causes anomalies? 

Thank you, @Yuri Marx @Robert Cemper ! Works for me as well - my issue was that JSON.Adapter is case sensitive. if payload comes as:

{  "strprop": "string",   "BoolProp": true } 

error fires (very unreadable). I thought that reason is the boolean value, but turned out it is property naming issue - should 100% match either name in a class description, or special JSON property name clause.

Thank you, @Dominic Chui !