Copy user settings between environments

[Q&A] General
1

Hi,

On the user screen there is the option to copy settings (tiles/columns/options) from one user to another. Is there also a possibility to do this between enviroments ?

This request is from our tester, when we use dbcopy tool to copy prod to acc we need to newly create the test user accounts. It would be nice if we could copy the settings from dev or test for these user accounts.

If there is nothing available in which table(s) are these user settings stored?

image
image945Ă—309 8.69 KB

2

The user settings are stored in 2 tables:

useroverviewsettings and kendousersettings

It is not easy to transfer between environments, because most values are overview-id bound. That means that if an overview changes id, it will be lost and/or it will apply settings that do not make sense in the context. This leads to the message that a grid cannot be loaded or that in the system health check there are overviewsettings found for a nonexisting table.

My suggestion would be to create an exampe user in your live database, disable that one, and in your accdb, after copydbtool, create your users and base the settings on that one as a basis (or make the default settings as preferred in your own components)

I will include the more technical details below:

For kendousersettings (tiles on metro and dashboard and visible grids) it’s hard to read/understand:
{kendousersettings,<key,subkey,value>,user.equals(system:getcurrentuser())}

image
image793Ă—335 22.6 KB

I would recommend against transferring these.

For useroverviewsettings it is more readable and I have transferred these before. Be aware that this only works between the same model for the reasons stated above.

You can easily export the data and then in your import definition change the user they are connected to and so import new settings for the new people. Make sure your keyvalues here are user + overviewid. You can bind the user to the emailaddress so it is more readable.

you can check this with
{useroverviewsettings,<overviewid,columns,filters>,user.equals(system:getcurrentuser())}

1 Like
3

Hi Helena,

Exporting tables does indeed not look very easy.

I guess your suggestion to create a “dummy” user in the live environment would be the best solution for this. We’ll look into that.

Thanks for your detailed answer!