Hi,
I've noticed Celigo will sometimes update records using an inline edit (submitFields / XEDIT event), and sometimes it will update using record.save (creating a normal save / EDIT type event)
- Why does Celigo change the way it saves the record? I know submitFields has a lower impact on governance, or are there other benefits?
- Is there a way to force Celigo to use .save() or .submitFields() specifically?
- how does Celigo decide which method to use?
- Is there a performance benefit to using (internalid) mappings instead of (name) mappings?
From my debug logs, tested by changing the terms mapping from (internalid) to (name):
20/08/2024 15:39:11 nlapi calls registered for $R r = NRecord.load({"type":"customer","id":6,"defaultValues":{}});
r.setValue({"fieldId":"altemail","value":"test@test.com"});
r.setValue({"fieldId":"terms","value":1});
r.submitFields({"type":"customer","id":6,"values":{"altemail":"test@test.com","terms":1},"options":{"enableSourcing":false}});
20/08/2024 15:40:22 nlapi calls registered for $R r = NRecord.load({"type":"customer","id":6,"defaultValues":{}});
r.setValue({"fieldId":"altemail","value":"test@test.com"});
r.setText({"fieldId":"terms","text":"Net 15"});
r.save({"enableSourcing":false,"ignoreMandatoryFields":false});