Manage solution versions and history.
Reference → Solution → DevOps → Track Changes → Recent | Version Control | Cross-Reference | Unused | Use Count
Version Control (Reference): Maintains summaries
Version Control tables maintain a summary,by Module and Configuration Table
,of
thecurrent
versionversions and last
modification ofmodifications for all solution elements
in a solution.
Access: Track Changes → Version Control
Parent Page: Track Changes Tools (Reference)Table of Contents maxLevel 2 minLevel 2 indent 10px exclude Steps style none
Purpose
TheVersion Control data
isautomatically
used to ensureensures consistency when connecting to Runtime for online changes. Designer's Runtime/Diagnostics interface compares configuration versions with running solution versions
, determiningto 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.
See Also
- Track Changes Tools (Reference) - Parent section
- Runtime Diagnostics (Reference) - Online configuration
- Recent Changes (Reference) - Change tracking
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...
In this section:| Page Tree | |||
|---|---|---|---|
|