From the Microsoft Dynamics 365 Business Central blogs: Transfer environments; Error handling; Common permission errors; User groups removal

In this week’s Dynamics 365 Business Central blog roundup:

• Transfer environments between Microsoft Entra tenants
• How to improve error handling with actionable errors in Business Central
• How to fix common permission errors in Business Central
• Prepare for the removal of user groups

Transfer environments between Microsoft Entra tenants

Writing on his blog, Stefano Demiliani noted that you can now transfer a Microsoft Dynamics 365 Business Central SaaS tenant to a different tenant without opening a support request with Microsoft.

Demiliani pointed out that now you'll find a new environment transfer action in the admin Center:

After clicking on this action, you can select the environment(s) to be transferred, specify the Entra tenant ID of the destination tenant, choose a date and time at which the chosen environment(s) should transfer to the destination, and then confirm the transfer operation.

Demiliani explained who has to initiate the environment transfer before it can proceed. He stated that the environment transfer must be accepted in the destination Entra tenant within eight hours after the transfer is created on the source tenant.

Demiliani wrote that transfer requests are valid for two weeks if they're accepted on the destination tenant within eight hours. He added that it isn’t possible to choose a date and time on the source tenant that is more than two weeks in the future. Demiliani than explained the actions to perform in the destination tenant.

How to improve error handling with actionable errors in Business Central

On his blog, Alberto Soben wrote that good error handling is the best way to ensure users can get through the different errors that may appear while they're working with D365BC.

In his blog post, he explained that actionable errors make it easy for users to handle errors in D365BC. Soben wrote that there are two types of actionable errors: inline validation errors and dialogue errors.

He then pointed out how to use inline actionable errors, which are used when a field validation happens and an error is raised. He also explained how to create an inactionable error. Soben offered details on how to use dialogue actionable errors. He stated that these message errors are very similar to inline validation errors, except they don’t occur when users are validating fields.

How to fix common permission errors in Business Central