Skip to main content
Solved

User permissions and dataset disappear after PSO upgrade

  • January 30, 2023
  • 2 replies
  • 159 views

Forum|alt.badge.img+9

Hi Experts,

Customer is facing a post upgrade issue.

During the upgrade from 6.9.0.26 to 6.10.0.13 the Admin group has been dissociated form the users but they kept the admin rights. 

 They also lost the dataset they should be able to view. The workaround used by the customer was to add 'viewAllDataSets' permission to the default set which seems working. 

 

According to our initial investigation, we did the same version upgrade process (6.9.0.26 to 6.10.0.13) in local environment, however, we were unable to replicate the issue. While comparing the pre and post system data files of the customer, we found that the "Administrator" group data is missing in the Groups query. But the Group_Permission and User_Group sections still contain the "Administrator" group id. But the point is Group table has the “Administrator” record in the database.

Do anyone of you faced these kinds of issues before? Are there any possibilities to sort this issue 

 

 

 

 

 

 

Best answer by Dilushkumar Vasudevan

I believe this issue was new to PSO folks!

We did not encounter the same issue during our local upgrade process; the upgrade was successful for us, and all functionalities are working as usual.

We believe this issue may have been caused by improper upgrade activity, but we couldn't determine the exact root cause. As a workaround, we have implemented the following:

R&D's suggestion: Manually apply/add the "Administrator" group to the PSO workbench.

We hope this will resolve their issue.🙂

Note: When adding the necessary group, ensure to consider the permission set for the "Administrator" group.

View original
Did this topic help you find an answer to your question?

2 replies

tomgreenwood
Superhero (Employee)
Forum|alt.badge.img+24
  • Superhero (Employee)
  • 423 replies
  • October 2, 2023

Hi Dilushkumar, it’s difficult to know what happened without knowing the full story here.  Perhaps the upgrade process wasn’t followed correctly? When are performing a major upgrade you need to export and import the system parameters from the previous version.

I see this was a while ago now so hopefully you managed to resolve it ?

Thanks,

Tom


Forum|alt.badge.img+9

I believe this issue was new to PSO folks!

We did not encounter the same issue during our local upgrade process; the upgrade was successful for us, and all functionalities are working as usual.

We believe this issue may have been caused by improper upgrade activity, but we couldn't determine the exact root cause. As a workaround, we have implemented the following:

R&D's suggestion: Manually apply/add the "Administrator" group to the PSO workbench.

We hope this will resolve their issue.🙂

Note: When adding the necessary group, ensure to consider the permission set for the "Administrator" group.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings