Column Refresh is a feature that allows you to fetch newly added columns from your external database tables without having to reconfigure the entire datasource. This is particularly useful when your database schema evolves over time and you want to make new columns available to your agents while preserving your existing custom descriptions.
When to Use Column Refresh
You should use the Column Refresh feature when:
Your database has added new columns to tables that you've already connected to elvex
You want to make these new columns immediately available to your agents
You want to preserve your existing custom descriptions and configurations
You prefer a quick update over reconfiguring the entire database connection
What Gets Updated
When you refresh columns, elvex will:
Identify new columns in existing tables that you've already connected
Preserve existing configurations - your current table selections and custom column descriptions remain unchanged
Skip column modifications - changes to existing columns (like data type changes) are not included
How to Refresh Columns
Step 1: Navigate to Your Database Datasource
Go to the Datasources section in elvex
Find and open the database datasource you want to update
Click Edit to access the configuration
Step 2: Review the Refresh Card
In the datasource configuration view, you'll see a "Refresh Columns" card that shows:
A description of what the refresh will do
A Refresh button to initiate the process
Step 3: Initiate the Refresh
Click the Refresh button
elvex will connect to your database and analyze the schema
This may take a few moments depending on your database size and connection speed
Step 4: Review Detected Changes
Once the refresh completes, you'll see a preview showing:
New columns organized by table, with their:
Column name
Data type (e.g., VARCHAR, INTEGER, TIMESTAMP)
Primary key indicator
Unique constraint indicator
Auto-generated description
Step 5: Customize Column Descriptions (Optional)
For each column, you can edit the Description field
These descriptions help your agents understand the column's purpose and use it more effectively
If elvex has auto-generated a description from your database comments, you can keep it or modify it
Step 6: Apply Changes
Click the Apply Changes button to add the columns
The new columns will be added to your existing tables
A summary of applied changes will appear on the configuration summary
Step 7: Save the Datasource
Review the updated configuration in the summary view
Click Save to persist the changes
Your agents now have access to the new columns
Example Scenario
Before Refresh:
You have a
userstable connected with columns:id,name,emailCustom descriptions explain what each column contains
After Adding Columns to Your Database:
Your DBA adds a
tiercolumn to theuserstable
Using Column Refresh:
Click Refresh and wait for the analysis
You see
tierlisted as a new column in theuserstableYou customize the description for
tierto be more specific to your needsYou click Apply Changes and save
Your agents now have access to these new columns without losing the existing
usersconfiguration
Troubleshooting
"Connection Failed" Error
Verify your database credentials are still valid
Check that the database server is accessible from elvex
Confirm that your service account hasn't been deleted or permissions haven't changed
"No Changes Detected"
This message appears when no new columns have been added since your last configuration
Your schema may not have changed, or the changes may be to existing columns (which aren't included in refresh)
Columns Not Appearing After Applying Changes
Ensure you clicked Save on the datasource configuration after applying changes
The changes are only persisted when you save the datasource
Refresh the page if changes don't appear immediately
Security Considerations
Column refresh uses existing credentials - it connects to your database using the same service account credentials you provided during initial setup
Read-only access required - elvex only reads schema information, it doesn't modify your database
Custom descriptions stay private - descriptions you add in elvex are stored within elvex and not sent to your database
Access control unchanged - adding new columns through refresh doesn't change who can access your datasource