> 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 


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:4d_tech-unsubscr...@lists.4d.com

Reply via email to