With the release business central Wave 1 2022 lot of new features has been added to improve the user interaction with application.
This feature is small improvements in business central which allows to changes the name of customer on open sales document. This change of name will be applicable for that document only. This change of name is controlled by setup on sales & receivables setup.
Lets see how this setup works now on sales order
If this setup is not enabled on Sales & Receivable setup .Try to change name on sales order and it shows following message
This message states that if you trying to change the customer name then master not found the record then asking whether like to create new record or if you existing customer with new name then select that customer.
2. If this setup is enabled in Sales & Receivables setup. Try to change name on sales order.
So with new year major version of business central is about to release and in context of that Microsoft released preview version of business central 2022 Wave 1 (BC 20). This preview version only possible to create for Sandbox and non production environment.
How to get this preview environment to get the hands on the new release
On the cloud version of business central one can create Sandbox as below for preview version
This preview version available on docker also.
For Docket Artifacts user following PowerShell command.
Recently one of my customer asked me to add few more fields on primary key and I was looking at the customer like he asked something which is daunting task to be done with business central as everybody aware of that we can not change the primary key fields when table is already having data as while deploying the app it throws an error as below
Even I tried using Force sync also but it is still failing to deploy the app as this is breaking change for the app.
Now question is how to do this and overcome from such situation as your customer is behind you to do that.
To make it work we need to use ObsoleteState and ObsoleteReason that means we need to make your table obsolete and create a new table with new primary key and change the references in all those object where the object is referred.
To make the table obsolete mention the property as below.
Obsolete property value
Not obsolete. This is the normal/default setting.
Will become obsolete in a future version.
Has been made obsolete.
After making above table obsolete created new table with the new primary key.
Next point is how to transfer data in the new table .
To transfer data from obsolete table to new table used Installed code unit . Additionally you can use temporary table to update data from old table to new table.
If you would like to learn more about ObsoleteState Property then visit here.
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.