Announcements
No record found.
Does upgrade process preserve user Personalization like filters, query , form control change etc.?
*This post is locked for comments
Hi Iamv,
All this changes are stored in SysLastValue table that would be updated as well. Usually there is no issue with it.
Depends on what is packed in the usage data container. In some cases it works, in some cases it breaks the application.
I am just about to go live with R3 and to be sure we are truncating the syslastvalue table as part of the cutover steps, since during user testing we have noticed that it did break some forms, reports and batch jobs due to changes on the underlying metadata or class structure (i.e. what variables are packed in a class). Validating what is impacted one-by-one would be way too much effort.
As Vilmos mentioned, sometimes you can have issue caused by SysLastValue, however, it's not the best solution to wipe this data for all users because of couple broken forms. I have not see any recommendations to delete SysLastValue during upgrade process, on the contrary, I have seen statements that all data should be upgrade correctly.
So if you need personalization you will have to update it and fix issues if any.
The problem is if you use for example saveLast on a form, it is possible that class versioning was not implemented, which would store what variables are associated in which order with a version number that you would normally just increment, if the variable list changes (as part of the upgrade process). In that case sysLastValue in the old system was holding values straight in the container, instead of [classVersion, [packed variables]], and would break your form for sure.
fredshen.wordpress.com/.../use-packunpack-on-form
Unless you or Microsoft did implement packing the correct way:
community.dynamics.com/.../axapta-formlarda-pack-unpack
There are also a number of other scenarios in which it can break, like when a table table buffer or a set of records are packed, but the table structure has been changed. One example of this error we have faced was related to Electronic address getting redesigned behind the Global address book by Microsoft, where the packed table record was used on some forms/query ranges, and unpacking has failed. We also experienced this with the redesigned credit card tables. Same goes for a packed Query.
We have decided that the safest way is to drop the usage data, and recreate batch jobs. Users should re-add personalizations manually anyway, to make sure the changed standard form design is respected.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
We are thrilled to have these Champions in our Community!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
CP04-islander 24
Michel ROY 14
Jagadabi 6
