You can exclude customers from the sync with NetSuite based on the previously set condition.
Configure the Condition to Exclude Customers from the Sync
To configure the condition, go to Settings > Integrations > NetSuite and populate the following fields in the Connector Settings:
-
Exclude Customers Condition - represented by a NetSuite field, native or custom.
- for a native field, enter the special expression (API name) of the native field. See the rules for writing native fields (as well as the list of NetSuite native fields supported by YayPay) in https://yaypay.helpjuice.com/en_US/88167-netsuite/bringing-over-custom-fields-from-netsuite#netsuite-customer-native-field--yaypay-customer-custom-field
- for a custom field, enter the custom field name (e.g. CustomerStatus).
- Exclude Customers Value - the value of the field (numeric, string, etc.), based on which the customers must be filtered.
Click SAVE CHANGES.
Below see some examples of Exclude Customers Condition configuration in the Connector Settings:
- NetSuite native field (string type: “15”)
- NetSuite native field (boolean type: “false”)
- NetSuite native field (boolean type: “true”)
The sync will fail, if:
- the special expression for a native field condition is incorrect.
- the Connector does not support the indicated native field. See the list of NetSuite native fields supported by YayPay: https://yaypay.helpjuice.com/en_US/88167-netsuite/bringing-over-custom-fields-from-netsuite#netsuite-customer-native-field--yaypay-customer-custom-field.
- the custom field is incorrect (absent in NetSuite).
- the field type is select or multiselect. Only text fields are supported.
Performing the Sync for the First Time (Hourly Sync)
After you configure the condition and the value for customers exclusion for the first time and the sync starts, the Connector receives documents, establishes their Customers, and filters them according to the configured condition.
Due to this being the first connection with NetSuite, the sync depth is 3 years from the current date.
If the Connector defines that the Customer must be excluded according to the set condition, the Connector syncs the Customer as deleted. For the deleted customers, the documents are not synced.
In case the Customer already exists in YayPay, but falls under the exclusion condition during the hourly sync, such a Customer will be marked as deleted in YayPay, and the Customer's documents will be marked as deleted as well.
Performing the Sync Triggered by the Condition Addition, Modification, or Removal
When you add/modify/remove the Customer Exclusion Condition and Customer Exclusion Value in the Connector Settings after the first connection with NetSuite is established, a separate sync is triggered to compare all existing Customers in the YayPay database and all the Customers in NetSuite for the last 3 years from the Last Sync Date (indicated in the Connector Settings).
- If an existing active Customer in YayPay appears to fall under the exclusion condition as a result of the triggered comparison, such a Customer is marked as deleted in YayPay, along with all documents.
- If a Customer was marked as deleted in YayPay, but during the triggered sync does not fall under the exclusion condition, such a Customer is restored along with all documents.
Examples:
|
Case 1: There is an active Customer in YayPay with the status PROSPECT. The previous condition was to exclude customers with the status LEAD. The modified condition is to exclude customers with the status PROSPECT. |
As a result of the triggered sync, the Customer will be marked as deleted according to the modified condition. |
|
Case 2: There is a deleted Customer in YayPay with the status PROSPECT. The condition is to exclude customers with the status PROSPECT. In NetSuite, this Customer's status is changed to LEAD. |
During the next scheduled sync, the Customer will be synced as modified relative to the Last Sync Date, and restored, because he does not fall under the exclusion condition anymore. |
