Custom Metadata Types for Data Field Lifecycle Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current techniques for managing data dictionaries in complex environments are inefficient, leading to confusing, useless, and stale data due to inconsistent policies and limitations in metadata management, particularly in multitenant on-demand services environments where data is not accurately copied between sandboxes, resulting in incomplete lifecycle management.
Innovation Solution
The implementation of custom metadata types that allow for the definition of relationships between data and provide additional information, enabling robust and efficient data field lifecycle management by storing data dictionaries within the same service environment as the data being managed, using graphical user interfaces to add custom properties, and maintaining referential integrity through custom metadata types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If current techniques for managing data dictionaries are used in complex environments, then data repositories can be maintained, but the management becomes inefficient and data becomes confusing, useless, and stale
Solution Approach 1:
The patent segments data dictionary management by implementing environment-specific copies (source environment, target environment, and sandbox environments) and dividing management responsibilities through custom metadata types. This segmentation allows parallel management of different data versions and environments, improving efficiency while maintaining data accuracy through structured separation.
Solution Approach 2:
The patent implements copying by creating environment-specific copies of data dictionaries across different sandboxes and environments. Custom metadata types are copied and adapted to specific environments, allowing efficient management and testing without affecting the source data, thereby improving productivity while maintaining reliability through controlled replication.
2Adaptability or versatility
If data is copied between sandboxes using current techniques, then data can be shared across environments, but the data is not accurately copied resulting in incomplete lifecycle management
Solution Approach 1:
The patent applies preliminary action by establishing custom metadata types and environment-specific data dictionary structures before copying data between sandboxes. This preparatory framework ensures that data is copied with proper context and relationships intact, improving both portability and copying accuracy across environments.
Solution Approach 2:
The patent uses custom metadata types as intermediaries between source and target environments during data copying. These metadata types act as mediators that preserve relationships and contextual information, ensuring accurate data portability across sandbox environments while maintaining complete lifecycle management.
3Ease of manufacture
If spreadsheet or similar tools are used to manage data dictionaries, then a simple approach is available, but the approach becomes inefficient as data repositories grow in size and complexity
Solution Approach 1:
The patent implements universality by creating a multi-functional platform that combines the simplicity of traditional data dictionary tools with advanced capabilities for managing complex, multi-environment data repositories. The system provides both easy initial setup and scalable management through integrated custom metadata types and environment-specific copies, resolving the contradiction between simplicity and scalability.
Data Source
AI summary
Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.