SynchUP Updates

2024.2.14 

SynchUP Core

• Data Retention for history has been updated to last 30 days. Any SynchUP Runs older than 30 days are automatically purged 
• Resolved an issue where payloads were unable to be resubmitted under certain circumstances 
• Updated core logic for setting validation errors. Prior, multiple setting errors would display as individual history records. Now, they all appear together under one single record for ease of viewing 
• Further improvements made to the saving of history records and added additional fault tolerance when saving records 
• Resolved an issue where you could navigate away from the Triggers tab in certain circumstances without the unsaved changes modal preventing you from navigating away 
  
  

NetSuite Connector 

• Order Puller
  • Added new setting to allow filtering by Custom Fields at the API level
  • Added setting to only pull a record a single time
     

BigCommerce Connector

• Product Pusher
• • Added fault tolerance to the API call that updates product attributes in BigCommerce. Additionally, if the BigCommerce API times out and SynchUP is unable to update an attribute then only that record will fail where previously the entire Run resulting in a Critical error
  • Resolved an issue where sometimes upserting a Product might result in a 409 error 

2024.1.31 

SynchUP Core

• Improved our Translation Engine to error on specific data records when running translations in bulk. Previously, if an unhandled exception would occur for a single record the entire subset of records passed to the Translation Engine would fail
• Improved syntax and compilation validation for the JavaScript in the Script Engine

M1 Api Connector

• Core
  • Improved fault tolerance and error handling when connecting to the API 

NetSuite Connector 

• Core
  • Improved NetSuite API fault tolerances to better handle minor delays in the API
  • Added additional fault tolerance for individual problematic records within a list from the API, such as a single record so large the NetSuite API times out trying to retrieve it
• Product Puller
  • Added support for pulling Charge Items and Discount Items
• Order Pusher
  • Added support for a new setting that allows mapping to Sale Item custom fields when creating or updating a NetSuite Sales Order 
• Order Puller
  • Added new settings to specify what custom field external ids map to for Sales Order, Customer and Customer Address

2024.1.17 

SynchUP Core

• Resolved an issue where the payload resubmit functionality would fail on very large payloads.
  • Please note that you will need to upgrade your worker for this to be resolved
• A new Auditing tab will now display on your Jobs. This tab will display additions, changes or deletions of various values about the job. It will also define who made the change, the day and time the change was made, and what the old values were replaced with
  • Please note that any changes made to the Job prior to this update will not be reflected in the UI
• Resolved an issue where scheduled triggers could be added through the UI in situations when they were not supposed to be
• Resolved an issue where the History tab filters could break after clicking into and then back out of a record with filters applied
• Updated strange styling issues when creating a new Organization through the new Organization wizard
• Updated strange styling issues surrounding the Last Ran date sometimes displaying 12/31/9999
• Updated the “Clone a Job” functionality to include the custom JavaScript in the Script Engine
• Updated a styling issue with the History filtering window doing the sliding animation when it was not supposed to
• Updated the History filtering window to remove filter badges when clearing out all filters
• Resolved an issue where list settings were disappearing from the UI when clicking into then out of them
  
  

NetSuite Connector 

• Inventory Puller
  • Overall refactor of the puller to be more efficient through NetSuite Advanced Search rather than GetList
  • Added additional filter settings for customizability
• Quote Puller
  • Added settings to define what NetSuite custom field stores the external id values. These values are now populated in the appropriate area on the MCO.
• Customer Puller
  • Resolved an issue where custom fields defined in the external id settings were not being validated in the NetSuite environment
• Order Puller
  • Resolved an issue where Return Authorization ids were not being pulled
  • Resolved an issue where a critical error could occur when pulling an item number

BigCommerce Connector

• Quote Puller
  • Added settings to define what b2b edition extra field stores the external id values. These values are now populated in the appropriate area on the MCO.
• Customer Pusher
  • Added new setting to map a MCO field using M1 linq syntax to a Customer Attribute in BigCommerce
  • Added new setting to map a MCO field using M1 linq syntax to a Customer Address Form Field in BigCommerce
• Order Pusher
  • Resolved an issue where when creating a new customer address on an order in a situation where the mandatory fields of first or last name are blank, SynchUP would silently fail to create the address without logging that failure. This situation will now display as a warning in the logs for that record
    
    

Listrak Connector 

• All Pushers/Pullers
  • Updated error handling and fault tolerance of the API calls to be more robust
• Email Pusher
  • Changed Transaction Log Filter setting to be optional rather than mandatory

SFTP Connector 

• All Pushers/Pullers
  • Resolved an issue where invalid SFTP credentials would throw an unhandled exception rather than handling it gracefully with friendly logs

2023.12.20 

SynchUP Core

• Mapping Tab
  • Resolved an issue where if you were to navigate to the Mapping Tab, then click away before it fully loaded, you’d be prompted with an Unsaved Changed modal
• History Tab
  • Improved the user control for Runtime filters to be more user friendly
• Details Tab
  • Resolved an issue where adding a blank value to list settings could delete all the settings in the list 

NetSuite Connector 

• Customer Puller
  • When pulling a Customer record that has addresses, the first and last name of the address on the MCO will now be set to the Customer records first and last name
• Transaction Puller & Order Puller
  • The existing Transaction and Order puller are being sunset and market “obsolete”. This is being done in favor of a new Order puller that’s been created in this release. Both the Transaction and Order puller each did things slightly differently. The functionality from both was combined into a new Order puller. This decision was made to maintain backwards compatibility. Existing jobs using one of these pullers can migrate to the new Order puller version.
• Order Puller 2.0
  • Added support for NetSuite Return Authorizations 

Listrak Connector 

• Email Pusher
  • Added functionality to now target the Refunds property on the MCO when sending emails 

BigCommerce Connector  

• Product Pusher
  • Updated the Default Category Id setting to be optional. Additionally added better support and verification that the value in this setting exists in the BigCommerce store
• Order Pusher
  • Improved functionality when supplying shipping_carrier and shipping_provider fields 

2023.12.6 

SynchUP Core

• Worker Core
  • Added additional resiliency when a worker retrieves the Job definition upon Run startup. Sometimes a Run would get stuck in a “Queued” or “Processing” state and would no longer start additional Runs afterwards
• History Tab
  • Resolved an issue where the “Hide Zero Details” filter would become stationary when scrolling and become “too sticky”
  • Resolved a UI issue in dark mode where a white box would appear in the filter section
  • Resolved an issue where some Jobs with a default mapping schema would not be able to be enabled
  • Resolved an issue where a very specific order of operations could cause the mapping schema from one Job to overwrite the mapping schema of an unrelated Job 

NetSuite Connector 

• All Pushers
  • Updated log text to be uniform and clear when stating settings do not exist in your NetSuite environment
• Invoice Pusher
  • Added new settings to define and specify which custom field in NetSuite contains the external id for an invoice. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which custom field in NetSuite contains the external id for an invoice customer. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which custom field in NetSuite contains the external id for an invoice address. If set, then follow SynchUP standard record matching rules for internal and external ids
• Customer Pusher
  • Added new settings to define and specify which custom field in NetSuite contains the external id for a customer. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which custom field in NetSuite contains the external id for a customer address. If set, then follow SynchUP standard record matching rules for internal and external ids
• Quote Pusher
  • Added new settings to define and specify which custom field in NetSuite contains the external id for a quote. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which custom field in NetSuite contains the external id for a quote customer. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which custom field in NetSuite contains the external id for a quote address. If set, then follow SynchUP standard record matching rules for internal and external ids
• Transaction Puller
  • Added additional error handling for certain situations that caused a null reference issue 

BigCommerce Connector

• Product Pusher 
  • Added new settings to define and specify which attributes in BigCommerce contains the external id for a product. If set, then follow SynchUP standard record matching rules for internal and external ids
• Customer Pusher
  • Added new settings to define and specify which attributes in BigCommerce contains the external id for a customer. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which attributes in BigCommerce contains the external id for a customer address. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added support for modifying the field “Store Credit Amount”
• Inventory Pusher
  • Added new settings to define and specify which attributes in BigCommerce contains the external id for a product. If set, then follow SynchUP standard record matching rules for internal and external ids
• Order Pusher
  • Added new settings to define and specify which attributes in BigCommerce contains the external id for an order customer. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which attributes in BigCommerce contains the external id for an order customer address. If set, then follow SynchUP standard record matching rules for internal and external ids
• Quote Pusher
  • Added new settings to define and specify which attributes in BigCommerce contains the external id for a quote customer. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which attributes in BigCommerce contains the external id for a quote customer address. If set, then follow SynchUP standard record matching rules for internal and external ids 

Listrak Connector 

• All Pullers & Pushers 
  • Improved fault tolerance when making requests to the Listrak API. When the Listrak API experiences intermittent outages SynchUP will now wait and try the API call again a few times before ending the Run in an error 

Deacom Connector 

• Order Puller 
  • Improved error handling when pulling orders. No longer masking legit errors that should have been exposed 

2023.11.08

SynchUP Core

• A new major feature has been implemented called the SynchUP Script Engine. This feature allows you to use JavaScript syntax to modify and transform the MCO after the Translation Engine has completed. For more information please visit the following Snapshot Knowledge Base Article:
• • https://support.snapshotdesign.com/knowledge/synchup-mapping-script-engine 

BigCommerce Connector 

• Order Pusher
  • Updated the order pusher to support updates to ShipTos and Shipping Addresses. The system now has the capability to integrate new ShipTo details or Shipping Addresses into an existing order when such information is not previously recorded 

• Company Pusher
  • Added new settings to define and specify which form field in B2B Edition contains the external id for a company. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which form field in B2B Edition contains the external id for a company address. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which form field in B2B Edition contains the external id for a company user. If set, then follow SynchUP standard record matching rules for internal and external ids 

• Invoice Pusher
  • Added new settings to define and specify which form field in B2B Edition contains the external id for an invoice. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which form field in B2B Edition contains the external id for an invoice customer. If set, then follow SynchUP standard record matching rules for internal and external ids 

NetSuite Connector  

• Order Pusher
  • Added new settings to define and specify which custom field in NetSuite contains the external id for an order. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which custom field in NetSuite contains the external id for an order customer. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which custom field in NetSuite contains the external id for an order address. If set, then follow SynchUP standard record matching rules for internal and external ids 

• Company Pusher
  • Added new settings to define and specify which custom field in NetSuite contains the external id for a company. If set, then follow SynchUP standard record matching rules for internal and external ids
  • Added new settings to define and specify which custom field in NetSuite contains the external id for a company address. If set, then follow SynchUP standard record matching rules for internal and external ids 

• Transaction Puller
  • Properly pulled and normalized NetSuite Items field “Amount” to the MCO LineItem.SubTotal property 

• Order Puller
  • Properly pulled and normalized NetSuite Items field “Amount” to the MCO LineItem.SubTotal property 

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 

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.09.27

SynchUP Core

• History Tab
  
  • Corrected an issue where the "Hide Zero Details" filter's state would not persist when clicking through to history details
  • Moved the "Hide Zero Details" filter to the top of the filters list, as it is the most frequently used filter
• Error Emails
  • Corrected an issue where Runs that had an extreme number of errors would exceed the max email size and users would not receive an error email for that Run
  • Error emails will now only show the first 10 errors that occur on a Run
  • Individual error messages will be truncated after 250 characters
  • Emails will now state to log into your SynchUP environment to see full error messaging
• When viewing Jobs by connector, Jobs are now alphabetical
• Corrected an issue when logging in where sometimes you'd get an "unexpected server error" message
• Corrected an issue where the Enable button on a Job would throw an error when clicked under certain conditions
• Added additional resiliency when saving payload data after a Run has completed

Deacom Connector

• Customer Puller
  • Added a new boolean setting that if set to true will only pull modified child ShipTos/BillTos
• Customer Pusher
  • Added a new setting that allows the specification of BillToAddressID. This will assist in customer matching

BigCommerce Connector

• Product Pusher
  • Corrected an issue where no logs were being displayed
  • Corrected an issue where the Run would critically fail with Variable Quantities
  • Corrected an issue where logs would be incorrect if the product did not have a title
• Customer Pusher
  • Added a new boolean setting that if set to true will delete Address Book entries which are not present on the MCO

NetSuite Connector

• Transaction Puller
  • Corrected an issue where the Run would critically fail when a transaction contained no web active products

2023.09.13

SynchUP Core

• A new Mapping tab has been added to the Details page of a Job. This Mapping tab contains the schema that drives the SynchUP Translation Engine. Modifications to this schema may be made to change the mappings of the Job as well as adding or modifying any Logic-based Translation Rules
• Resolved an issue on the History table of a Job where all Records shows that they were triggered as "Automatic" even when they weren't. The correct value is now displayed
• Resolved a styling issue with the datetime drop down on the Run Now modal
• Added additional error handling on the backend when saving history records. This will improve resiliency when jobs finalize

Listrak Connector

• Customer Pusher
  • Resolved an issue where emails were not found in Listrak even though they sis exist. The issue was mismatched casing. Set the pusher to ignore casing when looking up emails in Listrak

NetSuite Connector

• Transaction Puller
  • Resolved an issue where the "Transaction to Include" setting wasn't respected in some circumstances
  • Resolved an issue where some Records would get an "Object reference" error

2023.08.16

SynchUP Core

• Updated order of operations when finalizing a job. Previously we updated the Job status to pending after Payload data was saved. In instances of large amounts of Payload data this could delay the next job run by several minutes. We now update the Job status to Pending prior to saving Payload data. This allows the next Run to begin regardless of how long it takes to save Payload data.

Listrak Connector

• Customer Subscription Pusher
  • Updated the logic for the attribute "SubscriptionStatusOverride". If this attribute is set to "subscribed" or "unsubscribed" we will now look for the email under ContactInfo. Previously we were looking under Subscriptions for email 
    • Note: Default functionality when not using the attribute "SubscriptionStatusOverride" is left unchanged and will continue to look at subscriptions for email.

BigCommerce Connector

• Order Pusher
  • Updated incorrect pricing in certain circumstances

NetSuite Connector

• Multiple Pullers
  • Resolved an issue where WebData wasn't getting pulled for all product types 
  • For matrix products in NetSuite, updated the normalization to the MCI to only include the child Item Number. For Example: "123 : 123 ABC : 123 ABC XYZ" is now normalized as "123 ABC ZYX"

2023.08.02

SynchUP Core

• Added a new filtering feature for the History tab. A new filter section can be toggled by clicking the filter icon in the upper left corner of the History table. Each column of the History table can now be filtered based on a selection of the user's choice. The filters will remain sticky even while navigating to different history records. A "clear filters" button is present to quickly remove all filters and display all history records. 

BigCommerce Connector

• Customer Puller
  • Enhanced the Customer Puller to pull all addresses. Previously, we were only pulling 50 addresses.

M1 Api Connector

• Core
  
  • When internal dependencies, such as Direct commerce listeners, are unavailable, SynchUP will now classify that as a "Critical" error for the run. Previously, it was classified as a "Failed" error for all records of the run. 

NetSuite Connector

• Transaction Puller
  • Resolved an issue where Item Fulfillment records pulled out of NetSuite displayed $0 item prices on the Payload.

Deacom Connector

• Order Puller
  • Two new settings have been added surrounding external ids for bill tos and ship tos. If set, the puller will now check the specified user fields in Deacom for the data and if present, will populate the value of that user field on the respective external id on the MCO. 

2023.07.19

SynchUP Core

• Security & Performance Updates
  • Updated frameworks and dependencies to the front-end of SynchUP. This is to improve security and the user experience.
  • Updated frameworks and technology surrounding the way payload data is saved and retrieved. Performance has been improved for both the end user and processes within SynchUP. Additionally, the new technologies used opens the door for additional future features that weren’t possible prior.
• Further improved the reliability of the worker when encountering unexpected critical errors.

BigCommerce Connector

• Product Pusher
  • Resolved an issue where Products would not be created if ParentProductId was null on Payloads
• Customer Puller
  • Added support to pull more than 50 addresses on a customer record

M1 Api Connector

• Order Pusher
  • Updated the status type for the record from “Failed” to “Warning” if an order already exists within M1 Api
  • Added support for additional non-standard state code abbreviations

Listrak Connector

• Product Pusher
  • Added additional logging displayed to the user about how the data is
    transformed or modified in some way prior to sending the data to Listrak

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

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.05.10

SynchUP Core

• Added support across the application for time zones. All times that are displayed throughout the site should now display in the browser's current time zone. Previously, most all times were displayed in EST.

Listrak Connector

• Order Pusher
  • Resolved an issue where some instances were throwing an unhandled key error

BigCommerce Connector

• Order Pusher
  • Added logic to give appropriate validation error messages in the instance where ItemNumber is null on LineItems. Previously this resulted in a null reference exception
• Customer Pusher
  • Added logic to support the instance where certain scenarios would obscure an error message thrown by the BigCommerce API, resulting in a false successful message

Deacom Connector

• Customer Puller
  • Added logic to support the instance where certain instances of StartDate and EndDate passed into the APIwere obscuring an error message thrown by the Deacom API, resulting in a false successful message

2023.04.26

SynchUP Core

• Updated Next Run Time to display as "HH:MM AM/PM TZ" for clarity
• Ran issue where Run Duration is missing from the Job Detail Header when manually running a job
• Improved overall performance regarding SynchUP workers saving history. History Runs are now immediately written and are viewable in the UI. Added states for Runs of “Queued” and “Processing”. Records are written as they are processed in real-time so you can see the progress of the Run as it's happening.
  • Architectural changes for saving history have been made to allow easier future backend performance changes without affecting backwards compatibility
• Fixed a UI issue where the History tab would go invisible when hovering a mouse cursor over it
• Jobs on the Dashboard are now sorted alphabetically
• Resolved a display issue where Runs that resulted in a critical error would display "Unsupported Worker" as the Date Range. This now displays the correct Date Range instead. Previous Runs will not be retroactively updated and will continue to display “Unsupported Worker” for the Date Range
• Updated performance of Worker queue service to start the job closer to the top of the minute that the new Run is scheduled to start. Previously it could start at any point during the minute scheduled to start
• Improved the UX of a user attempting to log in to a subdomain they do not have access to. The website will now redirect them to reauthenticate. If they still do not have access, it will redirect the user to the account management portal so they can select a subdomain they have access to

M1 Api Connector

• Order Puller
  • Resolved an issue where a null reference exception could occur when pulling Orders under
    certain circumstances

NetSuite Connector

• All Pullers/Pushers
  • Added support for External Id Custom Field settings to use any NetSuite custom field type.
    Previously it was restricted to only allowing String custom field types.

BigCommerce Connector

• All Pullers/Pushers
  • Added a fault tolerance for all API calls when receiving 503 errors back from the BigCommerce API. SynchUP will now wait 1 second after a 503 error and attempt the request again. If after several attempts the API continues to give a 503 error, it will log it
    and move on
•  Customer Pusher
  • Resolved an issue where the "Suppress Customer by Email Lookup" setting wasn't being
    respected
  • Updated the BigCommerce Customer Pusher to support the updating of addresses that
    total greater than 10

2023.04.12

SynchUP Core

• When selecting a date range in the "Run Now" nodal the dates selected would append the current seconds on the clock.  The functionality now set the Min Date seconds to be "00" and the Max Date seconds to be "59"
• Added functionality to the Translation Engine to allow the default mapping rule to contain empty
  string
• Updated translation engine functionality to properly copy over null values from source to
  destination systems
  • Several additional enhancements have been made to job history architecture to further increase
  performance
  • Updated Page Title and Favicon for SynchUP rebranding

M1 API Connector

• Customer Pusher
  • Resolved an issue where if Country were null a serialization error would occur

NetSuite Connector

• Added some more friendly validation logic to the "Image Domain" setting used in several pullers and pushes. The validation now properly appends http or https, validates that the url used in a valid NetSuite SuiteCommerce site and the setting is no longer required for clients who do not have a
  SuiteCommerce site
• Customer Puller
  • Resolved an issue where when pulling large amounts of customers an id collision could occur causing the job to fail
  • Added functionality to pull the parent Company Id if it exists on the NetSuite customer record
• Company Puller
  • Added new settings that allow the mapping of a NetSuite child Contact to the Admin and User fields on a Company MCO. The setting allows you to specify a custom field and value. If that value is present on a child Contact, then that Contact will be mapped to the Admin or User MCO field
  • Added a setting that allows the puller to specify what custom field in NetSuite should map to externalId on the Company MCO

BigCommerce Connector

• Renamed "BundleB2B" to the newly rebranded "B2B Edition" wherever applicable
• Product Pusher
  • Resolved an issue where when a job contains a large amount of products the job could fail
• Invoice Pusher
  • Updated the logic of where to acquire customerId when externalId on the MCO is not present
• Company Pusher
  • Added a new setting to specify what field in BigC the externalId of the Company should be saved
• Pricing Level Pusher
  • Resolved an issue where if min quantity was higher than max quantity an error was thrown back from BigC. This also occurred if MinQuantity was not specified
• Customer Puller
  • Resolved an issue where not all translation rules were updated for newly added fields on the Customer MCO

Listrak Connector

• Customer Subscription Pusher
  • The Listrak Customer Subscription pusher checks to see if an email exists in Listrak to know whether it should update the subscription. If it does not exist Listrak gives a 404 Restful response. Previously this 404 was being logged as an error. It is now being logged as informational

2023.03.29

SynchUP Core

• MCO
  • Order
    • Added Comment fields to the Order entity
  • Customer
    • Added customer info such as name, phone, and email to the address objects on a Customer entity
• History UI
  • Fixed an issue where the Triggered column in the History view was not displaying data
  • Improved the UX of loading Log and Payload tabs to provide visual indications when waiting on data loading from the API
  • Improving database performance for retrieving history data. Should see a noticeable increase in performance when viewing History Details

BigCommerce Connector

• Customer Pusher
  • Added a new setting that allows the mapping of MCO data to BigCommerce Customer Form Fields
  • Added support to push extra customer info such as name, phone, and email on the address object of a Customer
• Order Puller
  • Improved the efficiency of the API calls retrieving product data. This has improved the speed of completing BigCommerce Order Puller jobs
  • Now pulling customer_message field. This is mapped to the new Comment fields on the Order MCO
• Product Pusher
  • Improved the efficiency of the API calls retrieving product data. This has improved the speed of completing BigCommerce Product Pusher jobs
• Company Pusher
  • Added  a new setting that allows the mapping of MCO data to B2B Edition Extra Fields
• Quote Pusher
  • Added  a new setting that allows the mapping of MCO data to B2B Edition Extra Fields
• Invoice Pusher
  • Added  a new setting that allows the mapping of MCO data to B2B Edition Extra Fields
• Order Pusher
  • Added  a new setting that allows the mapping of MCO data to B2B Edition Extra Fields
• Customer Pusher
  • Added  a new setting that allows the mapping of MCO data to B2B Edition Extra Fields

Deacom Connector

• Customer Puller
  • Resolved an issue where Deacom Billto and Sihpto customer records were being treated as separate customers. They are now appropriately related on the MCO where Shipto customers are address records
  • Added support to pull extra customer info such as name, phone, and email on the address object of a customer

NetSuite Connector

• Order Puller
  • Resolved an issue where the values that needed to be entered in the Status Filter setting weren't clear. updated log messages in the job and updated the Snapshot Knowledge Base with list of valid values to be entered
• Invoice Pusher
  • Added  a new setting that allows the mapping of MCO data to NetSuite Custom Fields
• Quote Pusher
  • Added  a new setting that allows the mapping of MCO data to NetSuite Custom Fields
• Company Pusher
  • Added  a new setting that allows the mapping of MCO data to NetSuite Custom Fields
• Customer Pusher
  • Added  a new setting that allows the mapping of MCO data to NetSuite Custom Fields

2023.03.15

SynchUP Core

• Rebranding! M1Connect has been rebranded to be SynchUP!
• Added new properties to the Order MCO to support PayPal transaction information

M1 Api Connector 

• Order Pusher
  • Added support to utilize the new PayPal transaction properties and push PayPal information to M1 Api

NetSuite Connector

• Bugs
  • Resolved an issue with the Product Puller where Products were not getting pulled under certain circumstances. This was hotfixed back to 2023.02.01

2023.02.15

BigCommerce Connector

• Customer Puller
  • Added address ID to pulled data to assist in address matching in destination systems
• Invoice B2B Edition Puller
  • Added functionality
• Order Puller
  • Added BundleB2B Support
• Order Pusher
  • Added BundleB2B Support
• Product Pusher
  • Miscellaneous bug fixes
• Quote BundleB2B Pusher
  • Added functionality

NetSuite Connector

• Company Puller
  • Added functionality
• All Pullers
  • Added retry to all API Calls to obtain data and cause an error to be logged while maintaining job processing
• Quote Puller
  • Added functionality
• Transactions Puller
  • Added setting to add not to record when data was last pulled
  • Added ability to set a Custom Field in NetSuite indicating that the record was pulled
  • Added a setting that if Custom Field is marked "true" it will not pull the record a second time

SFTP Connector

• Invoice Puller
  • Added functionality 
• Invoice Pusher
  • Added functionality
• Quote Puller
  • Added functionality
• Quote Pusher
  • Added functionality
• Company Puller
  • Added functionality
• Company Pusher
  • Added functionality
• All SFTP Pullers
  • Added logic to pull data from files based on last modified date (oldest-first) of the files, when constructing the payloads

2023.02.01

BigCommerce Connector

• Order Pusher
  • Corrected formatting of currency to be two decimal places
  • Improved process of passing order totals when creating/updating orders
• Product Pusher
  • Updated logic to use "ShowOnWebsite" to set the IsVisible flag inside of BigCommerce

Listrak Connector

• Order Pusher
  • Bypass translating Shipping Recipient data if it is not populated in the payload

NetSuite Connector

• Order Puller
  • Added Setting to filter orders by status
• Transaction Puller
  • Added Setting to filter orders by status
  • Added Setting to pull transactions by created date vs updated date

SynchUP Core

• Core
  • Updated core logic to operate asynchronously to improve logging
  • Improved performance on Joh History & History Details pages

2023.01.18

NetSuite Connector

• Order Pusher
• Updated Setting used for ExternalID to utilize the name of the custom field instead of the numerical ID, to store the data
• Pricing Level Puller
• New Data Puller

SFTP Connector

• All Pushers
  • Updated Setting used for ExternalID to utilize the name of the custom field instead of the numerical ID, to store the data

SynchUP Core

• Improved parsing of Job Run Condition field and displaying on the UI in a more reader-friendly text
• Clarified Time zone ambiguity in multiple areas in Job History
• Enhance US & Canada state recognition to include US & Canadian Territories as well as Armed Forces installments
• Updated Error Emails to remove duplicate notifications
• Improved Functionality of GetAttribute syntax to allow special characters inside the default value parameter
• Update Ready/Incomplete badge on connector to accurately reflect optional settings
• Improved visual appearance of List Settings on Client site to separate individual values by a line break instead of a comma

2023.01.04

BigCommerce Connector

• Corrected various errors when pushing orders
• Corrected regression of Order Shipped Status when pushing orders

Deacom Connector

• Corrected various errors when pulling orders
• Implemented update of ExternalID when ShipTo is found but, External is missing.

M1 Api Connector

• Updated Model to include Customizations, so it can be passed successfully to M1 Api

NetSuite Connector

• Corrected collision of IDs when using multiple Entity Types(e.g. Customer & Contact) when configured on customer puller

SynchUP Core

• Corrected misaligned time zones in multiple views of SynchUP Job History

2022.12.21

SynchUP Core

• Reviewed and Cleaned up default Schemas across all Pullers/Pushers to ensure completeness and all using common Schema
• Updated SynchUP and workre to use lates .NET 6 platform
• Pull All option setting added to Interval and Scheduled Triggers
• Expansive logging to all of SynchUP endpoints and Data access
• Pointed SynchUP to utilize Azure repository for external code packages
• Translation Engine updated to handle null Child Objects instead of Shallow Copy

BigCommerce Connector

• Order Pusher
  • Corrected log messages on fulfillment creation to state 'created' instead of 'updated'

Deacom Connector

• Order Pusher
  • Implemented ability for ShipTo externalID create, on order Update
  • Various error checking and validation

Listrak Connector

• Order Pusher
  • Added log record to historical tab when a record has been skipped due to resend configuration

M1 Api Connector

• Order Puller
  • Added Refund object to M1 API Response

NetSuite Connector

• Order Pusher
  
  • Added pushing of ExternalID to a custom field

2022.12.07

BigCommerce Connector

• Customer Puller
  • Added missing properties of the customer to MCO Attributes
• Inventory Puller
  • New DataPuller which pulls data of type InventoryItem
• Order Pusher
  • Resolved multiple issues surrounding pagination of data from BigCommerce
• Product Pusher
  • Added ability to control max/min length to text customizations 
  • Implemented delete functionality on product options

Deacom Connector

• Customer Pusher
  • Added DataPusher support for Customer data
• Order Puller
  • Implemented ability to filter orders by the t_slid field by configurable settings 
• Order Pusher
  • Implemented additional logic when trying to match BillTp and ShipTo Records by IDs prior to creation of new records
  • Switched CreateOrder endpoint from using an HTTP get request to using the HTTP Post endpoint, which allows for longer length requests and transmitting special characters without encoding

M1 Api Connector

• Customer Puller
  • Implemented retry policy when trying to obtain Customer Data from M1 API

SFTP Connector

• All Entries
  • Added DataPusher of all entity types to submit JSON data to a specific SFTP Server

2022.11.16

SynchUP Core

• Updated the History Summary data table to support item counts per page of 10/25/50/100 temporarily deactivating the Display Count column and supporting Hide Zero Details button for performance reasons

BigCommerce Connector

• Pricing Level Pusher
  • Resolved an issue where external ID was incorrectly being saved
• Customer Pusher
  • Resolved an issue where external ID was incorrectly being saved
• Product Pusher
  • Added the ability to write custom fields. New settings allow for the mapping of the MSO via SynchUP linq syntax to dynamically populate BigCommerce custom fields
  • Updated the writing of meta fields to have read and write permissions. Previously only had write permissions
• Customer Puller 
  • Resolved an issue where Title, Address 3, Address Type and other attributes were missing

Deacom Connector

• Order Pusher
  • Improved logging and the handling of master orders

M1 Api Connector

• Resolved an issue with all pullers where the connector was processing the incorrect minimum API Level Puller
  • Added a new pricing Level Puller for M1 API
• Order Pusher
  • Updated the Order Pusher to have the Company, Division, and Source Code setting as optional. The settings now function as the "default" values passed to M1 API. The Pusher will now first check to see if there are attributes on the MCO. If there are not, it will fail and not be passed to M1 API
• Product Puller
  • Resolving an issue where the first variation on the MCO was not necessarily the header style product