Customised field information "leaking" to other user's sessions?
Hi,
two of our users have notified us of a phenomenon concerning customised fields in the personal section of the PMP: Sometimes columns relating to fields the user did not add to the category appear in a category. In one user's case he sometimes had columns for fields one of his co-workers had added to his own similarly named category and vice versa. When opening an entry or the category's settings only the user's own fields were shown and no fields corresponding to the alien columns.
This does not happen every time, but I ran into the same phenomenon today when I found some alien columns in one of my own categories, though only during one session.
So far we have told the users that the alien columns are merely American weather balloons, but of course we are interested in a solution of the problem.
We are currently using build 6401 with the integrated database on a Windows 2k8R2 server and are planning to update to build 6403. Since the release notes do not mention this phenomenon I decided to ask without waiting for the update.
Regards,
Dennis
two of our users have notified us of a phenomenon concerning customised fields in the personal section of the PMP: Sometimes columns relating to fields the user did not add to the category appear in a category. In one user's case he sometimes had columns for fields one of his co-workers had added to his own similarly named category and vice versa. When opening an entry or the category's settings only the user's own fields were shown and no fields corresponding to the alien columns.
This does not happen every time, but I ran into the same phenomenon today when I found some alien columns in one of my own categories, though only during one session.
So far we have told the users that the alien columns are merely American weather balloons, but of course we are interested in a solution of the problem.
We are currently using build 6401 with the integrated database on a Windows 2k8R2 server and are planning to update to build 6403. Since the release notes do not mention this phenomenon I decided to ask without waiting for the update.
Regards,
Dennis