Skip to the main content.
Contact
Contact
Stay Connected

Sign up to hear about Snapshot's latest news and projects!

SynchUP by Snapshot October updates

 

We are constantly improving on our connectors. Here's what we did in October 2023.

2023.10.11

SynchUP Core

  • Resolved an issue where users might not access client organizations they have permission to under specific conditions
  • Addressed a problem preventing the deletion of list settings

BigCommerce Connector

  • Customer Puller
    • Standardized setting name and description for External ID
  • Invoice Puller
    • Standardized setting name and description for External ID
  • Company Puller
    • Resolved an issue where Companies without specified Admins were not included in the dataset
  • Order Puller
    • Introduced a new Filter Setting that enables configuration of which BigCommerce Order Statuses an order must have to be pulled; This filter can recognize Order Status ID, Order Status system name, or Order Status custom name

NetSuite Connector

  • Core Connector
    • Incorporated logic to address a specific error named “com.netledger.common.exceptions.NLUserError: No data was found”; This error appeared in new NetSuite environments devoid of data, SynchUP will now handle this error gracefully
  • Invoice Puller
    • Fixed an issue where some Invoice data didn't map correctly leading to an error
  • Transaction Puller
    • Enhanced error handling for cases where the Transaction Puller fails to write to a custom field in NetSuite

2023.10.25 

SynchUP Core 

  • Added ExternalId property to all Address entities. Default schemas have been updated. Existing Jobs will need to load a new schema, or add a new translation rule to existing schemas in order to utilize this new field 

NetSuite Connector 

  • Company Puller
    • Added a new setting to define and specify which custom field in NetSuite contains the external id for a company. If set, this will populate the value of that custom field on the MCO as the external id
    • Added a new setting to define and specify which custom field in NetSuite contains the external id for a company address. If set, this will populate the value of that custom field on the MCO as the external id
  • Customer Puller
    • Added a new setting to define and specify which custom field in NetSuite contains the external id for a customer. If set, this will populate the value of that custom field on the MCO as the external id
    • Added a new setting to define and specify which custom field in NetSuite contains the external id for a customer address. If set, this will populate the value of that custom field on the MCO as the external id
  • Order Puller
    • Added a new setting to define and specify which custom field in NetSuite contains the external id for an order. If set, this will populate the value of that custom field on the MCO as the external id
    • Added a new setting to define and specify which custom field in NetSuite contains the external id for a customer. If set, this will populate the value of that custom field on the MCO as the external id
    • Added a new setting to define and specify which custom field in NetSuite contains the external id for a customer address. If set, this will populate the value of that custom field on the MCO as the external id
    • Added the NetSuite field “Back Ordered” that appears on the Items list of a Sales Order or Item Fulfillment record to the LineItems entity on SynchUP MCO ShipTos and Fulfillment records.
  • Transaction Puller
    • Added the NetSuite field “Back Ordered” that appears on the Items list of a Sales Order or Item Fulfillment record to the LineItems entity on SynchUP MCO ShipTos and Fulfillment records
  • Customer Pusher
    • Resolved an issue where records were silently failing if no type was specified on the MCO and no default Customer type was specified in the settings. New logs will detail what is wrong and how to fix it
    • Resolved an issue where records were sometimes not matching on email and was creating new records instead of updating records 

 BigCommerce Connector 

  • Customer Pusher
    • Increased efficiency of customer lookups
  • Order Puller
    • Added a new setting to define and specify which attribute in BigCommerce contains the external id for a customer. If set, this will populate the value of that attribute on the MCO as the external id
    • Added a new setting to define and specify which attribute in BigCommerce contains the external id for a customer address. If set, this will populate the value of that attribute on the MCO as the external id
    • Resolved an issue where when an order is placed on BigCommerce as a guest, the BigCommerce api will return an id for that customer as 0 instead of null. This could cause issues when attempting to relate customer records between systems
  • Company Puller
    • Added a new setting to define and specify which extra field field in B2B Edition contains the external id for a company. If set, this will populate the value of that extra field on the MCO as the external id
    • Added a new setting to define and specify which extra field in B2B Edition contains the external id for a company address. If set, this will populate the value of that extra field on the MCO as the external id 

 Deacom Connector

  • Core 
    • Added logic when making an api request to check for the value “PollingGuid” in the response. If present, we now mark that record as a failure and log the api request and response for improved triaging