When does the createfrom get removed on record.save after a transform.

AI generated answer (using internal Slack threads):

The

createdfrom

field gets removed on

record.save

after a transform operation when you make changes that would remove the relationship between the original record and the transformed record. For example, if you are transforming a Sales Order record into a Return Authorization record, and then you set the customer field on the Return Authorization record, this would destroy the

createdfrom

relationship. Here is a code snippet that was shared in the conversation:

javascript
rma = record.transform({
  fromType: record.Type.SALES_ORDER,
  fromId: soId,
  toType: record.Type.RETURN_AUTHORIZATION,
});

let rmaId = rma.save({
  enableSourcing: false,
  ignoreMandatoryFields: true,
});

In this example, if you were to set the customer field on the

rma

record before calling

rma.save()

, the

createdfrom

field would be removed. It's also worth noting that the

enableSourcing

option in the

record.save

method could potentially affect the

createdfrom

field. If

enableSourcing

is set to

false

, it prevents the system from sourcing field values from related records. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******

What changes to an Invoice would remove the relationship to a sales order?