Objective
Keep a Data Source usable without deleting and recreating it. For example, edit a Data Source when an external database password rotates. Edit it when the host changes after an infrastructure migration. Edit it when a new schema must be visible, or when SSL settings change.
When to use
Use this task when:
- credentials changed.
- host, port, or database name changed.
- schema access changed.
- SSL mode or CA certificate changed.
- metadata needs better operator context.
Before you start
Confirm what changed:
- credentials: update Username or Password.
- database location: update Host, Port, or Database Name.
- schema visibility: update the schema list.
- security: update SSL Mode or CA Certificate.
A Data Source update affects future Report generation. Reports already generated stay unchanged.
Step by step
1
Open Data Sources
Go to Data Sources.
2
Find the connection
Locate the card for the Data Source you need to edit.
3
Open the edit form
Click the three vertical dots () on the card and select Edit.
4
Update the fields
In Edit Connection, change the fields that need correction.
5
Save changes
Click Save Changes.
6
Test the connection
Run Test Connection to confirm the updated settings work.
The Password field appears empty for security reasons. Enter a new value only when changing the password. Leaving it blank keeps the current password.
Field guide
Expected result
The Data Source keeps the updated configuration. After a successful test, operators can rely on it for Templates and Reports.
Common errors and care points
Leaving password blank unintentionally
Leaving password blank unintentionally
Leaving Password blank preserves the existing password. Enter a new value only when the credential changed.
Changing host without testing
Changing host without testing
Host and port changes can point Reporter to a different database. Always run Test Connection after saving.
Removing a schema that Templates use
Removing a schema that Templates use
If a Template or filter depends on fields from a schema, removing that schema can break future generation.
Editing when the connection should be retired
Editing when the connection should be retired
If no reporting process uses the database, delete the Data Source instead of editing it.
Next steps
- Use Test a Data Source Connection after every connection change.
- Use Generate a Report only after the connection is healthy.
- Use Delete a Data Source when the connection is retired.