Unanswered

User set default personal view in Model driven but it not still default return the default by admin

(2) Share

Report

Posted on by Marianoz0503

The user set a default personal view in the Model-Driven app, but it is still not the default; it reverts to the admin's default view.

Categories:

Error handling

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Jon Unzueta 1,827 Super User 2025 Season 2 on at

Like (0)

Report
User set default personal view in Model driven but it not still default return the default by admin

@
When a user sets a default personal view in a Model-Driven app but it reverts to the admin's default view, it often indicates that there might be some settings or configurations that need to be adjusted. Here are some steps to diagnose and resolve this issue:

Verify View Customization:

Ensure the user correctly saved their personal view as default. They can do this by selecting their personal view, clicking on the view dropdown, and then selecting "Set as Default".

Check App Settings:

If the app has been published with a specific default view for all users, it may override personal views. In the app designer, check the view settings to ensure that the user’s personal view is configured to have priority.

Ensure Permissions:

Confirm that the user has the appropriate permissions to set personal views. They should have at least 'User' level access to the entity in question. Lack of sufficient permissions might lead to limitations in view settings.

Review System Administrator Settings:

Check if the administrator has enforced a specific view for certain entities or if there are any policies that affect user interface customization within the app.

Clear User Cache:

Sometimes, browser cache may retain old settings. Clear the cache or try accessing the app in a different browser or in incognito mode to see if the change takes effect.

Update the App:

If changes have been made to views, ensure the app has been republished. Sometimes changes to views require the app to be republished for them to be visible to users.

Check for System Jobs:

Review any workflows or system jobs that may modify user settings or views on a schedule, which could revert changes made by the user.

Testing in Different Environments:

If possible, test the same scenario in a different environment to identify if the problem is related to specific environment settings or configurations.

🏷️ Tag me if you have any further questions or if the issue persists. ✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems. ❤️ Give it a Like if you found the approach useful in any way.

Was this reply helpful? Yes No
JS-07111234-0 2 on at

Like (0)

Report

User set default personal view in Model driven but it not still default return the default by admin

Hi, i have simmiliar issue: when user set the default flag to the other view (personal or public) and later log out and log in (or refresh the card in browser) the default flag reset to the main default view.

@Jon Unzueta - in point 2 You said " In the app designer, check the view settings to ensure that the user’s personal view is configured to have priority." - where can i find that priority setting of personal view? i don't see it anywhere.

Thanks in advance

Was this reply helpful? Yes No