mrob
11/09/2023, 9:54 PM"name":"INVALID_FLD_VALUE","message":"You have entered an Invalid Field Value 2285 for the following field: customer"
mrob
11/09/2023, 9:54 PMvar paymentRecord = record.create({ type: 'customerpayment', isDynamic: true })
paymentRecord.setValue('customer', customerId)
given the customer seems to be perfectly valid?
I can create a payment from that customer in the UI or browser console using transform just fine?mrob
11/09/2023, 9:54 PMmrob
11/09/2023, 9:55 PMmrob
11/09/2023, 9:55 PMmrob
11/09/2023, 9:56 PMmrob
11/09/2023, 9:57 PMAudit customerId - 2285 type - string
(and checked typeof to get string)reptar
11/09/2023, 9:58 PMmrob
11/09/2023, 9:58 PMcustomer
not entity
in this case I think?)mrob
11/09/2023, 9:59 PMreptar
11/09/2023, 9:59 PMmrob
11/09/2023, 10:00 PMreptar
11/09/2023, 10:00 PMreptar
11/09/2023, 10:00 PMcustomer
field on the resulting Customer Payment record. This field is populated automatically during transformation, and you cannot specify a value for this field after the transformation is complete.mrob
11/09/2023, 10:00 PMreptar
11/09/2023, 10:01 PMmrob
11/09/2023, 10:01 PMvar paymentRecord = record.create({ type: 'customerpayment', isDynamic: true })
paymentRecord.setValue('customer', customerId)
is not using transformmrob
11/09/2023, 10:02 PMtransform
I do not set the customer record via setValue. Both should yield me the same resultreptar
11/09/2023, 10:02 PMmrob
11/09/2023, 10:03 PMmrob
11/09/2023, 10:08 PMmrob
11/09/2023, 10:42 PM