Hello! I want to confirm: do we expected extension fields to also populated when we insert a record and pass a DSN?
In my use case we are inserting a line in UpdateSalesOrderDetailForSplittingSalesOrderLine and I am validating that the extension field ‘nsCoxFulfillmentMethod’ is populated.
If a Data Source Name is specified when calling another logic block, any extension fields that are populated on the record will pass for free to the called logic block.
If a Data Source Name is not specified when calling another logic block, extension fields must be mapped directly in the Field Mappings, or, using Additional Mappings to pass the extension fields from whatever DSN you specify in Additional Mappings onto the DSN of the target logic block.
Here’s an example where any additional fields on the SalesOrderDetail DSN will automatically get passed to the LB being called:
If it is a pair of base ownership logic blocks involved and you are a customer or partner and don’t have the ability to make changes, to get additional fields to flow between the base logic blocks, the calling logic block must either specify a Data Source Name or if that’s not possible, specify Additional Mappings so that a customer or partners additional fields travel for free from one base ownership LB to another. Nextworld Help gets into more detail on additional mappings per the screenshot below.
Depends on the details of your insert. You say “pass a DSN”, which means you already have a DSN of the matching 'shape’. Where did it come from? Was it a DSN variable or fetched from somewhere? Was the value populated in the “passed” DSN?
I’m assuming you mean this field in the insert statement is populated. Yes, if that record has the extension value populated and there is no unusual logic in the table triggers or action block, then the inserted record will also have the value.
Yes, that is what i am talking about, thanks for the confirmation and explanations y’all!
