SynchUP by Snapshot June updates
We are constantly improving on our connectors. Here's what we did in June 2023.
2023.06.07
SynchUP Core
- MCO Updates
- Added support for multiple addresses on Company MCO
- History Updates
- Resolved an issue where submitting a payload Run would show a 0 Record count instead of 1
- Core
- Improved efficiency of internal logging tools
- Improved resiliency of overall worker processing when handling unexpected errors or issues. Should prevent jobs from hanging in the "Processing" state under certain conditions.
BigCommerce Connector
- Customer Pusher
- Resolved an issue where we were not logging validation errors when missing values such as email address or name
- Company Pusher
- Added support for pushing multiple addresses on Companies
- Order Puller
- Added additional extraneous BigC datapoints from the api and saving them as attributes to the MCO
- Added logic to support to normalize BigC gift certificates to the MCO
- Order Pusher
-
- Resolved an issue where line-item totals were not denormalized properly to BigC
- Resolving an issue where fulfilling and der would result in an incorrect status order or operations to occur
NetSuite Connector
- Invoice Puller
- Adding new settings to identify the custom fields external id for invoice and company are stored in NetSuite
- Company Puller
- Added support for pulling multiple addresses on Companies
- Order Puller
- Resolved an issue that would sometimes occur with an error stating "Too many options"
- Product Puller
- Improving Matrix Product normalization to MCO
Deacom Connector
- Customer Puller
- Resolved an issue where a duplicate key error could occur, resulting in a critical failure of the job
2023.06.21
SynchUP Core
- Further improved efficiency of logging framework to speed up overall job performance
BigCommerce Connector
- Product Pusher
- Improved API call efficiency to speed up overall job performance
- Customer Puller
- Added additional setting to identify the Custom Form Field that address ids are stored in
Deacom Connector
- Customer Puller
- Added additional settings to identify the Deacom UserField Id BillTo Customer External Id is stored in
- Customer Pusher
- Added additional settings to identify the Deacom UserField Id that BillTo Address Ids should be stored in
NetSuite Connector
- Product Puller
- In the event that the auth token for NetSuite does not have the permission "Custom Item Fields" we've improved the error message in the UI to better explain that