Configuration of Share Permissions for a Data Model Does Not Save the Changes

Question

For Data Admins and Data Designer users, there is a function available to configure share permissions for the Data Model. Sometimes it can be noticed that new changes are not being saved.

What steps can be performed to resolve this problem?

Prerequisites:

Documentation for Setting Data Model Access Permissions

https://documentation.sisense.com/docs/managing-access-to-data-models

Answer

The web server function to configure permissions for Data Models uses the Galaxy service.

On Windows Sisense versions:

Restart the Sisense.Galaxy service.

On Linux Sisense versions:

Delete the Sisense galaxy pod.

kubectl get pods -n sisense | grep galaxy

kubectl -n sisense delete pod galaxy-xxxxxxxxxx-xxxxx

A new Sisense galaxy pod will start up.

Notice:

Restarting of the Galaxy service is the initial troubleshooting step for this problem specifically, and in the majority of instances, this does resolve the problem.

The restarting of the service does not have a heavy impact on the application or require downtime.

If the problem still persists after restarting, it is suggested to gather the Galaxy service logs as well as a HAR file trace to be included in a support ticket.

Windows:

C:\ProgramData\Sisense\application-logs\galaxy\galaxy.log

Linux:

/var/log/sisense/sisense/galaxy.log

Generating a HAR file for troubleshooting:

https://support.sisense.com/kb/en/article/generating-a-har-file-for-troubleshooting-sisense

Document References:

https://documentation.sisense.com/docs/managing-access-to-data-models

https://support.sisense.com/kb/en/article/generating-a-har-file-for-troubleshooting-sisense

Updated 03-02-2023

Data Models

Elasticube