Profile configuration can't be started in Business Central
This article provides a resolution for the "personalization could not be started" error that occurs during profile configuration in Dynamics 365 Business Central.
Symptoms
When there are issues preventing the profile configuration in Business Central, the user receives the following error message, and can't start the profile configuration. When the configuration is started, all customization records are loaded and compiled together. If one of these records causes a compilation error, then the profile configuration can't be started.
Sorry, something went wrong and personalization could not be started. Please try again later, or contact your system administrator.
Resolution
Note
To solve this issue, you need tenant administrator permissions in Business Central.
As a tenant administrator, you can perform the following steps to remove the profile configurations with errors or alternatively, export the profile and fix the code issues.
Important
The step described in the Remove profile configuration records section will delete records with compilation errors and the specific profile configuration will be deleted. It's recommended to take a screenshot of any configurations done, before deleting them.
Identify profile configuration
- In Business Central, in the Tell Me box, enter Profiles, and then choose the related link.
- Select the profile card of the profile that can't be customized, and then choose Manage customized pages.
- Select the Troubleshoot button.
You now get the list of all records that contain errors. To proceed, remove profile configuration records or export (force) of profile configuration (from version 16.2).
Remove profile configuration records
To remove the identified records, select the Manage action to delete the profile configurations with errors.
Export (force) of profile configuration (from version 16.2)
Starting with Business Central version 16.2, you can try to mitigate the issue by exporting the profile, fixing the issue, and then reimporting the profile.
In Business Central, in the Tell Me box, enter Profiles, and then select the related link.
Select the Export Profiles button.
A message will display to tell you that there are errors. Select Yes when you're prompted to export the profiles with errors. This will download the AL code related to all profiles on the tenant.
Unzip the profile package that you downloaded, and open the AL file for the page customization that contains the issue.
The page customization name follows this pattern:
PageCustomization.<target-page-name>.Configuration<id>.al
.Based on the diagnostics from the troubleshooting page, or by moving the page customization AL code into an AL app to benefit from the compiler diagnostics, locate the code block that causes the issue and remove it.
Create a new .zip file with the fixed page customization.
Return to the Profile List page and select the Import Profiles button.
Follow the wizard's instruction and, when prompted, select the profile that was fixed in the list of profiles to import.
Return to the list of customized pages for this profile and verify that no errors are reported.
More information
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for