Sourced Fields issue: We have a custom transactio...
# suitebuilder
m
Sourced Fields issue: We have a custom transaction body field called AR Rep, this field is present on SOs and Invoices, but not Estimates. It is configured to be sourced from Customer > AR Rep. When we create a new SO from a customer record or create a new SO and select the customer, the AR Rep field is sourced correctly from the Customer record. Since the Estimate record does not have an AR Rep field, creating an SO from the quote does not populate the AR Rep field on the SO. Shouldn't this field still source from the customer record? Or are the transformed fields from the quote a higher priority that sourced fields from the Customer record in this case?
n
The sourcing is done when you add the customer. Or generally, what I have seen, custom fields flow to the related records if they are on both of the records. So you might want to add it on the Estimate and see if it flows through to SO.
m
Thanks. Yes, adding that field to the Estimate form in a Sandbox caused it to work as we expected.