Hi Manoj

There's example code of reading a JSON string from a POST request, and then transforming it to an object in

https://community.intersystems.com/post/lets-write-angular-1x-app-cach%C3%A9-rest-backend-part-9

Hope that helps

Chris

Hi Confused

If you're a Trak customer, your best option is to raise a TRC to have the appropriate Support team assist.  However, IE11 isn't a fully supported platform for Layout Editor, though it will work.  You will need the Microsoft DHTML Editing Component at a minimum, this can be obtained from

https://www.microsoft.com/en-gb/download/details.aspx?id=8956

Hope this helps

Chris

Hi Simcha

I've written a multi part guide to doing just this (it's not complete yet, but I've been struggling to get enough time to finish it).  You can find it here - https://community.intersystems.com/post/lets-write-angular-1x-app-cach%C3%A9-rest-backend-start-here

Hope that helps

Chris

There can be more to "speed" that just execution time of your code.  If you need to add an index to help performance, then a Caché SQL query will be able to utilise it without any code changes.  If you are using $Order, then you need to spend some time writing and testing your new code.

I typically use SQL to identify objects, then Object methods to interact with them, but for simple updates of large numbers of objects, I'll usually use a simple SQL Update.  The beauty of Caché is the flexibility to use the best tool for the task at hand

Hi Javier

I did this by implementing a fromJSON method on each class, which allows me to do what you describe.  By moving this to the persistent class, I don't have to worry about instantiating or accessing the object, but can just apply a JSON update to an object

The details are in https://community.intersystems.com/post/lets-write-angular-1x-app-cach%C3%A9-rest-backend-part-9

Hope this helps
Chris

Just to add a word of warning.  The syntax for %Object is only available in 2016.1, and is deprecated in favour of similar but incompatible objects and syntax in later versions.  If you have the choice of versions, it would be wisest to adopt 2016.2+ and use the DynamicObject class and methods, as this will be more futureproofed

Details are at https://community.intersystems.com/post/json-changes-cach%C3%A9-20162