| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Find the Subsidiary Lookup Criteria field.
| Note |
|---|
You must not edit the Default Staria FlowAP General Setup. Any changes made to the default template will be overriden during new version releases of FlowAP. To use a customized version of the Staria FlowAP General Setup, save a copy of the Default Staria FlowAP General Setup. Apply your own lookup criteria to the new Staria FlowAP General Setup record and save. |
...
The lookup criteria follows the JSON array syntax.
The complete item subsidiary code lookup table is surrounded by brackets
Example: [JSON ARRAY].
Each element in the lookup table is surrounded by curly braces and is separated by a comma.
Example: [{ELEMENT1}, {ELEMENT2}, {ELEMENT3}]
Each element of the lookup table contains four (3) parameters.
xpath - XML element which will be the source of the subsidiary information used for the lookup ("//cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID=\"VAT\"]").
nsfield - This is the NetSuite subsidiary record field that will be used to compare the text from the XML element to find the subsidiary record in NetSuite.
regexp - A regular expression, often referred to as a "regex" or "regexp," is a powerful and concise way to represent patterns in text data. It is a sequence of characters that defines a search pattern. Characters that match the search pattern will be retained and unmatched characters will be removed.
...
Invalid subsidiary records are not returned by the lookup
inactive = T
Internal id of the subsidiary record will be set on the subsidiary element of the FlowAP document JSON when an item subsidiary record is found.