KingswaySoft - Data Integration Made Easy

Version 24.1.1 - August 30, 2024

This is a new service release, which comes with the following updates and fixes:

New: CDS/CRM destination component now supports the newly introduced BypassBusinessLogicExecution feature.
Update: CDS/CRM source component now uses proper scales for numeric fields when DT_DECIMAL data type is used. For existing components, a refresh of the component is required.
Update: CDS/CRM destination component no longer sends the matching key fields in update request when working with Manually Specify Record Matching Criteria.
Update: Default Handling of non-matched values option is set to "Leave it as is" in Option Value Mapping Editor in CDS/CRM destination component.
Update: CDS/CRM source component now supports IsChunkingSupported check in order to facilitate a more resilient download when working with file type field. If chunking is detected as not supported, the component won't perform chunk download.
Fixed: CDS/CRM destination component may report "Invalid input value" error when working with NULL values with an optionset field.
Fixed: You may get incorrect GUID and DateTime values returned from a Premium Service Lookup component when no match is found while working against CDS/CRM instance if the Premium Service Lookup component was created by version v23.3 or earlier and upgraded to v24.1.

Version 24.1 - June 18, 2024

The following are the updates and enhancements made for each group of components:

General
- New: The included Premium Service Lookup component now supports returning multiple matching records (including all). This should be considered a breaking change, the component now works as an asynchronous component when the Max Returned Matches option is set to be greater than 1. Any existing references to the _HasMoreThanOneMatch output column in downstream pipeline components should be updated to use the new _HasMoreThanMaxReturnedMatches column instead.
- Update: Premium Service Lookup component now uses Full Cache as the default caching option after the component is created.
- Update: We have introduced a newly designed exception message window for better usability.
- Enhancement: Some additional DPI display optimizations to various forms.
Dynamics 365 CE/CRM & CDS
- New: CDS/CRM connection manager has a new API Version option available in UI, which allows you to specify a particular API version that you want to work with.
- New: CDS/CRM destination component now provides an Option Value Mapping feature which can be used to convert incoming values into valid optionset values along with the ability to create such options on the fly if no match is found in Dynamics.
- New: Dynamics CRM Command Task now supports INSERT INTO ... SELECT statement.
- New: CDS/CRM connection manager now supports custom SSL certificate and custom HTTP headers when working with the WebAPI service endpoint.
- New: CDS/CRM destination component now supports homogeneous batch messages when working with Upsert action.
- Update: We have some updates to our FetchXML query support to work with some of the recent FetchXML features.
- Update: We have updated the SQL to FetchXML parsing engage for better handling of some special cases in the conversion.
- Update: We have removed the dependency on Microsoft.IdentityModel assembly.
- Update: Some improved handling of custom authorization server URLs when working with OAuth authentication.
- Fixed: CDS/CRM connection manager's select organization window might not always use the same authentication option as the connection manager UI.
- Fixed: CDS/CRM destination component may output NULL value to the default output IsNew column when working with a connection manager that uses the WebAPI service endpoint.
- Fixed: CDS/CRM source component might report a KeyNotFoundException when reading from some unique activity entities.
Dynamics 365 F&O
- Fixed: Working with a Dynamics 365 F&O instance using the Upsert or Update action, the AX destination component might report a 404 resource not found error while the records are indeed in the system, this used to happen to the records that contain some very special characters in the key values.
Dynamics 365 Business Central
- New: We added two new OAuth grant types (Client Credentials and Certificate) in NAV connection manager when working with Business Central online.
- Fixed: In case your Business Central company name contains some special characters, you might receive some resource not found errors when working with service calls initiated from either NAV source or destination component.
- Fixed: When working with a SOAP connection manager, the Premium Service Lookup component might report empty values in those LookupResults output columns if the cache mode has been chosen as Partial Cache or No Cache.

Version 23.2.2 - Nov 23, 2023

This is a new service release, which comes with the following updates and fixes:

New: We have added a new "Use Heterogeneous Batch Operation Messages" option to the CDS/CRM destination component which allows you to specify whether to use the recently introduced xMultiple feature including CreateMultiple, UpdateMultiple and DeleteMultiple. The xMultiple messages are only utilized when the option is enabled, unlike our v23.2 and v23.2.1 releases in which we used a batch size threshold as the way to determine whether xMultiple is enabled. During design time, our software will automatically enable or disable the option depending on whether the xMultiple message is supported by the platform, and when the option is changed based on the detection, a toast notification will be shown.
Update: Multi-select option set name fields now have a length of 4000 instead of 255 previously. This can help avoid some buffer overflow errors with the CDS/CRM source components.
Fixed: NAV destination component might not write properly when one of Update or Upsert keys has a value that contains + characters while the manual matching option is used.

Version 23.2.1 - Oct 12, 2023

This is mainly a service release, which comes with the following updates and fixes:

Enhancement: AX destination component now supports flexible field length configuration for its Error Output's AxErrorMessage column, including the support of changing it to be a DT_NTEXT column so that it can accommodate as many characters as needed for the error messages received. This can be useful when the OData message is extraordinarily long.
Enhancement: CDS/CRM destination component now supports flexible field length configuration for its Error output's ErrorMessage column and the SkippedRows output's SkipReasonMessage column, the feature includes the support of changing them to be a DT_NTEXT column so that it can accomodate as many characters as needed for the error messages received. This can be useful when the OData message is extraordinarily long.
Update: CDS/CRM destination component now supports UpdateMultiple messages when SOAP 2011 service endpoint is used if the component's Batch Size setting is greater than 20.
Fixed: You might receive an "Entity Id must be specified for Operation" error when trying to update a record by primary key in a CDS/CRM destination component that uses a connection manager configured for the WebAPI service endpoint.
Fixed: You might receive an "Entity Id must be specified for Operation" error in a CDS/CRM destination component that uses the Upsert action while its connection manager is configured for the WebAPI service endpoint.
Fixed: The input values for statecode and statuscode might get dropped in the update service call for CRM Command Task and CDS/CRM destination component, when using an Update action with a connection manager that is configured for the WebAPI service endpoint.
Fixed: The input values for statecode and statuscode might get dropped in the update service call for CDS/CRM destination component, when System Duplicate Detection is used as the matching criteria.
Fixed: In some very unique situations, you might experience some odd package load issues with existing packages that work in an older release.

Version 23.2 - September 8, 2023

The following are the updates and enhancements made for each group of components:

General
- Enhancement: We have some updates to the License Manager program UI to make it more responsive to changes made to the license installation in the background.
- Update: We have removed SSIS 2008 (Including SQL Server 2008 R2) support.
Dynamics 365 CE/CRM & CDS
- New: We added a new Dynamics CRM Command Task which can be used to translate SQL scripts, including INSERT, UPDATE, DELETE, into operational Dynamics 365 service calls in order to facilitate data write.
- New: We added support for the recently introduced xMultiple messages (CreateMultiple, UpdateMultiple, DeleteMultiple). This feature is automatically enabled when it is supported by the destination entity while the batch size is greater than 20.
- Update: KingswaySoft.DynamicsServices assembly has been updated to be .NET Framework 4.6.2 based. This affects the way where you look for the assembly in case you use any custom script components or tasks that might reference this assembly.
- Fixed: When working with ExecuteWorkflowAction in CRM/CDS destination component, you might receive the "System.NullReferenceException: Object reference not set to an instance of an object" error if the service call's response is empty. This is an issue specific to v23.1 and v23.1.1 releases.
- Fixed: When working with the principalobjectaccess (POA) entity, the Upsert action in the destination component might not perform any creation even if needed.
Dynamics 365 BC/NAV
- New: We added support for OR operator when building an OData query in the NAV source component.
- New: The NAV source and destination components should now work with company-specific metadata in case the metadata is different between companies.
- New: We added support for image/attachment download in NAV source component when working with the REST or OData service endpoint.
- Update: The NAV connection manager should now work with those custom OAuth server URLs that do not follow the typical /oauth2/v2.0/authorize or /oauth2/2.0/token URL path format.
- Fixed: When working with the Create action in the NAV destination component using a REST or OData connection, the destination component might skip the input values for ID field if the batch size is set to 1.
Dynamics 365 FO/AX
- Update: The AX connection manager should now work with some OAuth server URLs that do not follow the typical /v2.0/Authorize or /2.0/Token format.
- Fixed: When working with an F&O connection, the AX destination component's Update or Upsert action might report a resource not found error if any of the key values contain some special characters such as a slash character.
- Fixed: The test connection function in AX connection manager might not always use the latest configuration for the test service calls, which could result in incorrect reporting of issues.

Version 23.1.1 - May 19, 2023

This release is mainly a service release, which comes with the following updates and fixes - Note that this will be our last version that supports SSIS 2008 (SQL Server 2008):

Updated: We have now made the Bypass Power Automate Flows option in the CRM/CDS destination component an official feature which is backed by the recently introduced SuppressCallbackRegistrationExpanderJob platform feature.
Fixed: When providing an input to the associatedentitytypecode.old field (introduced in v23.1) in the CRM/CDS destination component that works with documenttemplate entity, the template document may not be properly converted between the old type code and new type code for the template's associated entity in case they are different.
Fixed: When using a manually specified key for Update action in the CRM/CDS destination component, if one of the records in the batch does not have a match in the target system, the rest of the batch may fail with the same match not found error even though a match might actually exist.
Fixed: When using the Recurring Export function, the AX source component would return empty values for all columns, even though there are values in the system. This appears to be an issue that is occurring in some relatively new F&O instances due to changes made to the export files by Microsoft recently.

Version 23.1 - May 19, 2023

The following are the updates and enhancements made for each group of components:

General
- Update: The auto-update form now displays a warning message about required maintenance for software upgrade.
- Update: We have removed the dependency on Microsoft.NetEnterpriseServers.ExceptionMessageBox.dll assembly.
- Fixed: KingswaySoft License Manager might report an incorrect grace period when the license is running under the grace terms.
Dynamics 365 CE/CRM & CDS
- New: CDS/CRM source component now supports outputting MetadataId when reading from EntityMetadata/FieldMetadata.
- New: CDS/CRM destination component now supports outputting results returned by ExecuteWorkflowAction in the default output.
- New: We added support for migration of documenttemplate entity by introducing a new field called associatedentitytypecode.old which can take the associated entity's old type code in the source system so that we can rewrite the template content to be properly used in the new system.
- New: We added support for "not-contain-values" FetchXML conditions.
- New: We added some additional condition operators such as ContainValues, DoesNotContainValues, etc.
- Update: CDS/CRM source component now uses DT_DECIMAL data type for number fields, which should provide better accuracy. For existing components, a refresh of the component is required.
- Update: We have made the Authorization Server URL option in the CDS/CRM connection manager to be using a combo dropdown control, which should make it easy to select any of those known authorization servers for Dynamics 365 online services.
- Fixed: You may run into "Object reference not set to an instance of an object" error in CDS/CRM Connection Manager when working with the Certificate OAuth type. This was an issue that particularly happens to v22.1 only.
- Fixed: You may run into "Object reference not set to an instance of an object" error when reading OptionSetMetadata from CDS/CRM source component.
- Fixed: CDS/CRM source component may report "Invalid URI: The Uri scheme is too long" error when reading EntityChanges with an Input Token.
- Fixed: Reading from knowledgearticlescategories entity in CDS/CRM source component may raise "Resource not found" error when working with the Web API service endpoint.
- Fixed: CDS/CRM source component missed outputting 'Two Options' type fields in the OptionSetMetadata output.
- Fixed: When using the Upsert action to update an existing record to inactive state in a CDS/CRM destination component, the component might create a new record instead if the component's error handling is set to Redirect Error Rows while its batch size is set to 1.
- Fixed: You may run into "LogicalName is required when entity id is not specified" error in CDS/CRM destination component when performing Bulk Delete action through Web API connection.
Dynamics 365 BC/NAV
- New: We added support for the latest Business Central 2023 Release Wave 1 (v22).
- New: We added the "Authorization Server URL" option in NAV Connection Manager to support an alternative authorization server when necessary.
- New: We added "Use Integrated Authentication" support in NAV Connection Manager when working with NAV On-Premise instances.
- New: Generating OAuth token in NAV Connection Manager now supports specifying the OAuth scopes.
- Update: We have deprecated Basic authentication mode when working with Dynamics 365 Business Central Online.
- Update: Default Service Endpoint in NAV connection manager has now been changed to REST, which is the preferred authentication option.
- Fixed: NAV source component may output NULL on _ParnetLinkNo field when working with OData connection.
- Fixed: You may get "'POST' requests are not allowed" error in NAV destination component when performing Upsert action to create a record with a Batch Size of 1 and the key field value is provided while working with OData connection.
- Fixed: Upsert to update with a key field value contains "/" may not find the match in NAV destination component when working with REST/OData connections.
Dynamics 365 FO/AX
- Enhancement: Enhanced batch writing in AX destination component when working with a Dynamics F&O connection. In the new version, we implemented a new solo batch request pattern to facilitate a more granularly controlled batch writing, so that one failed row will not fail the entire batch when the component's error handling option is configured as Redirect error rows while there is an error with one of the rows in the batch.
- Some other general updates.

Version 22.1 - October 19, 2022

The following are the updates and enhancements made for each group of components:

General
- New: We have added support for SQL Server 2022 (SSIS 2022).
- Enhancement: We have updated the license manager program to make it more resilient in obtaining new license files or renewals should there be intermittent networking issues. The enhancement mainly applies to unattended license requests or updates using command line via Windows script, it is particularly helpful when you run our software on Azure SSIS IR as it involves license activation requests each time when the instance is started or restarted.
- Update: The entire program has received some major branding updates in various UI elements.
Dynamics 365 CE/CRM & CDS
- New: We added User Multiplexing support in CRM/CDS Connection Manager, which can help improve data load performance if used properly.
- New: The CRM/CDS source component has a new source type called Metadata which can be used to extract metadata (EntityMetadata, FieldMetadata, LookupMetadata, and OptionSetMetadata) from the system.
- New: The CRM/CDS source component now support multi-threaded reading when working with Audit Logs source type.
- New: We have added Authorization Code OAuth type to the CDS/CRM connection manager.
- New: CRM/CDS Source component now lists N:N Relationship entities in Source Entity drop-down for Entity Changes source type
- New: CRM/CDS Destination component now supports outputting SavedRecordId and IsNew for Alternate Key Upsert action when working with a Web API connection.
- New: We added support of using optionset fields as a text lookup target field in CRM/CDS Destination component.
- Enhancement: Better string length detection for optionset label fields in CRM/CDS component when working with Web API service endpoint.
- Fixed: CRM/CDS Destination component may report "Object reference not set to an instance of an object" error when performing Update with manually specified key(s) and no match can be found.
- Fixed: You may run into error "Invalid lookup setting" in CRM/CDS Destination component when using optionset field as the target field of Alternate Key lookup method in Text Lookup.
- Fixed: CRM/CDS Destination may report "Unexpected empty matching key values" when configuring the primary key as the manually specified key in Upsert action while the input value for the primary key field is NULL.
- Fixed: You may receive the "Record does not exist" error when using Alternate Key in Text Lookup in CRM/CDM Destination component if the input value contains special characters like & or # through a Web API connection
- Fixed: 'Ignore Unchanged Fields' option may not work properly when a lookup type field is used as manually specified matching key in CDS/CRM destination component when performing Update/Upsert action through a WebAPI connection.
- Fixed: The "{filefieldname}_binarycontent" field is not available in CRM/CDS component's metadata when working with Web API.
- Fixed: CRM/CDS Destination component may fail with a "Specified cast is not valid" error when incidenresolution.owner fields are specified while updating incident entity through a Web API connection.
- Fixed: You may run into "Object reference not set to an instance of an object" error in CRM/CDS Destination component when performing Merge action with a Batch Size of 1 that uses a Web API connection.
- Fixed: When working with the Entity Changes source type in CRM/CDS source component via a WebAPI connection, it is possible that you might receive an "Invalid URI: The Uri scheme is too long." error.
- Fixed: CRM/CDS Source component may not output the records properly when working with "begins-with" FetchXML operator when working with Web API connection.
- Fixed: You may receive a "Year, Month, and Day parameters describe an un-representable DateTime" error from Premium Service Lookup component when working with CDS/CRM connection which includes a date/datetime output field while the source is an OLE DB Source component.
Dynamics 365 BC/NAV
- New: We now support the REST service endpoint in the NAV connection manager. This is the recommended API interface going forward.
- New: We added support for the new Business Central 2022 Release Wave 1 (v20) and 2022 Release Wave 2 (v21).
- New: Batch writing in NAV Destination component now supports changeset when working with the OData connection.
- Enhancement: Improved retry implementation on HTTP 500 and 503 errors.
- Update: Client Secret is now an optional property when generating NAV OAuth token in NAV Connection Manager.
- Update: Default batch size is lowered to 50 in NAV Destination component when working with OData connection.
- Fixed: NAV Destination component may not find the matched record(s) properly when using enumeration type field as the manually specified key field in Update/Upsert/Delete action through a SOAP web service connection.
- Fixed: Create action may not send input values for the entity key fields in the service requests when working with OData service endpoint in NAV Destination component.
- Fixed: You may run into "Evaluation failed for field Transit-from Date/Time" error in NAV Destination component when working with a datetime field through a SOAP web service connection.
- Fixed: NAV Destination component may report a "no boundary information was found" error when performing batch operations through OData connection for some particular instances
- Fixed: Redirect Error Rows may not work properly in NAV Destination component when using a Batch Size of 1 through the OData connection.
Dynamics 365 FO/AX
- Enhancement: Improved retry implementation on HTTP 500 and 503 errors.
- Update: Dynamics AX Next Sequence Number component now shows a warning to indicate the component only works for Business Connector connection.
- Fixed: You may run into a 404 Not Found error when authenticating against an ADFS server in AX Connection Manager for some special Authentication Server URLs.

Version 21.2 - November 11, 2021

The following are the updates and enhancements made for each group of components:

General
- New: We added a new action button in the KingswaySoft License Manager which makes it easy to request a free trial.
- New: We added limited password attempts feature to Connection Managers that use OAuth token file. When the limit is reached, access_token and refresh_token values will be deleted from the token file, this is to protect the file from unauthorized use.
Dynamics 365 CE/CRM & CDS
- New: We added support for multi-threaded reading in the CDS/CRM source component when reading from AuditLogs source type.
- New: CDS/CRM destination component now supports a new "Bypass Custom Business Logic" option which will leverage the BypassCustomPluginExecution system feature when enabled.
- New: We added a Timezone Conversion Engine option in CDS/CRM Connection Manager, which can be used to overwrite the default timezone conversion strategy when required.
- New: The Delete action for audit entity now supports two new fields which are targetid and targetidtype when working with a WebAPI connection. Those two fields can be used to delete all record change history for a particular record using the DeleteRecordChangeHistory service call.
- Enhancement: CDS/CRM destination component now leverages "BypassCustomPluginExecution" feature when both Tentatively Disable Relevant Plugins and Tentatively Disable Relevant Workflows options are enabled.
- Enhancement: We have some performance enhancement when writing to workflow entity with statecode/statuscode field mapped in the CDS/CRM destination component.
- Enhancement: Our version detection service call is now using the v9.0 service endpoint when working with Dynamics 365 online using a WebAPI connection.
- Fixed: You may get error "State code is invalid or state code is valid but status code is invalid for a specified state code" in destination component when using "Tentatively Disable Relevant Plugins" option through a SOAP web service connection.
- Fixed: CDS/CRM destination component was not outputting "NoChangesRequired" value properly when using a batch size of 1.
- Fixed: CDS/CRM destination component may default output column SaveRecordId value as NULL when using System Duplicate Detection record matching criteria with a batch size of 1 while performing Update action.
- Fixed: Upsert using System Duplicate Detection record matching criteria in CDS/CRM destination component through a WebAPI connection may not update existing records properly.
- Fixed: Redirect error handling in CDS/CRM destination component may not work properly when working with Merge action while input CoalesceNonEmptyValues value is set to true.
- Fixed: 'Ignore Unchanged Fields' option may not work properly when a customer type field is mapped in CDS/CRM destination component when performing Update/Upsert action.
- Fixed: Using Partial Cache in Premium Service Lookup component when working with CDS/CRM connection may not produce right output values for output lookup type fields. For example, you may receive a NULL output value for owneridtype field from the Premium Service Lookup component when the field has been selected as an output column.
- Fixed: You may not be able to add an OR filter operator in the Premium Service Lookup component's query designer when using the Partial Cache or No Cache option.
Dynamics 365 BC/NAV
- New: We now support the OData service endpoint in the NAV connection manager which provide some advanced integration features that were not possible using the SOAP service endpoint.
- New: We added support for the new Business Central 2021 Release Wave 2 (v19).
- New: We have added a new Premium Service Lookup component which can be used to lookup records when working with Business Central or Dynamics NAV connections.
- Enhancement: NAV connection manager now defaults the connection to Dynamics 365 Business Central online using the OAuth authentication type.
- Enhancement: NAV destination component has a much more robust data type handling when writing data using the NAV destination component.
- Update: NAV source component now outputs datetime value in SSIS datetimeoffset data type, this provides a more accurate output value. A refresh of the component using the "Refresh Component" button is required in order to take advantage of this feature for existing component.
Dynamics 365 FO/AX
- New: We added a new OrderBy option in the AX source component which can be used to sort the data retrieved from Dynamics 365 Finance and Operations.
- Update: The ActiveDirectoryResource property in AX connection manager has been renamed as ServiceResource. This is implemented to make it consistent with industry terminology, which should be considered as a breaking change, since older versions would not be able to recognize the new parameter name. All jobs that have the ActiveDirectoryResource property parameterized should be re-configured using the new ServiceResource property, as the old property has been removed from job configuration once upgraded.
- Enhancement: AX destination component has a much more robust data type handling when writing data to a F&O connection in the AX destination component.
- Fixed: AX component may not make proper retry service calls on 429 response error when working with a Dynamics F&O connection.

Version 21.1 - June 16, 2021

The following are the updates and enhancements made for each group of components:

General
- New: We now ship a new console version of KingswaySoft License Manager program which is designed to work more reliably in a container environment.
- New: KingswaySoft License Manager program now always uses a secure service endpoint for activation and deactivation requests.
- Enhancement: We lowered .NET framework requirement to v4.5.2 when working with SSIS 2012 or above.
- Enhancement: We added support for TLS 1.3.
Dynamics 365 CE/CRM & CDS
- New: We have added a new Premium Service Lookup component which can be used to lookup records through CRM/CDS connections.
- New: We have added a new OAuth type to the CDS/CRM connection manager called Interactive Login which allows to login to the system through interactive login in order to establish the connection, this can save the effort of creating Azure Active Directory application registrations.
- Enhancement: The "Tentatively Disable Relevant Workflows" option in the destination component now also disables Power Automate flows if there are any.
- Enhancement: Some addition fixes of the "undeclared property" error in the CDS/CRM destination component for some very unique lookup fields when working with WebAPI service endpoint.
- Fixed: You might experience an InvalidCast error ("Specified cast is not valid") when writing to incidentresolution_createdon field in the CRM/CDS Destination component using WebAPI.
- Fixed: You might receive an error indicating "Failed to process 'entityimage' field with an input value of '' (value type: null, field type: Image, entity: contact)" when the input value for an entity image field is empty when working with the SOAP 2011 service endpoint.
- Fixed: In some very rare situations, the CDS/CRM destination component may not actually perform the write operation when statecode/statuscode field(s) are mapped when using the WebAPI service endpoint.
- Fixed: When using the Alternate Key Upsert in the CDS/CRM destination component, the result reported back by the destination component may not be correct except the first row in the batch when WebAPI is used.
- Fixed: When working with the Entity Changes source type in the CRM/CDS source component using a WebAPI connection, you may receive an error indicating "The navigation properties are not supported with $select clause".
- Fixed: OAuth password authentication might not work with certain CDS/CRM environments when ADFS server is involved in the authentication process.
- Fixed: When using the Write First Record Only as the Source Duplicate Optimization option in the CDS/CRM destination component, the Batch Size option may only work for the initial batch, not subsequent ones.
- Fixed: When using a batch size of 1 in the CDS/CRM destination component, the multi-threaded writing may only work for the first batch, not subsequent batches.
- Fixed: You might received an "Inavlid URI error" when working with some IFD enabled Dynamics CRM 4.0 environments.
- Fixed: When using a FetchXML query that might contain multiple filter elements (instead of multiple conditions under one filter element) in the CDS/CRM source component, the component might drop all other filters except the first one during runtime.
- Fixed: The CDS/CRM source component might report an error - KingswaySoft.IntegrationToolkit.DynamicsCrm.CrmServiceException: CRM service call returned an error: 'TimeZoneRule' entity doesn't contain attribute with Name = 'systemuserid'.
- Fixed: When working with accessteammember entity in the CDS/CRM destination component using the WebAPI service endpoint, you might received an error indicating "KingswaySoft.IntegrationToolkit.DynamicsCrm.CrmServiceException: CRM service call returned an error: An error has occurred when retrieving CDS/CRM entity metadata: The remote server returned an error: (404) Not Found. ".
- Fixed: When using the Primary Key as the matching criteria for the Upsert action in a CDS/CRM destination component that uses WebAPI as the service endpoint, the reported batch results might be incorrect for some of the rows in the middle of batch.
- Fixed: The CDS/CRM source component only lists the primary key field from a linked entity when <all-attributes /> is used for the linked entity, while it should list all available field for the linked entity.
- Fixed: When the "Remove Unresolvable References" option is enabled in CDS/CRM destination component, and a GUID input value is mapped to a lookup field, the component might send an invalid FetchXML query which includes an empty attribute name.
- Fixed: In a very special situation where the connection user has an uilanguageid of 0 in the target system, writing to the product entity with a multilingual name provided, the CDS/CRM destination component would SetLocale calls using uilanguageid of 0 which might error out.
- Fixed: The CDS/CRM destination component might fail when writing to a N:N relationship entity which has an empty entity set name when WebAPI service endpoint is used.
Dynamics 365 BC/NAV
- New: We added support for some recent Business Central releases including Business Central 2021 Release Wave 1 (v18), Business Central 2020 Release Wave 2 (v17), and Business Central 2020 Release Wave 1 (v16).
Dynamics 365 FO/AX
- New: AX Destination Component now supports batch writing using a newly introduced Batch Size setting available in the destination component when working with F&O OData service endpoint.
- New: We added the ability to quickly toggle string and numeric fields to various lengths or sizes in AX Source component so it can accommodate more data when needed, when working with F&O OData service endpoint.
- Enhancement: F&O service calls now gracefully handle 429 error returned by the service by following the instruction given in the service response.
- Fixed: Update or Upsert action might fail with 404 errors when the records actually exist in the target system which contains some very special characters when using the AX destination component to work with a Dynamics F&O connection.

Version 20.2 - November 4, 2020

The following are the updates and enhancements made for each group of components:

General
- New: KingswaySoft License Manager now includes the ability to show and copy the LicenseId within the program which can be used for renewal purposes without having to reveal the full license key details, for instance, if a third-party reseller or agent is involved.
- New: KingswaySoft License Manager program now offers a link in the UI to help renew license maintenance or subscription with one single click.
Dynamics 365 CE/CRM & CDS
- Update: CRM/CDS Destination component comes with some massive SSIS metadata changes, including the renaming of some SSIS component properties and output columns. For instance, CrmRecordId output column in the CRM/CDS destination component has been renamed to SavedRecordId, and CrmErrorMessage has been renamed to ErrorMessage, and so so. Such changes should be considered as breaking changes, since any packages saved with the new version will not work with older versions. It is important to make a full backup of your SSIS packages before opening with the new version in Visual Studio.
- Update: The CrmServerUrl property in CRM/CDS connection manager has been renamed as ServerUrl. This should be considered as a breaking change, since older versions would not be able to recognize the new parameter name. All jobs that have CrmServerUrl property parameterized should be re-configured using the new ServerUrl property, as the old property has been removed from job configuration once upgraded.
- Update: We have a completely new implementation for datetime conversions in this release, which should eliminate the situation that the conversion might create discrepancies for some special datetime values because of the conversion from user timezone to UTC or the other way around. The new implementation should have a 100% accuracy in converting datetime values between timezones by fully respecting system behaviors. In particular, all datetime values returned in CRM/CDS source component should be exactly the same from CRM/CDS UI - there used to be some discrepancies for some special datetime values in some unique timezones.
- New: CRM/CDS Destination component now provides three new Process Optimization options, which can be used to tentatively disable CRM/CDS plugins, workflows and auditing during the writing process.
- New: Delete listmember action support in the CRM/CDS Destination component when using WebAPI.
- New: "Enable System Duplicate Detection" option is now available for Convert action in the CRM/CDS Destination component.
- New: CRM/CDS Destination component now supports writing to the name field of product entity properly when working in a multilingual environment while the connection user is using a different UI language from the base installation language.
- New: CRM/CDS Destination component now send output records in the exactly same order as they were received from upstream components when multi-threaded writing is enabled.
- New: CRM OptionSet Mapping component now supports working with the CDS Connection Manager as well.
- New: CRM/CDS Source component now provides a discretionary update experience in which you can choose how refresh should be performed in case any column-level property changes made manually should be retained.
- Enhancement: Some significant performance improvements when performing Create action for listmember entity in the CRM/CDS Destination component.
- Fixed: "Specified cast is not valid" error in the CRM/CDS Destination component when writing to the listmember entity using WebAPI.
- Fixed: "Skip Record if Lookup Failed" Text Lookup option may not function properly when working with the listmember entity.
- Fixed: "System.ArgumentNullException: Value cannot be null. Parameter name: value" error in the CRM/CDS Source component (through a WebAPI connection) when reading from activity entities and one of the actityparty's primary field is null.
- Fixed: CRM OptionSet Mapping component may add an extra space character in the output values when working with multiselect field.
Dynamics 365 BC/NAV
- New: NAV Source component now provides a discretionary update experience in which you can choose how refresh should be performed in case any column-level property changes made manually should be retained.
- Fixed: Batch Size may revert back to 200 if it is set to 1 after opening the NAV Destination component twice.
Dynamics 365 FO/AX
- New: AX Source component now provides a discretionary update experience in which you can choose how refresh should be performed in case any column-level property changes made manually should be retained.
- Enhancement: Dynamics AX destination component now saves a new OdataProperties custom property for the component itself and all F&O fields (external metadata columns), this will eliminate the needs of downloading the entire metadata document upon start which can take a significant amount of time, therefore it should emit a better performance during runtime. For existing component, a refresh of the component is required in order to take advantage of this enhancement.
- Fixed: 404 Not Found error when performing Update or Upsert action when working with a Dynamics 365 F&O environment where one of the key fields contains an ampersand "&" or number sign "#" character.

Version 20.1.1 - August 27, 2020

This is a service release of our 2020 wave 1 (v20.1) release, which includes the following bug fixes.

Dynamics 365 CE/CRM & CDS
- Fixed: When Upsert action is used with manually specified key(s) in CDS/CRM destination component, the component might report an incorrect IsNew value in its default output for those updated records - this is a regression bug that happens to the v20.1 release exclusively.
Dynamics 365 BC/NAV
- Fixed: When a batch size is used, NAV destination component might only send one row at a time after the initial batch.
- Fixed: In some rare cases, NAV destination component might send redundant error rows to its error output when the input value is not valid while the entire batch has the same or similar pre-processing errors.
- Fixed: NAV destination component might send empty rows to its outputs in some rare cases.