This bug was first discovered in July of 2016. See the NUG thread "Does 4D Support Dotted Notation in Object Fields?” if you are interested in how it was discovered (thanks to Douglas Von Roeder). ACI0095526.
Even though I filed the bug report, I can think of at least twice since then that I’ve been bitten by this behavior because I forgot about it. I think this is an example where documenting doesn’t help that much. Thinking 4D will save the changes I’ve made to an object is so natural a thought that I keep forgetting it won’t work in these situations, even though I had documented it myself. If it is true that this wasn’t implemented as we naturally think it should have been for performance reasons, I’d like to express that I would prefer it to be slower and know that it is saved than faster and find out later it wasn’t saved. -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <[email protected]> <www.synergyfarmsolutions.com> > On Oct 31, 2017, at 7:46 PM, Tim Nevels via 4D_Tech <[email protected]> > wrote: > > It is quite alright to have different behaviors for things IF YOU DOCUMENT > IT! How can we defensively programing around unknown problems? ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
