Versions Compared

Version Old Version 12 New Version 13
Changes made by

Krizia Ilaga (Unlicensed)

Lou Dizon

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Navigate to Setup > Company > General Preferences

  2. Click the Custom Preferences subtab.

  3. Click the “Open” button. This opens the Default FlowAP General Setup in a new tab.

  4. Hover over the actions button and click “Make Copy”.

  5. Give your FlowAP General Setup record a new name.

    1. Enter the XML Folder ID, PDF Folder ID, JSON Folder.

    2. Update the other preferences if necessary.

  6. Click Save.

  7. Go back to Setup > Company > General Preferences and click the Custom Preferences subtab.

  8. Select the FlowAP General Setup record you created.

  9. Save the General Preferences page.

Name

Description

XML Folder ID

Enter the Internal ID of a folder where the incoming XML files should be placed.

JSON Folder ID

Enter the Internal ID of a folder where the parsed JSON Data of incoming XML files should be placed.

PDF Folder ID

Enter the Internal ID of a folder where the incoming PDF files should be placed.

Exclude Vendor Credits From Bulk Conversion

Check to exclude vendor credits from processing.

Subsidiary Lookup Criteria

This field should contain an array of JSON objects that would be used as criteria for searching the Subsidiary for the FlowAP Document. You can enter a maximum of 8 criteria and a minimum of 1.

Expand
titleDefault
Code Block
languagejson
[
        {
            "xpath": "//cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID=\"VAT\"]",
            "nsfield": "taxidnum",
            "regexp": "[^0-9]",
            "operator": "contains"
        },
        {
            "xpath": "//cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID=\"VAT\"]",
            "nsfield": "custrecord_sta_flowap_endpointid",
            "operator": "contains"
        },
        {
            "xpath": "//cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID",
            "nsfield": "taxidnum",
            "regexp": "[^0-9]",
            "operator": "contains"
        },
        {
            "xpath": "//cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID",
            "nsfield": "custrecord_sta_flowap_endpointid",
            "operator": "contains"
        },
        {
            "xpath": "//cac:AccountingCustomerParty/cac:Party/cbc:EndpointID",
            "nsfield": "custrecord_sta_flowap_endpointid",
            "operator": "contains"
        },
        {
            "xpath": "//cac:AccountingCustomerParty/cac:Party/cbc:EndpointID",
            "nsfield": "taxidnum",
            "regexp": "[^0-9]",
            "operator": "contains"
        },
        {
            "xpath": "//cac:AccountingCustomerParty/cac:Party/cac:Contact/cbc:ElectronicMail",
            "nsfield": "email",
            "operator": "contains"
        }
 ]

Use Vendor Subsidiary When Subsidiary Lookup Not Found

If this is checked and the subsidiary lookup fails due to no or multiple match, processing will proceed to vendor lookup. If a unique vendor is found and has only one subsidiary, then the vendor's subsidiary will be used.

Gateway Token

Enter the token to access Flow Gateway Dashboard. Please contact support@staria.fi if this has not been set up for your account.

Gateway Domain

Enter the domain to access Flow Gateway Dashboard. Please contact support@staria.fi if this has not been set up for your account.

Info

Subsidiary Lookup Criteria Syntax

  • Each criteria is separated by a comma.

  • The minimum lookup criteria is 1.

  • The maximum lookup criteria is 8.

  • Each lookup criteria must have:

    • “xpath”: - This is the complete source element from the XML. If the element has a parent, all parent elements must be included in the path definition.

    • “nsfield”: - the field ID of the subsidiary field where the string found in the XML element will be compared to.

  • Optional parameter of the lookup criteria

    • “regexp”: - enter a regular expression to clean up unwanted text in both the XML element string and the NetSuite field value being compared.

    • “operator”: - enter the search operator to be used. If blank, “is” operator will be used.

Example:

{"xpath": "//cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID=\"VAT\"]","nsfield": "taxidnum","regexp": "[^a-zA-Z0-9]",”operator”: “contains”}

...