Manage solution versions and history.
Reference → Solution → DevOps → Track Changes → Recent | Version Control | Cross-Reference | Unused | Use Count
Version Control (Reference): Maintains summaries by Module and Configuration Table of current versions and last modifications for all solution elements.
Access: Track Changes → Version Control
Table of Contents maxLevel 2 minLevel 2 indent 10px exclude Steps style none
Purpose
Version Control data automatically ensures consistency when connecting to Runtime for online changes. Designer's Runtime/Diagnostics interface compares configuration versions with running solution versions to determine online configuration capability.
Table Columns
Default Visible Columns
| Column | Description |
|---|---|
| VersionID* | Version identifier |
| Module* | Module name |
| TableType* | Database table classification |
| Lines* | Number of entries |
| ChangedSinceBuild* | Changes after last build |
| DateModified* | Last modification date |
Additional Columns
| Column | Description |
|---|---|
| ID | Unique record identifier |
| ChangedSincePublish | Changes after last publish |
| DateCreated | Record creation date |
*Columns marked with * are displayed by default
Online Configuration
Version Control enables:
| Feature | Function |
|---|---|
| Consistency Check | Validates configuration versions |
| Hot Reload | Determines safe online changes |
| Sync Status | Shows out-of-date modules |
| Conflict Detection | Identifies version mismatches |
Navigation
Double-click any row to navigate to that configuration table in Designer.
Use Cases
Development
- Track module changes between builds
- Identify modified tables
- Monitor solution evolution
Deployment
- Verify build readiness
- Check publish status
- Confirm version alignment
Maintenance
- Identify stale modules
- Track modification patterns
- Plan updates systematically
Integration
With Runtime
- Enables online configuration updates
- Validates hot reload compatibility
- Synchronizes changes dynamically
With Designer
- Powers diagnostics interface
- Supports version comparison
- Enables safe online editing
Best Practices Checklist
- Review before build/publish operations
- Monitor ChangedSinceBuild column
- Verify version consistency before deployment
- Use for impact analysis of changes
In this section...
| Page Tree | ||
|---|---|---|
|
Using the Version Control Table
The data from the Version Control is automatically used by the platform to ensure consistency when connecting the Solution in execution (Runtime) in order to perform online changes.
The Designer UI under Runtime / Diagnostics compares the versions of your configuration files with the versions of all the tables in the solution in execution, allowing the online configuration to proceed or remain in offline configuration, showing which parts of the solution are out of date.
→ Go to Runtime Diagnostics for more information on online configuration and hot reload procedures.
Version Control Table Columns
Property | Description |
|---|---|
ID | Assigns a unique identifier to each record. |
VersionID* | Specifies the version identifier of the record. |
Module* | Identifies the module to which the record belongs. |
TableType* | Classifies the type of database table. |
Lines* | Counts the number of lines or entries. |
ChangedSinceBuild* | Flags changes made since the last build. |
ChangedSincePublish | Indicates changes made since the last publication. |
DateCreated | Records the date when the record was created. |
DateModified* | Captures the date when the record was last modified. |
*(Column displayed by default on data grid)
| Tip |
|---|
Double-click on a row navigates to the Designer configuration UI for the selected table. |
In this section: