When adding a new column to a Managed View via the Administrator module (V8i SS4 8.11.11.567). I will move this new column to the top then apply the changes and close out and when I come back in the newly added column is at the bottom of the Selected columns list. It takes me several tries before PW retains the change. Kind of a pain, does this happen to others?
I just tried to reproduce it in my 08.11.11.574 admin, basically i made a view then went back into it, added another column, moved it to the top, went out and then back in again and it was still in the same spot. This is what you were doing correct?
What you are describing was actually an old TR that has been fixed, I actually filed it and verified the fix was done.
This TR was not fixed. We have 08.11.11.574 client and server. When I place a new column and move it up the list it always defalts back to the bottom of the list. There is no way to change it's position.
I have recently updated to 8.11.11.590 and have found this issue hasn't been resolved. Just as Neil explained I add a new column and save and come back in and its back to the bottom of the list.
to add to my previous post our Integration Server is running 8.11.11.586 version and Admin & Client are running the 590 version so it should work according to Marty testing results.
The issue does still exist.
Here's what I've found: When PWA will not allow you to specify the column position, have a look in the dms_viewcolui table to see if personal instances of the view have been defined for the global view being modified. In my testing instances of the global view were created by the system, not by the user.
The situation where ProjectWise will refuse to allow you to position a column in a global view exits where the same user has logged in to PWE and the system has created a personal instance of the global view being modified.
For example: Log in to PWE as an admin, and browse to a folder that has a global view. Log out of PWE. Have a look in the dms_viewcolui table to see if PW created a personal instance of the view (i.e. a system generated instance of the global view that is user specific). Once this exists, the same user cannot specify the column order for that global view in PWA.
Logging in to PWA as a different admin user (where a personal instance of the view does not exist) will produce a result where the user can modify the view as desired.
Deleting the rows from the dms_viewcolui table for the admin user will also result in the desired result.
For any user that also has a personal instance of the same global view, any column added to the view will be displayed in PWE at the far-right of the view, regardless of where it is positioned in the global view definition.
PW = 08.11.11.574
Scott