Looking at the removal changelog, the old personalisation engine will be replaced with Saved Views at some point in October this year.
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/get-started/removed-deprecated-features-platform-updates#personalization-without-saved-views
We tried Saved Views a few months back but it wouldn't work for our use case. We use personalisations to show customised forms (e.g. a custom field / powerapp on forms) to all users. The personalisations would be applied when their account is created and then it would appear as their view when they log in. However, this does not seem to be possible with Saved Views from what I can see.
Custom views can be applied company wide, but it would require each user to select the new view and make it their default on initial login. While this might be feasible for 3/4 users for 2/3 forms - we have around 20 HR/sysadmin users, ~400 ESS users and at least 20 individual personalisations with more to come. This is a fustrating experience for all end-users and might end up with crucial business-specific data missed if users don't end up performing this task.
Is there any way to set a view for a form as default for all users, with 0 effort from them?
In addition, if memory serves me right - ESS isn't supported like other forms are and will only have one view, similar to how personalisations work currently. However, all the old personalisation sysadmin pages get replaced with Saved Views. Is there any way to force an ESS personalisation on users while the Saved Views feature is active?
Edit: upon further testing, it looks like the feature has been updated with the ability to add defaults for users. However, the problem with self service still looks to be an issue.
