Manage personalized views

(3) Share

Report

Posted on by PT-01100339-0

364

Hi Experts,

I'm asking for the set up of personalized views.

For example, user A can personalize all form except for <released products form>.

With the <released products form>, admin will create many views for different users, in which user A can view and edit a <Purchasing view (include Purchasing tab)> of <released products form>. Admin will copy this view to user A.

When user A access the <released products form>, I want the default view to be <Purchasing view> instead of <Standard view> from the beginning, user A doesn't need to set the view as default by himself. Can admin do it by himself without telling user A that you must use <Purchasing view> instead?

There is a case, user A will change the view to standard, is there any setup to lock the <Purchasing view>, by that user A can use that view only?

Thank you so much!

Regards,

Categories:

Dynamics 365 Supply Chain Management

I have the same question (0)

All responses (5)

Answers (4)

Verified answer

Waed Ayyad 9,039 Super User 2025 Season 2 on at

Like (1)

Report

Hi,

You can prevent the personalization from the following path System administration > Setup > Personalization and you can prevent personalization on specific forms for specific user.

To share new view and set it as default, while creating the view set the pin as default view toggle button to true.

Thanks,

Waed Ayyad

If this helped, please mark it as "Verified" for others facing the same issue

Was this reply helpful? Yes No
Verified answer

Adis 6,069 Super User 2025 Season 2 on at

Like (1)

Report

Hi,

What we do in our organisation is the following. I want to stress out that this approach is based on either the users not having the know-how to override this setting or being disciplined enough to ask before doing something, rather than on real technical restriction. If you need real restriction then customization is necessary.

1.: Create and publish a new view that you set up as the default view.

2.: Check for personalized views that the users created and delete them.

The users cant use their customized view that is based on Microsofts "Standard view".

They have your published view now as default. In case they change something, the changes are based on your published view and not on Microsofts standard view.

If they have the knowledge, they could switch to the standard view first and then create a new view that is based on the standard view.

Kind regards, Adis

If this helped, please mark it as "Verified" for others facing the same issue

Keep in mind that it is possible to mark more than one answer as verified

Was this reply helpful? Yes No
Verified answer

Adis 6,069 Super User 2025 Season 2 on at

Like (1)

Report

I have to correct myself. @Waed Ayyad is right, I forgot about this option. Thanks for addressing it.

Kind regards, Adis

If this helped, please mark it as "Verified" for others facing the same issue

Keep in mind that it is possible to mark more than one answer as verified

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 301,119 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

In addition to the earlier replies, I would like to answer your last question. Out of the box, there is no option to prevent users from switching to the default view. In case you try to delete the standard view for the users, it will recreate it once the users opens the form.

In case you really need to have this option locked on particular forms, you can consider a customization. What is the background of this requirement? If it is about security, there is an option for table/field and form control override permissions using security role settings.

Was this reply helpful? Yes No
PT-01100339-0 364 on at

Like (1)

Report

Thank you, Waed and Adis. Your responses have addressed most of my concerns.

Regarding André’s question - I had previously asked about controlling field-level access on a form for different user roles. Currently, there doesn’t seem to be a direct way to prevent, for example, a sales clerk from editing purchasing-related fields. As a workaround, I’m considering using Personalized Views to manage visibility or editability based on the user.

Was this reply helpful? Yes No