Today morning there was issue raised by my consultant stating that text on business central reports showing weird characters as below.
Though these reports was working well on On-Premise but after uploading to cloud it started showing those weird characters.
After checking report layout found that using the same fonts which is available on cloud version of business central but it still fails.
Why ? What could be the reason.
After checking found that customer created data in local language and to display those we need to have font which support those characters to show and I change the font on report and it showed correctly. (Surprisingly the font I used to show report data it worked properly and show data correctly and even it is not listed in the standard list .I think it depends on your country also)
On your own container you have leverage to install the font by using PowerShell command.
But for cloud please choose font wisely so it will not break your app.
Recently faced a problem of table locking which goes in not responding stage and finally user close the tab ,but when user opens the session again it actually messed up the critical data (It seems unimaginable force was roaming that time when this happens). Eventually after trying couple of days for data correction I need to contact Microsoft to restore the database.
When this happening my customer asked me if something like this happen then can we kill or cancel the session of user and then I came across this feature of Business Central admin center.
How to access admin center
This can be by adding tenant id with your business central URL as below
With the release of Business Central Wave 1 2020 new feature added to delete the extension data from production or sandbox. Prior to that we can uninstall the extension but data still there for the extension.
This feature will be useful when
1) Application is not in use.
2) Customer have desire to reinstall the extension data from scratch.
Let see how to uninstall and delete the extension data.
1) Launch the business central and search for extension management.
2) Select the required extension for uninstall. In this you can see new option added for delete extension data .
3) After selecting the option then you will get following warning message.
4) After click ‘YES’ then you can see ‘Delete Extension Data’ will get enable as follows
5) After that you can click on Uninstall then system will again warn before starting deleting data from extension.
6) If you are sure then click ‘YES’ and it will start processing to delete the data. This can not be undone.
By writing this I feel that clock is running faster and till the time we are utilizing the features of Wave 1 2020 more new features are planned and about to release in upcoming version Wave 2 2020.
There are plenty of features are planned for Wave 2 2020 but will list here what are the features I am looking for.
Database access intent changed to read-only for frequently used reports As business required faster access to the information so to speed up default database access change to Read-only.
Notify users of high-risk changes in selected setup fields :- This features means we can make list of fields from master table and get notified when someone changes.
Business Central in Microsoft Teams :-Integrate Microsoft team with Business Central.
Page Inspector supports temporary tables :- With this update, the inspection pane now displays valuable record information also for pages that are implemented to use temporary tables. Information about the current record is displayed in a consistent way and is not different from inspecting pages that use physical source tables.
Data audit system fields are added to every table :- Four New Field will be added in every tables to track the transactions log.
Attach to user session when debugging in sandbox :-Currently, when you debug with the Visual Studio Code AL debugger, you cannot attach to a user session, making it much harder to troubleshoot issues that are dependent on users and user permissions. This feature enables attaching to an active user session on the sandbox.
Debug extension installation and upgrade code :- It is currently not possible to debug extension install or upgrade code by just adding breakpoints and deploying a new application. Instead, some workaround is required to manually trigger the install and upgrade code, possibly commenting out upgrade tags and so on, making it tedious to properly test install and upgrade during development, as well as to troubleshoot issues.
For More information on Planned features please check this link