The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
Once these records have been defined, they can be communicated to a connected eCommerce channel. Support for bi-directional integration is included, making it possible to send changes from Business Central to the external environment, but also retrieve changes from the external environment and update the corresponding Business Central records accordingly. Logic has also been extended to CSM’s order management functionality so that orders placed by B2B users are appropriately identified as such when they are retrieved into Business Central.
This functionality has been added to initially support an upcoming BigCommerce integration, but will also be incorporated into other CSM integrations.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
Sales channels that are using both CSM’s legacy and modern API Engines now have the ability to execute the Test Channel Communication action for either one.
A new Shipping Order Behavior field has been added to the CSM Shipping Method This field is used to either follow the default behavior of adding sales lines to orders for shipping charges or skip this activity. This is useful in scenarios where a company wants to map channel shipping methods to Business Central shipping agents, but does not want to include shipping charges on the order.
A new cross-reference CSM Currency table has been added to CSM sales channels. This allows users to map Business Central currency codes to currency values that are retrieved from an eCommerce channel.
New Business Central source types have been added to CSM item attributes. It is now possible to map CSM item attributes to any field on the Business Central Item and Item Unit of Measure In addition, logic has been added to support mapping to custom tables, which is useful if a company is maintaining its attribute data in something other than a standard Business Central table.
The ability to use Business Central’s marketing text table as the source of CSM listing descriptions has been added to the application.
The Synchronize Item Attributes action which was previously available only on the CSM listing card has been added to the list page, allowing users to perform this action against multiple records at once.
A new CSM Listing Synchronization History table has been added to CSM listings. This table presents a history of any attribute synchronization actions that were performed against the listing, including information as to whether or not the action was successful.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
An issue with the integration between CSM and CPM existed where in certain scenarios an eCommerce channel’s status was not reflecting that it had been fully paid. This has been corrected.
Sending a CSM listing’s pricing group pricing information to an external channel did not work if the listing was mapped to a resource. This has been corrected.
A mapping issue was preventing the retrieval of products with certain special characters from an external channel into Business Central. This has been corrected.
CSM Core has been compiled against Microsoft Dynamics 365 Business Central 2024 Wave 1 (version 24) for compatibility issues. No issues were detected and no immediate changes to the extension were necessary. A number of clean-up activities were performed to accommodate changes or upcoming deprecations that were introduced with this release.
New integration events to calculate and check an order’s balance have been added to the CSM Order Header table.
A new integration event for splitting retrieved order notes has been added to the CSM Create Sales Order table.
A new design pattern for the loading of default and demo data has been implemented for CSM Core.
CSM Core’s subscription configuration has been updated to automatically include the standalone API Engine library as part of new subscriptions.
To support an upcoming CSM for Amazon release, a new Auto Assign Lot Boolean field has been added to the CSM Sales Channel table. This field is only visible for Amazon FBA sales channels, and allows CSM to automatically assign lots to lot-tracked items on FBA orders.
When CSM would post a retrieved refund to a customer ledger, it would assign the payment method that was assigned on the customer’s card to the ledger entry, rather than the payment method that was retrieved from the sales channel. This has been corrected.
CSM sales channel, order, and order document fields have been added to the Customer Ledger Entry table, allowing users to identify the CSM activity associated to a particular ledger entry.
New Bal. Account Type and Bal. Account No. fields have been added to the CSM Payment Method table. This allows users to define a channel-specific balancing account for a given CSM payment method, rather than requiring that a balancing account be defined for the related Business Central payment method.
It is now possible to place order notes that have been retrieved from a sales channel on a sales order in Business Central.
CSM Core has been refactored to use the version of the API Engine that was introduced as a standalone extension in 2022. This standalone API Engine features many improvements over the original API Engine that was included as part of CSM, so refactoring CSM to use this improved version will have many benefits. As Suite Engine develops new features and functionality for its eCommerce extensions, this new version of the API Engine will be used. However, the refactoring process was performed in such a way that it is possible to execute specific API functions according to either the new or old API Engine in CSM. In this way, a current user of CSM can use newly-developed functionality with the new API Engine while continuing to use the old API Engine for all of their existing processes. Following this CSM Core refactor, Suite Engine will refactor its individual eCommerce platform extensions, allowing companies to migrate all of their API functions to the new API Engine.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
When attempting to retrieve CSM orders for a CSM channel with a customer behavior setting of Manual, any failures in order creation would cause the entire automation process to end. This has been corrected so that a single failure does not terminate the entire automation process.
If an API set code was not assigned to a CSM shipping method, CSM’s order creation process was unable to map that CSM shipping method to a Business Central shipping agent. This has been corrected.
A new External Document No. Format field has been added to the CSM Sales Channel table. Previously whenever CSM created a new sales order from retrieved channel data, the external document number was automatically created from the related sales channel and order ID. With this new field, users can choose any field or combination of fields from the CSM Order Header table as the basis for sales orders’ external document numbers.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
Corrections
If CSM was unable to find a payment method mapping for a retrieved order as part of the order automation, the entire automation routine would fail. This has been corrected.
When assigning tax area codes to orders, CSM was prioritizing the CSM order’s ship-to date over and relevant tax area setup in the CSM Country Setup This has been corrected.
When a sales return was created from a CSM order, it was possible to create discrepancies between the sales return amount in Business Central and a connected eCommerce platform by reducing the amount of order-level charges (such as shipping and handling) but not reducing the tax amount on these charges and then releasing the document. This has been corrected.
It is now possible to assign a Business Central resource as the refund discrepancy account on a CSM sales channel.
A Create option has been added to the list of available order processing action types for CSM sales operation rules. This allows companies to develop operational rules to allow or deny the creation of sales orders if certain criteria are met.
It is now possible to automatically create CSM listings directly from the standard Business Central item card.
New integration events have been added to CSM:
A new integration event to support additional scenarios for sending CSM attributes from Business Central to a connected channel has been added to the CSM Listing Management.
A new integration event to filter the types of order documents that are retrieved from a particular channel for a given order has been added to the CSM Order Management.
A new integration event that permits the modification of an order’s last run timestamp following the execution of a single automation task has been added to the CSM Order Management.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
To support an upcoming BigCommerce integration, support for BigCommerce refund quotes have been added to CSM.
CSM’s automation routines would sometimes fail with a G/L inconsistency error if balancing accounts were not assigned to the relevant payment methods. This has been corrected.
Attempting to create a sales order from a CSM order with a coupon value that exceeded the total amount of the order items would fail for some platforms. This has been corrected.
The parent key in certain global key variables was not being cleared/reset between transactions, resulting in data being inserted multiple times on the same order. This has been corrected.
When creating a sales order from a CSM order, CSM would assign the primary contact from the customer card, rather than the contact assigned to the related CSM customer. This has been corrected.
If a customer in Business Central had an assigned ship-to code, this code was being included on sales orders that were created from CSM orders, even if the retrieved order information differed from the default ship-to. This has been corrected to leave the ship-to code blank on any sales orders created by CSM.
Certain Amazon financial transactions were not being entered as part of the related Amazon financial event transaction. This was a CSM Core issue, and has been corrected.
Miscellaneous inaccuracies were corrected on various CSM page tooltips.
A CSM prefix has been added to the captions for assorted pages to prevent confusion when similar objects from the standalone API Engine are present in the same environment.
To support an upcoming Shopify integration, new flexibility to the way in which variation options and their values are sequenced has been added.
The External Preview URL and External Admin URL fields on the CSM Listing and CSM Listings pages have been hidden by default. As functionality supporting these fields is added to specific platform extensions, these fields will be made visible for those platforms.
Attempting to send a CSM listing to a connected eCommerce channel would result in a “the changes to the CSM listing record cannot be saved…” message. This has been corrected.
CSM Core has been compiled against Microsoft Dynamics 365 Business Central 2023 Wave 2 (version 23) for compatibility issues. No issues were detected and no changes to the extension were necessary.
The Load Products from Channel action has been improved to assign a channel’s default inventory availability calculation settings to all CSM listings that are created as a part of this process.
Additional logic has been added to accommodate scenarios where the total on a refund retrieved from a sales channel does not match the total on the credit memo built by CSM in Business Central. In such a scenario, an additional line for the discrepancy amount is added to the credit memo.
The default long and description setting for sales channels has been re-worked to allow for sources beyond CSM’s out-of-the-box selections.
It is now possible to define a maximum run time for CSM’s housekeeping automation.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
If a user started the process of creating a sales return from a CSM order, cancelling this process would still result in the creation of a blank sales return. This has been corrected.
Attempting to link a CSM attribute that was retrieved from an external platform to an item attribute in Business Central would result in an error. This has been corrected.
When sending a CSM attribute to an external platform, CSM would attempt to send option values for non-option attributes. This has been corrected.
When creating listings for configurable items, CSM would assign the parent item’s unit of measure to all of its children, rather than use any unique SKU units of measure that have been defined for the children. This has been corrected.
Deleting a CSM listing with an image that had been retrieved from an item record would result in the image being deleted from the item, as well. This has been corrected.
A number of new cues have been added to the CSM Administrator role center to highlight orders or other records with errors or failures to process.
A new Run Automation action has been added to the CSM Automation List This can be used to execute a specific automation routine for testing/troubleshooting purposes.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
For certain CSM enumeration fields, a blank value was being represented by a numerical value rather than a blank. This has been corrected.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
A G/L inconsistency error message would be displayed when attempting to post a sales order if the order’s payment method did not have an assigned balancing account. This has been corrected.
A new OnAfterCSMCustomerAdded integration event has been added to the CSM Wizard
New fields for excluding the sending of G/L account and resource lines as part of shipments have been added to the CSM Sales Channel table. If these fields are enabled and CSM sends shipment information from Business Central to update an order on a connected platform, any G/L account and/or resource lines will be skipped. In scenarios where there are a large volume of these line types, excluding these records can reduce the time it takes to execute the order automation.
Several improvements have been made to the Create CSM Listing from BC Items action that is used to create CSM listings for multiple Business Central items at once:
A “last used options and filters” option has been added to allows users to run the action according to a standard set of criteria.
A new Item No. option has been added to the SKU Number assignment field.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
To support an upcoming Magento integration, functionality that allows for the retrieval of channel categories from a connected platform has been implemented.
If a CSM setup record was not present in Business Central, any Role Center would display an error message. This has been corrected.
The status text for order document lines on CSM orders that were retrieved to build refund credit memos were displaying placeholder values for variable text, rather than the text itself. This has been corrected.
Dimensions were not being assigned to customer ledger and general ledger entries created by CSM as a result of retrieving and posting refunds from a connected platform. This has been corrected.
Several corrections have been made to the process of creating new CSM attributes for configurable items through the listing wizard:
These attributes were not being properly identified as configurable.
The attribute name was being used to validate whether the attribute already existed as a CSM attribute. This created issues if the attribute’s name was not identical to the existing CSM attribute. This has been changed to use the Link 1 value, rather than the name, when performing validations.
When assigning CSM attributes to an attribute set, the lookup list from the CSM Item Attribute Code field was not filtered to display only those attributes that have been defined for the related CSM sales channel. This has been corrected.
When attempting to open the CSM API Messages list, users would sometimes encounter a JIT load error message. This has been corrected.
The housekeeping automation routine has been optimized for faster performance.
Miscellaneous code clean-up activities that bring CSM in line with Microsoft’s coding guidelines have been completed.
The process by which CSM determines whether CSM is in live or test mode has been moved from platform extensions and to Suite Engine’s subscription extension.
CSM listing prices were being calculated based on the associated item’s base unit of measure, rather than the unit of measure that was specified on the CSM listing. This has been corrected.
When a CSM shipping method was defined with a blank sales channel shipping method, its setup would always be assigned to sales orders, regardless of the retrieved shipping method. This has been corrected.
A new function has been added to create default demo data to support newly-added CSM functionality.
A new CSM upgrade notifications feature has been added to CSM Core. This feature uses standard Business Central notifications functionality to alert users of changes that are made to installed CSM extensions as part of a version upgrade and advise of any actions that must be taken to accommodate these changes.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
A new Item Variation Worksheet has been added to the Suite Engine Variations module. This worksheet allows users to link existing parent and children items/item variants and then build the item variation structure that connects them. This supports scenarios in which both the parent and children records already exist in Business Central, and there is no need to use item variations to generate children for a defined parent.
When creating an item variation option that is linked to a Business Central item attribute, the process would error if the item attribute had an option value with a blank code. This has been corrected.
New integration events have been added to the CSM Create Sales Order and CSM Order Management codeunits.
CSM Core has been compiled against Microsoft Dynamics 365 Business Central 2023 Wave 1 (version 22) for compatibility issues. No issues were detected and no changes to the extension were necessary.
The CSM Core response processor was unable to properly handle mappings to enumeration extensions. This has
been corrected.
In some scenarios, the External Requires Update field was incorrectly set to True for CSM credit memo order
documents. This has been corrected.
The Order Status field on a number of CSM tables has been re-captioned to BC Order Status for added clarity:
CSM Automation (in addition, the corresponding page’s caption was removed to use this updated table caption)
CSM Order Line
CSM Order Line Archive
CSM Order Status
The BC Order Status field in the CSM Order Status table has been changed from an option type field to an enumeration.
Functionality has been added to support the setup of multiple job queues for CSM automation.
A sales order’s channel code and channel order ID are now being populated prior to the insertion of the sales header record. This supports scenarios in which a user wants to assign custom order numbers to channel orders.
It is now possible to aggregate inventory across multiple Business Central locations when calculating item availability for CSM listings.
A new Listing Default Attribute Set field has been added to the CSM Sales Channel This provides additional flexibility in establishing the relationship between a sales channel’s categories and attribute sets:
One Per Category: categories and attributes have a unique one-to-one relationship (this is CSM’s default behavior).
Single: a default listing attribute set can be assigned to the channel. This default will be assigned to all of the channel’s listings, regardless of category.
Multiple Categories: a many-to-one relationship can be established between categories and attribute sets.
The CSM API Messages page has been updated to sort by the Message Initialized field, providing a chronological view (starting with most recent) of API messages.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
To support all channel integrations, the results message that is presented following the execution of the test channel communication action has been updated for clarity.
To support all channel integrations, objects have been added to present display notifications of necessary changes and actions that need to be taken as part of future CSM upgrades.
To support an upcoming Shopify integration, functionality has been added that allows users to initiate and post a return order from a CSM order within Business Central, then update the order on the Shopify platform accordingly.
A number of changes have been made to CSM Core to support an upcoming integration between CSM and CPM:
CSM Core now retrieves an order’s total gift card amount.
A new event trigger was added to prevent CSM from attempting to post an order’s payment in environments where CPM is also installed so that CPM may execute this activity instead.
Refund application functionality that was originally included in the Shopify integration has been moved to CSM Core.
After an API message was passed to a codeunit, the API message was not being refreshed in system memory/the related variable. This has been corrected.
Validating a mapping to an enumeration field would modify the record itself. This has been corrected.
The existing OnBeforeUpdateChannelOrderStatus integration event on the CSM Order Header table did not have all the necessary parameters to completely handle the update logic. This event has been obsoleted and replaced with a new event that has the necessary parameters.
Posting a sales order when Business Central’s work date was earlier than the order date would result in an error. This has been corrected.
The Send to Channel action on the CSM Channel Categories page was mistakenly placed in a separate New This has been corrected.
Attempting to manually assign a CSM parent channel category to a CSM channel category on the CSM Channel Categories page would result in a primary key error. This has been corrected.
CSM listing product information records that were built from extended text had a source type of Value rather than Blob. This has been corrected.
A new integration event has been added to the SENVARL Item Variation Option table to support adding or overriding default values.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
A number of fields were missing from various CSM order archive tables. This has been corrected.
Incorrect/confusing text on the CSM category wizard has been removed.
Completed order status information was not being properly communicated from Business Central to external BigCommerce channels. This has been corrected.
Support for Microsoft Dynamics 365 Business Central 2022 Wave 2 (version 21) has been added to CSM.
A number of CSM objects had code that was not in compliance with Microsoft’s published guidelines. This has
been corrected.
JSON response processing would error during the order automation process if no new orders were available for
retrieval. This has been corrected.
Attempting to send feeds to Amazon would result in an unsupported character message. This has been corrected.
Archive table and page objects did not exist for CSM order document line records. This has been corrected.
Attempting to manually enter a CSM channel primary category on CSM listings would result in an error. This has
been corrected.
The FTP FastTab on the CSM Sales Channel page supported functionality that is no longer used. This FastTab has
been hidden by default. The underlying fields are still present and can be used, if needed.
Miscellaneous field captions have been updated for clarity.
CSM Core’s automated test scripts have been expanded to include additional testing scenarios.
A Generate SKUs action has been added to the item variation card. Executing this action will automatically build
SKU values from a variation SKU’s existing SKU item number, and (if applicable) SKU variant code.
An Update SKU Status action has been added to the item variation card. Executing this action will automatically
update the status of all selected variation SKUs to Active.
It is now possible to link CSM sales channel other charges and CSM shipping methods to Business Central resource records.
A new integration event has been added to allow a subscriber to change the calculation logic of the order total amount in the CSM Sales Header table.
CSM cross references were not being used to populate state/province information for new Business Central customer that were created a result of orders retrieved via CSM. This has been corrected.
A previous CSM Core release was missing the necessary changes to support a correction to the Magento platform integration (“The Channel Payment Method field on CSM orders was not being populated with retrieved data from Magento”). This has been corrected.
This release introduces CSM API function support for JSON content types. By default, CSM will convert JSON data buffer content to XML, but in some scenarios this would create issues if the content could not be properly communicated via XML. For example, retrieval of a channel order with a special character in one of the fields (such as an “&” instead of the word “and”) would previously fail because the special character was not supported by XML.
For most of your existing CSM API functions, no changes should be necessary. If you have received errors or experienced issues due to data buffer content existing in an XML format, however, you can change the related CSM API function’s content type from Data Buffer XML Paths to Data Buffer JSON Paths. This will instruct CSM to generate the data buffer in JSON when executing the related function.
The scenarios in which this change will be needed vary from channel to channel and function to function; if you require guidance as to the specific API functions that need this change in your environment, please consult with your CSM partner contact.
In a previous version of CSM Core, a number of actions in the CSM Administrator Role Center were marked as Obsolete to support deployment in W1 environments. These actions have now been removed:
The Customer List – Order Status page
The Customer – Order Summary report
The Customer – Top 10 List report
The Customer/Item Statistics report
The /Item Stat. by Salespers. report
The List Price Sheet report
The Inventory – Sales Back Orders report
The Sales Order Status report
CSM API functions now generate data buffers via JSON processors.
In a scenario where an archived order was retrieved into Business Central a second time (for example, if a modification was made to the order on the sales channel), an attempt by CSM to archive this duplicate order would result in an error. This has been corrected; when CSM archives an order that has already been archived, a suffix will be appended to the archived order’s ID. For example, suppose we archived CSM order 1234 in Business Central. This order was modified in the eCommerce channel and retrieved by CSM a second time. When this order is archived by CSM, it will be assigned an order ID of 1234-01. If this process was repeated, subsequent archive records would be numbered 1234-02, 1234-03, and so forth.
It is now possible to run the Update Status action against multiple selected CSM orders.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel specific integrations:
To support CSM deployment in W1 environments, the following actions in the CSM Administrator Role Center that are not compatible with W1 have been marked as Obsolete:
These actions will be removed from CSM in a future release.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
A common framework for configurable items has been added to CSM Core. Configurable items refer to products that are available in multiple, variable configurations such as color or size. The specifics of the functionality will vary from platform to platform, but the general structure will remain the same across all integrations:
These features will support configurable item functionality in multiple upcoming platform integrations.
A number of CSM objects had code that was not in compliance with Microsoft’s published guidelines. This has been corrected.
Product data in Stripe was not being refreshed prior to the creation of a new CSM free trial. This has been corrected.
The CSM Discount Allocation field was not being displayed on the CSM Sales Channel page for applicable sales channels. This has been corrected.
An Item Attribute Options 2 page that was created to assist in development activities was accessible to users through search functionality. This has been corrected.
Under certain conditions, the last run time for the SALESORDERLIST function was being improperly updated, resulting in channel orders being skipped during the retrieval process. This has been corrected.
A variable was missing from the API function used to send CSM item attribute sets to a sales channel. This has been corrected.
Deleting a CSM listing would not delete related listing records such as product information, listing children, and listing attributes. This has been corrected.
CSM Core’s automated test scripts have been expanded to include additional testing scenarios.
To support the creation and management of configurable items for sales channels, a new “Suite Engine Variations” library extension has been introduced. This extension assists users in the creation and management of Business Central records that represent a parent item and all of its configurable variations. This module allows you to identify the variable options (such as color) and values (such as red, blue, and yellow) that comprise an item’s configurable variations. You can then instruct Business Central to determine all of the different attribute combinations that exist for the item. Separate items or item variants can be created to represent these variations.
Support for Business Central’s new sales pricing experience has been added to CSM.
New listing import actions have been added to allow for the creation/importing of multiple records at once:
Import Items: this action can be used to create listings for multiple Business Central items at once.
Import Listing Images: this action can be used to import multiple images and assign them to CSM listings
at once.
See the in-depth features description for more details.
It is now possible to run the Send All Listing Data to Channel and Send Listing Base Info to Channel actions against
multiple selected CSM listing records.
Name fields have been added to the lookup pages that are accessed when assigning a table or field to a CSM API
mapping record. Previously these tables contained object ID fields, but with the addition of these new name
fields, it is easier for users to identify the associated database object that they want to assign to the CSM API
mapping.
To support an upcoming Amazon integration, the ability to retrieve a single order from an external platform has
been added to CSM sales channels.
Attempting to open various CSM pages while automation routines were running would result in an error. This has
been corrected.
Deleting a sales channel would not delete associated records in other tables. This has been corrected.
The unit of measure was not being populated on sales lines that were retrieved from an external platform for
items that were mapped via Business Central’s item reference feature. This has been corrected.
CSM Core’s default demo data load has been updated to store demo credentials in Azure Key Vault.
This release introduces a new Channel Shipping Method field (field number 205) to the CSM Order table, which replaces
the Ship Service Level field (field number 200). If you are upgrading your existing CSM integration with this release, you
must make the following changes to ensure that your solution continues to operate as desired:
Functionality has been added to create records in dedicated attribute tables that were introduced in an earlier release to support different attribute data types (attributes, attribute sets, and attribute options). This will support new product features in multiple upcoming platform integrations.
To support shipment method data retrieval activities in multiple upcoming platform integrations, a new Channel Shipping Method field has been added to the CSM Shipping Method and CSM Order tables and their related pages. This field replaces the existing Ship Service Level field, which is where an external platform’s retrieved shipment method code was stored. The existing field entered these retrieved values as Business Central codes, which resulted in a format that was incompatible with some platforms. The new field retrieves these values as text, which will support all data retrieval scenarios. See the upgrade instructions for more details.
A new CSM Shipping Zone table and related page has been added to support shipment method data retrieval activities in an upcoming BigCommerce integration.
To support sales channel payment methods that do not permit multiple payment capture activities against the same transaction, a new Single Capture Boolean field has been added to the CSM Payment Method table. When this option is enabled for a CSM order’s assigned payment method, CSM will capture and send the payment to the sales channel when the related Business Central sales order is fully shipped and invoiced. If the sales order is partially shipped and invoiced, no payment capture is recorded.
Functionality has been added to support gift card management in an upcoming Shopify integration.
A number of CSM objects had code that was not in compliance with Microsoft’s published guidelines. This has been corrected.
When the CSM setup wizard was used to create a new channel that uses an existing API set, leaving the credential information blank in the wizard would result in CSM deleting that API set’s existing credentials. This has been corrected.
Deleting a sales channel did not result in the deletion of that channel’s related CSM automation records. This has been corrected.
Channel-specific field captions on channel orders were not extended to the related archived orders. This has been corrected.
Miscellaneous typos have been corrected.
CSM Core’s automated test scripts have been expanded to include additional testing scenarios.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
Credential management was not properly supporting environments in which credentials are stored against API sets. This has been corrected.
Functionality has been added to allow for the copying of an existing API credential record.
It is now possible to run the following actions against multiple selected CSM listing records:
Send Price Update to Channel
Calculate Channel Availability
A recent release of Microsoft Dynamics 365 Business Channel replaced item cross reference records with item reference records. The following areas of CSM that previously used item cross references have been updated to use item references:
Creation of CSM listing records via the Create Listing Wizard.
Several improvements have been made to CSM API Message records:
A new HTTP Response Status Code field has been added to CSM API Message table. This field displays the server-issued status code that was generated as a response to the message request.
It is now possible to edit a CSM API message’s response and then instruct CSM to reprocess it. See the in-depth feature description for more details.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
There were primary key fields on some CSM tables that were marked as Obsolete. This has been corrected.
Error messaging was unclear when status matrix data failed to load for a sales channel. This has been corrected.
Error messaging was unclear if a user failed to properly assign an archive after days value to channel records. This has been corrected.
The External Tracks Inventory field in the CSM Listing Children List FastTab on the CSM Listing page was improperly captioned. This has been corrected.
Deleting a CSM API message did not result in the deletion of that message’s related CSM API data buffer records. This has been corrected.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
A number of CSM objects had code that was not in compliance with Microsoft’s published guidelines. This has been corrected.
CSM order bill-to names were not being automatically populated upon creation. This has been corrected.
Release Overview
Attempting to process automation routines with a blank sales channel code was resulting in an error. This has been corrected.
Demo validation functions have been added to CSM.
G/L account and transfer route updates were made to the CSM for Amazon demo data load.
Release Overview
Changes have been made so that CSM Core’s API engine can be utilized without a CSM Core subscription:
These changes allow Suite Engine to introduce new products that use the API engine without requiring the presence of a CSM Core subscription.
The following Channel Sales Manager Core changes will support forthcoming features and functionality for channel-specific integrations:
Links to credit amounts in the Sales Channel Order Statistics FactBox that is displayed on channel order lists and pages were not functional. This has been corrected.
Inserting a log entry record would produce a duplicate entry number error. This has been corrected.
Tooltips on the CSM Automation List page contained errors. This has been corrected.
Updated demo credentials have been applied to CSM.
Suite Engine-branded items have been added to the CSM Core demo data load.
Addition of tooltips and captions
Modifications to Data Load Generator to utilize object names instead of numbers for multi-version compatibility
Renaming of objects and variables to comply with current BC Standards
Modifications to allow for conversion and removal of special characters within inbound API response data
Addition of Listing Unit of Measure to Availability Calculation within listing management to allow the calculation to factor in the Qty Per Unit of Measure associated with Listing Unit of Measure
Events added to InsertOrderLevelSalesOrderLines function of the Create Sales Order code-unit to allow subscribers to handle order-level charges differently than the core product
Additional mapping depth flexibility added to ProcessNormalizedNodesForParent function of CSM API Response Management code-unit to allow for processing of Record Nodes nested within Normalized Nodes