Database Manager
Overview
The Database Manager is made available if your organisation has 1 or more dedicated (private) PostgreSQL databases linked to it. It exposes administration functionality for you to manage your database at a high level without the need to directly maintain the database.
Access the database manager
Navigate to the Admin Panel and on the left hand menu select Data then Database
User Manager
The User Manager allows you to create, manage or remove database users. You can assign permissions to a user to allow them to access and edit the database directly so that they can use a database connection in 3rd party applications (QGIS, ESRI etc).
- Select the 'Users' tab to open the User Manager.
- Select an existing user from the drop down menu, you can type to filter.
- Or, create a new user from the navigation menu.
Edit Permissions
Once a user is selected or created, new options become available. Click on 'Edit Layer Permission' to assign a new permission to this user. The available permissions will then be shown.
- a green tick indicates permission is already assigned
- a red exclamation indicates permissions is not assigned
To grant or revoke a permission, click on the card for the permission, e.g 'View Layer'. A popup window will show the intended action:
- the SQL commands to be run may be shown, for your peace of mind
- all commands are generated server side and cannot be modified
- click 'Grant' or 'Revoke' to run the command
Fixing Errors
If managing a table created outside of XMAP you may encounter some errors if the table is not compatible with XMAP or other 3rd Party applications. XMAP performs checks to ensure your tables will remain compatible across a variety of applications. In the event of an error, you may be presented with a 'Fix' button (see image below). This will attempt to rectify the problem by applying a set of permissions and configurations to the table. It's recommended to read any clarifications below regarding specific errors if you are managing tables created outside of XMAP and ensure that no warnings are made regarding potential issues.
No Sequence
This fix is not expected to cause any compatibility issues, however if a new primary key column is created it's recommended that a Force Refresh is applied in XMAP to reload the configuration. If a 'No Sequence' error is shown, the Fix button will apply the following:
This fix is not expected to cause any compatibility issues, however if a new primary key column is created it's recommended that a Force Refresh is applied in XMAP to reload the configuration.
- Check for the existence of a primary key
- If no key is found one will be created
- Create a sequence if needed and set the sequence to the highest value in the primary key field
Troubleshooting
An error says 'No Sequence'
Your layer is missing a primary key and/or sequence. Any layers that are registered in XMAP require these. A future update may enable support for granting permissions on layers without a primary key and sequence.
Related Articles
Using your XMAP layers in QGIS
Overview For customers who have a dedicated database connected to XMAP, you can access your data directly in QGIS. This means that both XMAP and QGIS are reading from the same source, so there is no risk of multiple versions of your data existing in ...