-
Telephone Number Formats per Country/Region (similar to the VAT Registration No. Formats)
Our customers keep expressing the wish that when entering telephone numbers, an automatic check should be carried out to determine whether a number is correct and corresponds to the country-specific format. It should be possible to setup several telephone number formats per country/region, as has already been done with the VAT numbers. If a telephone number is then entered (e.g. on a contact), it should be checked whether it is a valid number. It should be prevented that invalid numbers can be inserted. In this way, all telephone numbers in the "address base" would appear uniform and incorrect entries would be reduced. We should probably orientate on the E.164 standard, which defines a general format for international telephone numbers. -
Changing the visibility and position of FastTabs on card pages
In the legacy windows client (of NAV and BC14), it was possible to hide and move FastTabs on card pages. Unfortunately, the modern client of Business Central no longer offers this functionality. To help users work efficiently, this option should also be made available in the modern client (both in user-personalization and in profile-customization). -
Define invoice rounding per vendor
Currently, it is only possible to define in general in the "Purchases & Payables Setup" whether an invoice rounding should be performed or not.
Suppliers are very different regarding invoice rounding, i.e. some vendors round their invoices and others do not. For this reason, it should be possible to specify per vendor whether invoice rounding should be performed or not.
It would be best to implement this in a similar way as for the items with regard to the "Prevent Negative Inventory" field. With the option "Default" the setting according to "Inventory Setup" applies and with the option Yes or No the setting according to the respective item applies.
Especially in Switzerland, many BC customers struggle with this problem, as about 70% of the vendors round their invoices to 0.05 and the rest do not. This means a lot of manual and complicated handwork so that the purchase invoices can be created and posted correctly.
-
Access Connector for Dataverse and Power Platform should support virtual tables
With the "Access Connector for Dataverse and Power Platform", data can be exchanged between Microsoft Access (on-premises) and Dataverse (cloud), which is very helpful. Unfortunately, the connector does not support virtual tables of Dataverse, which is a major limitation.
Exchanging data between Dataverse virtual tables (cloud) and Microsoft Access (on-premises) and Microsoft Excel (on-premises) should also be implemented.