The neat thing about objects, in my opinion, is that they are reference based. 
I would try to stay away from using OB Copy unless it is warranted. For 
example, in your example you could just use the field directly or a reference 
to the field. Unless you save the record, changes won’t be put back in the 
database anyway.

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.

Synergy Farm Solutions Inc.
Hill Spring, AB Canada

> On Jun 12, 2018, at 7:26 PM, johnbdhPop via 4D_Tech <> 
> wrote:
>       So maybe I want to use OB Copy when I load the record in an input form. 
> That way I can make changes to the object without changing the object in the 
> field. That way if the user cancels I don’t have to worry about the field.
>       When the user saves the record, should I use OB Copy to save the object 
> back to the field, or does it really matter?

4D Internet Users Group (4D iNUG)

Reply via email to