Potentially, the current behavior can be explained by having a query passed to the form from the menu item. I just tried this in an environment having a preview of 10.0.39 applied. I then get a warning about a query conflict and you can choose to load the preferred query. In case this is not sufficient for you, you can try to find where Microsoft is generating the link to load the correct query and call the logic yourself.
Thanks, I know where 'they live'. I'm trying to load a specific view during the forms init() call. It appears that Microsoft butchered the standard functionality on the ProjProjectsListPage form, where I can load the default view for the user, but the actual filters are cleared and show only when one switches between views.
There are some saved views stored as resources and deployed to all users with help of some x++ coding. The class EcoResSavedViewSysSetup is having an example how to deploy saved views.
If you already have a saved view, an administrator can use the form Personalization to copy saved views or publish them as an organization template.
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.