-
Two digit date patern range 01/01/1930 through 12/31/2029 outdated
The current situation is: If the date you want to enter is in the range 01/01/1930 through 12/31/2029, you can enter the year with two digits; otherwise, enter the year with four digits. If the user types 29 it is interpreted like 2029 but if he types 30 it is interpreted like 1930 that is confusing for the users. We like this behavior to be changed so that the range is taken from windows setting or that it can be configured some ware else. -
We would like to personalize the ribbon by adding own tab and own groups
We would like to personalize the ribbon by adding own tab and own groups. As was possible in the windows client. -
Export table to Excel
From Business Central 15 versions and above, the development environment has been deprecated, and the options to open, export Tables Directly from the dev. Environment for an example from Business Central 14 to Excel are no longer part of the Lates version of business Central 15;16; 17; versions on-premise and online. However, it is still possible to open a table by means of table = ..... in the url. The table will then be opened in a screen. However, there is no option to export the data to Excel. Our customers need this to supply data for an Accountant's audit. furthermore it was possible in version befoor BC15 to adjust data in that screen. As support consultants, we sometimes need that option. We now seem to have no options to make a quick correction -
possibility to personalize subforms
For example the Sales Order cart page 42 has a subform ->Lines (Sales Order Subform 46, ListPart) That Subform has actions and there we would like to be able to hide actions and/or change the order. -
filter criteria must be remembered on all pages. example Sent Emails (8883, List) it doesn't work there
On the page Sent Emails (8883, List) the filter is not remembered and saved. Normally you can save your own filter, however on the page the filter is saved but the filter criteria is not. This page "Sent emails" is a bit different, the page is temporary, which then leads to the page building up content in code, which then interfers with how the filters are working.
-
Record has been removed from the filter
it would be nice if there is a notification if a record no longer falls within the filter critera. Like "Record has been removed from the filter." Now the record disappears and you are suddenly working in another record
-
Work Date unexpected behavior
As described in the documentation, the Work Date is set to the current date for each session.
Change basic settings for the current user - Business Central | Microsoft Learn
Unfortunately, the Work Date field in My Settings does not reflect that. When switching companies, there is the old used Work Date. Even worse if you do change it, it will still be changed to the current date after the company switch!
-
It should be possible to link/synchronize a new Azure Active Directory (AAD) user account with an existing Business Central (BC) user account.
The customer's story is as follows:
There is an employee who resigned. That employee was marked as inactive in BC and removed from Azure AD. After a few months, the employee was rehired. As a result, the employee was recreated in Azure AD and synchronized in Business Central. The issue is that the employee can no longer be linked to their existing account; instead, a new account is automatically created with a sequential number appended. So, what was userx becomes userx 1. Our customer does not want this; they want the user to be able to regain their old (userx) account.
-
Feature modification for Business Central using Power Automate flows to allow the activation of the flows to be run within BC for users that have been applied Run only users to them instead of granting full ownership
For situations where we have a Power Automate Flows to Business Central where flows are created from an owner of the flow and shared with other BC users that have the respective access to grant them the ability to run the flow within BC when they have only Run only users and not Co ownership of the flow as that opens up the flow to unwanted modification from the shared ownership users as it currently stands.
As the shared ownership users may change the flow completely from what it was initially intended as the goal is to use the Run only functionally to limit the access to the flow itself yet allow the users to run it within BC as well.
You’re offline. This is a read only version of the page.
