Version 2.3

Owned by Nadine Roeper
Last updated: Aug 31, 2018


General changes and corrections

  • SIS administrator: By regenerating a connection by double clicking and the generation of processes afterwards, the scheme information of the connection were not available whereby the panel list was empty.
  • SIS transformation: The transformation "Type formatting" has left the result empty in case of failed formattings for integers. Now the result will be filled by 0 if the formatting failed.
  • Validation errors occuring during saving of a connection will be recorded in the server logs.
  • The manual implementation of a process from the CRM has requested an ID what is only required for an adhoc implementation.
  • Not transformed values from subordinated data objects have not been emptied in the target if the source object is not available anymore. Example: Deletion of the email address in the CRM.
  • The date formatting in SQL demands has been adapted for the SIS data base, therefore, these are independent of country settings.
  • The client-server-communication between SIS server and SIS administrator has been optimised.
  • The messages processing has been optimised in the SIS administrator.
  • The process parameter "Asynchronic implementation" has been removed generally.
  • The transformations deliver details of errors inclusive originator data.
  • Potentially time-consuming tranformations (CRM translation code, demand data and C# script) give feedback for the implementation progress.
  • The SIS records in the data base have been slimed down in order to save memory capacity.
  • There is a new compliance regulation for an unsuccessful search. After processing the repetitions, this generation will be implemented.


Sage CRM

  • Bank details: The general CRM error regarding verification of rights for secondary entities has been compensated at the bank details for making the deletion possible.
  • Demands to the webserve which contain two followed dashs at various points, will be cancelled by the CRM. The CRM connection replaces these signs by a linkage.
  • ID columns, e. g. user selection, could not be emptied by explicit allocation.
  • The demand of all records by a process uses a sorting.


Sage 100 / Office Line

  • The process and data service implementation has been optimised.


Sage New Classic

  • The data demands for changes in the CRM have been adjusted by milliseconds. By the exchange integration, milliseconds could be included in "Updateddate" what could lead to a wrong change recognition.
  • Setting of the main contact person in the CRM updates the data images of the company in case these were synchronised to the CRM. This serves the conflict management.
  • The templates "Contact person by CRM person" have been adapted. By transformation, the changed area will if applicable remain and the area of the company will be used for the first generation.
  • The process and data service implementation has been optimised.
  • The template "Customer by CRM company" has been adapated. The area allocation has been removed.
  • The template "Supplier by CRM company" has been adapted. The area allocation has been removed.
  • The hierarchy verification for persons/contact person now also searches in the complementary direction for available data images.
  • The hierarchy verification for account now also searches in the complementary directions for available data images.
  • The data service template "Order items" has been corrected.
  • The verification of the turnover tax key can be deactivated in the connection.


Sage WinCarat

  • The access to WinCarat has been transformed from ODBC to native data base connections. Therefore, it is required to regenerate the WinCarat connection.
  • The process and data service implementation has been optimised.
  • The date demands for changes in the CRM have been adjusted by milliseconds. By the exchange integration, milliseconds could be included in "Updateddate" what could lead to a wrong change recognition.
  • Hierarchy verifications also consider complementary data images.


Sage 50

  • The process and data service implementation has been optimised.
  • The saving problem for the writing access to Sage 50 has been reduced. The complete resolving is planned with the next maintenance update for Sage 50.
  • The date demands for changes in the CRM have been adjusted by milliseconds. By the exchange integration, milliseconds could be included in "Updateddate" what could lead to a wrong change recognition.
  • Setting of the main contact person in the CRM updates the data images of the company in case these were synchronised to the CRM. This serves the conflict management.
  • Setting of the standard address in the CRM updates the data images of the company in case these were synchronised to the CRM. This serves the conflict management.
  • Further templates for data services are available.





Impressum