Version 2.6


General changes and corrections

  • ERP focus: Data services with aggregates have generated an incorrect demand on MS-SQL.
  • ERP focus: Data services without standard sorting have generated an incorrect demand.
  • ERP focus: The incorrect display in the chrome browser has been corrected.
  • ERP focus: The errors in the sorting and grouping of data columns or columns with translation group have been corrected.
  • The SIS received an own user administration which will be used for the web focus. The administration will be made by the SIS administrator.
  • The SIS web focus is an independent ASP.NET website for the display of data services. The installation will be implemented by a web deploy package which can be taken of the set up resources.
  • When saving data schemes, deleted entities will not be removed.
  • The transformation "Regular impressions" has been corrected.
  • AdHoc transfers will be excluded by the process lock so that the prompt implementation will be improved.
  • When saving data images, a control for duplicates will take place.
  • Data images can directly be edited in the SIS administrator.
  • The determination of the amount of connections for the license verification has been optimised.
  • Ths SIS is available bilingually (de/en). The language selection can be made by the environment settings.
  • The transformation "CRM translation code" has been adapted in order to determine the language which needs to be used.
  • ERP focus: A demanding error could occur for the data saved in the CRM.
  • ERP focus: The display in the new window was incorrect.
  • When downloading the plugins by the SIS administrator, "temp" registers will be ignored.
  • ERP focus: The Key5 (team) will be controlled in order to display the right tab menu.
  • Debugging: Adhoc implementations will be repeated continuously. Individual implementations will also be repeated if the procedure is set to completely repeat.
  • The process limitation value of the change recognition will not be saved when cancelling.
  • SIS administrator: The sorting of the process list has been corrected.
  • SIS administrator: The allocation dialogue includes a search feature for panels.
  • The conflict handling "Transfer only source changes" has been added. Therefore, a copy of the last transfer will be saved in the data image. This can be deactivated in the server configuration on request. In case, a conflict is occuring, the current record will be compared with the copy and only actual changes will be transferred in the source. Therefore, the overwriting of "new data" in the looser record with "old data" from the winner can be avoided.
  • The standard SIS webservice includes a feature for the enqueuing of an adhoc transfer "/StartProcess/{ProcessId}/{SourceId}". The invoking will be made by POST and the basic authorisation of the SIS administrator access will be used for the authorisation. 


Sage CRM

  • The basic component (SisCrm) generates a serial letter view for the account entity.
  • The connection implements a constraint update for company and person as soon as a change has exclusively be made at phone or email in order to increase the update date.
  • The connection supports an additional address for company and person based on the address types. By multiple types, the first address ascending by the creation date will be selected.
  • The demanding error in the CRM will be compensated by a constraint parenthesis whereby also deleted records will be recorded.
  • The SIS 2.6.1 supports the CRM version 2018 R3.


Sage 100

  • The turnover bug regarding the last day in a period has been resolved for the version 6.2.
  • S100 8.0: The customer data can be overwritten for the proof transfer.
  • The kind of proof email allocation has been corrected.
  • S100 7.1, 8.0: The modules of the application server have been updated. The account number allocation has been corrected. The programme code has been optimised. Proof transfer: If the tax kind is not empty, the value will be transferred for the proof creation.
  • The error output of application server errors have been corrected.
  • Current account by ERP account: The company allocation can be overwritten by parameter if this has been changed by a duplicate adjustment in Sage 100. Further data will not be updated automatically. For this, a table script can be used.
  • Contact person by person: The company allocation can be overwritten by parameter if this has been changed by a duplicate adjustment in Sage 100. Address connections with company addresses of the old company will be deleted. Address connections of person addresses will be updated. The old person connection will be deleted and regenerated. The primary address will be overtaken by the new company if applicable about what the process parameter of the primary address decides. Further data will not be updated automatically. For this, a table script can be used.
  • Bank details by CRM bank details: The company and person allocation can be overwritten by parameter if this has been changed by a duplicate adjustment in Sage 100. Further data will not be updated automatically. For this, a table script can be used.