OnActuate is committed to ensuring our customers understand the products and services they are investing in. Check the OnActuate blog every quarter to learn about the important updates to the cloud and more.
User-based service protection API limits
User-based service protection API limits help protect system performance and availability from harm by individual users or integrations. The limits are designed to protect the service when client applications make extraordinary demands on server resources through integrations with Open Data Protocol (OData) or custom service APIs.
In this release, the feature is optional and is disabled by default. In version 10.0.30, the user-based API limits will be enabled by default but can optionally be disabled. The feature is targeted to become mandatory in version 10.0.33.
Update in November 2022
Platform Version: 10.0.30
Build Number: 10.0.1362
Link: November Update 2022
New grid control support for grouped card lists and multi-column card lists
Pages with these types of card lists are no longer automatically reverting to use the legacy grid control. In addition, any usages of the forceLegacyGrid() API—because of a grouped or multi-column card list—should be safe to remove.
Link: Grid Capabilities
SQL queries issued from non-interactive sessions will be assigned a timeout duration. The default value is 3 hours for an individual query. In scenarios when longer query execution is anticipated, use query Timeout API to override the default value
Update in January 2023
Platform Version: 10.0.31
Build Number: 10.0.1406
Link: January Update 2023
Allow Row version change tracking for tables and data entities
A new change tracking option has been added to finance and operations apps. This option enables Microsoft Dataverse to be used for incremental synchronization of data. Change tracking is a prerequisite for several features, such as Data archival, Synapse integration, Mobile offline, and Relevance search. The eventual goal is to unify all existing finance and operations data synchronization frameworks into one that is based on Dataverse synchronization services.
Before you create or update data entities so that you can use them with row version change tracking, verify that all tables that are used as data sources for those entities allow for row version change tracking.
A New Table metadata property
A new Table metadata property, DisableDatabaseLog, lets you prevent tables from being added to the database log. The default value is No. If the value is set to Yes, the table can’t be added when the database log is set up.
A New SecurityRole metadata property
A new SecurityRole metadata property, Can Be Deleted From UI, has been added to help protect system roles from being deleted by using finance and operations apps. The default value is Yes. If the value is set to No, a delete action will cause the following error message to be shown: “‘NN’ is a system role that can not be removed.”
Check out the latest features released for Microsoft Dynamics 365 Finance.
If you have any questions or concerns about the latest capabilities, or require assistance on your digital transformation, contact OnActuate!