Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 5 Next »

The subsidiary lookup criteria are used to determine which NetSuite subsidiary record needs to be used for the transaction that will be created through FlowAP e-document conversion.

Navigating to the setup

Navigate to FlowAP > FlowAP Configuration > Staria FlowAP General Setup

View and edit the record related to your subsidiary.

Navigate to the Lookup Criteria.

Find the Subsidiary Lookup Criteria field.

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.

Understanding the Subsidiary Lookup Criteria

The lookup criteria follows the JSON array syntax.

  • The complete item 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.

Default Item Lookup Criteria

[
{
"xpath":"//cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID=\"VAT\"]",
"nsfield":"taxidnum",
"regexp":"[^a-zA-Z0-9]"
},
{
"xpath":"//cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID=\"GLN\"]",
"nsfield":"taxidnum",
"regexp":"[^a-zA-Z0-9]"
},
{
"xpath":"//cac:AccountingCustomerParty/cac:Party/cbc:EndpointID",
"nsfield":"custrecord_sta_flowap_endpointid"
},
{
"xpath":"//cac:AccountingCustomerParty/cac:Party/cbc:EndpointID",
"nsfield":"taxidnum",
"regexp":"[^a-zA-Z0-9]"
},
{
"xpath":"//cac:AccountingCustomerParty/cac:Party/cac:Contact/cbc:ElectronicMail",
"nsfield":"email"
}
]

Lookup Results

  • 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 record is found.

  • No labels