-
|
After an upgrade from NAV 2015 to BC14 to BC18, I found that the Personalization function causes an error with some pages but not others.
After removal of legacy flagged User Personalization and ensuring there were no Personalization errors in the troubleshooter (https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-troubleshooting-user-personalization), the error still persists. Removing all personalization from the database for both users and for profiles has also not resolved the issue. This error occurs in the upgraded database; however, if all of the same apps are loaded into a docker container with one of our demo databases, there is no error. I have reviewed a lot of posts or articles and nothing seems to fix it. Including this one ( https://www.sauravdhyani.com/2020/01/msdyn365bc-2019-wave-2-something-went.html) which was useful to explore even if the cause does not apply to our situation. Unfortunately there is also no error in the Event Viewer. This is an onprem environment that we are testing on our servers for a customer. Current user is SUPER. License is our partner developer license. Has anyone else run into this error after an upgrade or something else? If so, how did you resolve it? Got any suggestions on additional tables in SQL to review that maybe I've missed? Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The answer appears to be due to a step which was missed in the technical upgrade by inexperienced individuals. The technical upgrade steps document upgrading, and adding Control Addins for BC18. This was not completed. I suspect the primary issue is the Microsoft Social Listener addin was not created and the resource was not imported. The Personalization error occurred on pages which all have hidden Social Media factboxes or elements which utilize the control. Note that prior to updating the addins, the following tables were cleared of records. The records in these were from prior to the upgrade, and therefore should be removed to prevent conflicts or issues: they are obsolete once the database is upgraded from NAV 2015 to BC18. Page Data Personalization |
Beta Was this translation helpful? Give feedback.
The answer appears to be due to a step which was missed in the technical upgrade by inexperienced individuals. The technical upgrade steps document upgrading, and adding Control Addins for BC18. This was not completed.
I suspect the primary issue is the Microsoft Social Listener addin was not created and the resource was not imported. The Personalization error occurred on pages which all have hidden Social Media factboxes or elements which utilize the control.
Note that prior to updating the addins, the following tables were cleared of records. The records in these were from prior to the upgrade, and therefore should be removed to prevent conflicts or issues: they are obsolete once the da…