I am currently researching a way how to make a default column configuration for all types and to spread it to all users (e.g. remove public_id, author, creation_time for all tables and users). Currently, you can define configuration for displayed table columns only for a logged in user.
My idea was to make a user config and then to spread it via updateMany in mongodb. This proves as a viable way BUT:
User config is not saved at all. It looks like it is, but once you log out and log in, the config is gone and you are in the default state. When viewing through browser console, you get HTTP 400 when saving the config.
EDIT: I found a topic about this, It should have been resolved last year but it seems it occurs again: Collumns preference cannot be saved
In mongodb, I see collection management.users.settings which contains the settings for my colleague, probably saved in previous release 2.2.0. However my colleague does not see this config anywhere, and copying it to my settings (under my user-id) behaves the same.
There is no mention of User settings in Datagerry API reference, for example under Users endpoint, so no dice again…
Can this be somehow fixed please?
The best scenario would be this:
Admin can define default column layout for all users, then users can subsequently define their own configs and save/load them via Configs button. Configs do survive between logout/login/restart.
If point one is no-go, then at least please fix the saving and loading of configs, I can do the rest via some automation through mongoDB.
We were not able to reproduce the “saving column config and relog”-issue. Everything works fine after logout and login, the filter is applied. Can you provide us more information on the issue to enable us to reproduce it?
Since every type has other identifiers for its fields, a configuration is saved per type (in this example the public_id of the type is 25) and user (in this case the public_id is 1).
If you have configurations in the management.users.settings which are not displayed, then you were maybe on the wrong type or the type was deleted.
Quoting you:
The best scenario would be this:
Admin can define default column layout for all users, then users can subsequently define their own configs and save/load them via Configs button. Configs do survive between logout/login/restart.
This would be a new feature. It will be discussed during our next feature meeting.
Thank you for your reply. From your example of settings and trial&error testing I have the following details for you.
Creation and persistence of custom configs per user IS POSSIBLE but it has a condition. The user already has to have some config present in user.settings collection for the type he creates the config for. Then the config persists even when logging out and logging in again and can be successfully used.
But if there is no config present in DBfor the specific type, then saving of the config for this type fails, see screenshot:
