Hi Tim, I haven’t had time to try this myself today, but do you know off the top of your head if this is only fixed when using dot notation? Or is it fixed when for the old style of code as well (when we had to traverse the object tree to the children, getting a reference to the child and then changing the child object without changing the parent object)?
Thanks. -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <[email protected]> <www.synergyfarmsolutions.com> > On Jun 13, 2018, at 12:31 PM, Timothy Penner <[email protected]> wrote: > >> However, be aware of a bug in 4D. If you modify a child object in an object >> type field and then save the record, the object will not be saved. It is >> only saved if you modify a top level key in the object. The workaround, >> until 4D fixes this, is to assign the object field to itself before saving. > > This issue only exists in earlier versions of the product (R releases), where > the feature was first introduced. > > In v17.0 this will work as expected, without needing to assign the field to > itself. > ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
