With the new version of the Business Central (2020 Wave 1) administrators have a way how to restrict users who could export data to Excel. This is common request across all industries to allow this functionality to only some users.
The permission is under the permission set “D365 Excel Export Action” and for system with own permission sets it could be done by specifying System Permission ID 6110.
Users who don’t have this permission are not able to export any data from any page (“Open in Excel” or “Edit in Excel”).
The specific action (Open or Edit) is dependent on whether the Excel Add-In in installed on the user’s computer. In the Cloud version, if user has Add-In he see both actions; however, in the On-Premise version only one of them is shown (based on whether the Add-In is installed or not). This can’t be unfortunately changed by any setup and we have to hope that it will change in the future.
All released or planned features from Microsoft Dynamics 365 Business Central 2020 Wave 1 could be found on Microsoft Docs.
Page inspection is a function that lets users get details about a page. The provided information is split into a few separated tabs:
Information about the page and the underlying table (name and object ID).
Table Fields tab shows information about data in the underlying table. If the table does not have an underlying table, no information in this tab is shown. Page fields calculated using variables (also table field from a different table than the underlying one) are not shown.
– User in this tab can find – ID and Name of the field – Data Type of the field – Value of the field – Other details (primary keys, extension names…)
List of all extensions that are subscribed to the page or corresponding table.
Page Filters show current filters that are applied to the page. All filters within all FilterGroups are shown (with information about in which FilterGroup they are applied)
The functionality of Page Inspection is very similar to About this Page in the original Microsoft Dynamics NAV Role Tailored Client.
One of the most known problem, especially in systems with many users, is managing DB locking for records, that require many updates. In term of Business Central (and previously NAV too) this problem is mostly known from No. Series.
The new version of the Business Central come with new setting in No. Series called “Non-Blocking No. Series” that could heavily improve the performance of core processes.
To set No. Series as a non-blocking, user has to select “Allow Gaps in Nos.” in the No. Series. This could be used without any problem for series that does not require to be sequential (I definitely to recommend this requirements with users who are responsible for auditing and legal requirements whether the series could have spaces in numbering or not). For example, in the Czech Republic it’s possible to use this setting for Customers, Vendors, and other entity related records, even for Orders, Quotes and any other documents that are not posted into G/L under this number.
All released or planned features from Microsoft Dynamics 365 Business Central 2019 Wave 2 could be found on Microsoft Docs.
Saved Setting in reports is one of the functionalities that are in the Business Central (and also in NAV) for a long time (since NAV 2015); However, many people do not know about this feature and what possibilities are offered.
Everyone knows that reports contain at the very beginning of the request page section called “Saved Settings” that allows the use of predefined filters or(as is more usually used as from my experience), only the automatically predefined filter created when the report was run for the last time.
This field has a lookup to the page “1560, Report Settings” based on a system table “2000000196, Object Options”. The page is also available using “Search for page/Tell Me” as “Report Settings”.
On this page, users (with the proper permissions) can modify, create, or delete saved settings for reports for all users. To create a new setting user can use the function to duplicate (action Copy) the existing one or create a blank configuration from scratch.
Saved Setting can be defined for a specific user (as is created automatically through report itself), or it can be shared with all users. To allow using of the saved setting for all users, an admin must set field “Share with all users” to Yes.
IMPORTANT: There is currently a bug in the system. If two saved settings for the same object that are used by one user have the same “Name”, the user won’t be able to select the one shared to all users. On the request page of the report, both configurations will be visible, but the one created only for the user will be used.