admin schema - a set of views for more convenient interaction with system tables from the
public schema - entities, schemas, table fields, triggers, constraints and others.
admin is not a system schema, i.e. it isn't added to instances by default. So after loading this schema into your solution, you can edit its views just like any other custom user views.
You will need to pick up the current version of the
admin schema from the admin template. To do this, follow the link
admin in the left "Save Schema" field and click
Save. Zip-archive with the schema will be saved to your device.
Next, go to the schema upload interface on your instance:
Select the zip-archive with the
admin schema in the right "Restore Schema" field and click
Restore. If the download is successful, a
Success message will appear.
If an error occurs instead of a success message, you will have to manually fix the problems using the message in the error message.
You can also set the flag "Mark invalid objects as allow_broken", and schema will be forced to load, but after that you will have to manually resolve conflicts in all views marked with
allow_broken = true
Please note that the schema will be completely overwritten. If you had edited views from the
adminschema or created new ones, they will be overwritten after the update.
When creating a new solution, specify
admin as a template
An instance will be created for you, including the current version of the
You can deploy a neww instance with an admin schema by one button through onboarding: click here
You can also choose any of our other templates. We try to keep the admin panel version up to date in our template solutions, but if for some reason the chosen template hasn't been updated for a long time, and the admin panel in it is outdated, follow the steps from the subsection "Add or update the schema in your instance" above.
If you are using your own admin schema, you should modify it to reflect the changes below
funapp.translationsconfigures and stores translations
funapp.user_settingsstores user settings
entity_idfield has been renamed to
user_view_generator_allow_brokenfields are moved from the
public.schemasfield to a separate table
public.rolesis removed - it is no longer used;
public.role_column_fieldsis divided into
check, which allows you to more flexibly manage access rights (prohibit updates for specific fields and allow insertion, for example);
schema_idfield added to
save_restore_keyfield added to
is_alternate_keyfield added to