Version 2021 R2

Web Client Build Number: 10.2.0.54057

DataSync Build Number: 10.2.0.51787

November 08, 2021

Modifications importantes

• As of this release (2021 R2), SEI WebClient, DataSync and Web Central Point Configurator will no longer support Internet Explorer 11. Pour une expérience utilisateur optimale, nous recommandons vivement d'utiliser nos produits avec un navigateur compatible tel que Google Chrome ou Microsoft Edge.

• Users using SAML2 as Single Sign-On will now have to update their returnUrlattribute from https://yourserver:81 to https://yourserver:81/Account/SSO (for more info, see Azure Single Sign-On for Web Client).
  In addition, we have now changed the auto-sign in for SAML2, users will now see the WebClient login page when they will sign in.

 

Points forts

Configure OAuth 2.0 for SSO

We now have the possibility to also configure OAuth 2.0 providers within the Web Client to be able to use as Single Sign On. The user-friendly interface makes it easy for anyone to setup any provider of their choice.

To configure OAuth, see the documentation OAuth 2.0.

Optimize Caching in Excel AddIn

New caching optimizer that provides workbook analysis and statistics, and optimization recommendations for caching.

Increase Performance using Olap Column Store

Optimized load times for OLAP cubes (up to 3x faster) and less disk space usage for SQL warehouses (up to 10x lower).

UDM, Sales Forecast and Financial Budget Enhancement

New Universal Data Model module for financial budgets.

New Template

Sage 200 Evolution

Améliorations

Client web

• When activating the license, the EULA needs to be accepted. (7948)

• For Viewer license, Duplicator, Reporting Tree Node Selector and Reporting Tree Duplicator authorization has been added. (8197)

• For Single-Sign On, we now have the possibility to easily configure OAuth 2.0 providers within the Administration section in Web Client.(4033)
• Improve the overall general security by enhancing the user creation and reset password flows. With the changes done, we recommend that all of the Web Client users to reset their password.(3527)

• In Users, a new button is added to expire existing users which will enforce them to reset their password. (6220)

• In a worksheet, missing values can be forced to be displayed in a pivot. (8086)

• In Reporting Tree, characters length has been restricted for Reporting Tree Description, Node Description and Tab Name to avoid issues when using Reporting Tree in Excel Add-in. (8209)

• In Reporting Tree, a validation has been added to avoid duplicated Tab Name. (8670)

• In Reporting Tree, a Comment column has been added in the grid of Manage Nodes. (7327)

• The field for Reporting Tree Node values has been increased from 200 to 2000 characters. (8320)

Gestionnaire OLAP

• In the OLAP Manager, we improve the performance on Load All action. Additional to that, within the Environment & Data Sources, a new checkbox Columnstore Indexes has been added for OLAP Data Source to enable Column Store for SQL Server 2016 (and up) that will reduce the disk space used by Cubes and loading time for views.(7554)

• In OLAP Cube Details, a new checkbox No null in sources has been added that will improve the performance on Refresh action for Oracle Datawarehouse. (8748)

Excel Add-in (Complément)

• A new button Caching Optimizer has been added that will provide recommendations to optimize the cache. (4291)

• Duplicator, Reporting Tree Node Selector and Reporting Tree Duplicator authorization has been added for a Viewer license. (8197)

• An option to duplicate on children only has been added for Reporting Tree Duplicator. (8285)

DataSync

• Under Extraction Tables, Post Execution Script has been added to permit users to execute their own SQL script at the end of each Synchronization and Consolidation table. (8544)
• In DataSync Flat File connectors, the possibility of using External Source connection has been added. (DOC: 6508)
• In DataSync Flat File connectors, the possibility of customizing the Format Definition has been added. (DOC: 6508)

Modèles du Client Web

Modèle universel de données (UDM)

• Added a new Budget Module.

• View UDM_FINANCE_SUMMARIZED was changed to use a slice of Finance Staging to avoid the strain on the tempdb and faster performances.

• Cube UDM Finance, new Ledger Type logic, added a Data Source for OLAP Summarized if not changing the Fiscal Calendar and only using the currency conversion to have better performances when the Fiscal Calendar stays the same.

Sage 200 UK

• Cube UDM DimTime: changed table to view and removed related trackings and info pages.

• Changed Opening.

Sage 300

• For AR and AP Staging, changes were done to balance in the rare scenario when the Posting Date is before the Document Date in the ERP.

Sage 200 Evolution

• Sage 200 Evolution is now an available data source in UDM.

Sage 100 NA Template

• Added Info with a Stored Procedure to refresh all views. When using SELECT * in a view, if the administrator does customization or updates the ERP and some table structure changes, unfortunately, the meta data of those views are not updated automatically. Running this Info Page will fix this issue.

Modèle Sage 200 UK

• Added Info with a Stored Procedure to refresh all views. When using SELECT * in a view, if the administrator does customization or updates the ERP and some table structure changes, unfortunately, the meta data of those views are not updated automatically. Running this Info Page will fix this issue.

• Added Table Extraction of DS_OPENING_BALANCE for Opening Balances to make sure the tables NLNominalAccount, NLAccountYearValue, and NLAccountPeriodValue are in sync when calculating the opening balances

Modèle Sage 300

• For AR and AP Aging, changes were done to balance in the rare scenario when the Posting Date is before the Document Date in the ERP.

• Optional Field ETL now supports different collations between and within database.

• Optional Field ETL improvements:

  • Ability to drop table and re-create.

  • If table exists and there is no rows, resets the Previous Update Time in case a TRUNCATE TABLE was ran.

  • If one or more new optional Fields was mapped, a logic was added to take the lowest audit datetime of the rows containing those optional fields to do incremental load properly in case the sync Stored Procedure was ran before the Mapping Stored Procedure.

  • Added Special Logic for Consolidated Databases where the logs will record the max audit datetime of the table instead of the day the Stored Procedure was ran for tables where CPYID is detected. This way, even if the Sync Stored Procedure is ran before the incremental load in DataSync, the next Sync will be done properly.

Correctifs

Client web

• When renaming a view, a duplicate with same ID was sometimes created in the Command Center. (4454)

• Best Slice logic does not take Specific Join in account. (7122)

• Least Join logic does not take Specific Join in account. (8514)

• When the field is attached to the specific operators (<>, <, >), an issue occurred in the Best Slice detection. (8427)

• When deleting a Reporting Tree, nodes are not deleted in the database and some dependencies are still present within Report and Distribution. (7497)

• Since version 9.2, left and right positions were not available for Chart Legend. (7953)

• User with Administrator flag (no Data Model or environment authorization) cannot perform Data Entry on Multi-Tenant environment. (8220)

• Cannot copy Data Model when the user's username is exceeding 20 characters. (8325)

Distribution

• In a distribution job, sometimes users were not able to add a new view. (8833)

Excel Add-in (Complément)

• When using Reporting Tree and a value in filter, WHERE clause were added twice when generating the SQL query. (8112)

• The X button at the top-right corner does not completely close the Duplicator and Reporting Tree Duplicator windows. (8272)

• Potential InvalidCastException on Formulas can occur when Excel Addin for Sage is also enabled at the same time. (8126)

• Issue occurs in Formula caching when opening 2 files that contain the same Reference name. (7558)

DataSync

• In Sage Intacct connector, some operators (NOT IN, <>, !=) were not working when using filters within an Extraction. (7671)

• In HTTPS, trying to cancel an ongoing job had no effect (SQL Server, Sage Intacct, and etc.). (7827)

Modèles du Client Web

Modèle universel de données (UDM)

• Sage 200 UK, Sage 300, Sage Intacct, Sage X3, Sage Acumatica.

• Cube UDM Finance Staging. Total Budget wasn't configured properly, Period was meant to be hardcoded to 1.

Modèle Sage 200 UK

• Changed Opening Balance Logic in Nominal Ledger to match the ERP's.

• In DataSync, Collation Transformation removed from Extraction.

Modèle Sage 300

• In DataSync, Collation Transformation removed from Extraction.

Modèle Sage Intacct

• Changed GL Data Models to use GLDETAIL instead of GLENTRY to have access to the BOOKID.

• In DataSync, Collation Transformation removed from Extraction.

• In DataSync, Primary Key wasn't set properly for table Journal and Inventorytotaldetail.

Modèle Sage X3

• In DataSync, Collation Transformation removed from Extraction.

• In DataSync, Primary key wasn't set properly for tables: AGRPFCY, CMARKETING, PREQUISD, MFCWST, PRECEIPTD, PJMFINOVRRPT.

Modèle Acumatica

• In DataSync, Collation Transformation removed from Extraction.