Custom Metadata Types with Validation Formulas

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional metadata techniques are limited in describing metadata formats, making it difficult for third-party developers to create metadata that adheres to predefined standards, and struggle with accurately monitoring and flagging service disruptions in multi-server environments.

Innovation Solution

The implementation of custom metadata types with metadata relationships and validation formulas allows for the creation of custom metadata formats, enabling more sophisticated and consistent metadata management, including relationships with standard and custom objects, and supporting traversal of relationships within validation formulas.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional metadata techniques are used, then simplicity is maintained, but the ability to describe metadata formats and enable third-party developers to create standardized metadata is limited

Engineering Contradiction:
Improvemetadata format definition capabilityVSAvoidmetadata management system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments metadata management into distinct components: custom metadata types define formats, custom objects store instances, and validation rules enforce constraints. This segmentation allows third-party developers to work with standardized formats while maintaining system simplicity through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The metadata system is made dynamic by allowing custom metadata types to be defined and modified at runtime, enabling the system to adapt to different metadata formats and requirements without requiring system reconfiguration or deployment changes.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If custom metadata types with relationships are implemented, then metadata management sophistication is improved, but system complexity increases

Engineering Contradiction:
Improvemetadata relationship capabilityVSAvoidvalidation formula complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

Validation formulas act as intermediaries between custom metadata relationships and business logic requirements. These formulas provide a standardized mechanism to traverse and validate relationships without requiring complex custom code, thus managing complexity while enabling sophisticated metadata management.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The validation formula mechanism serves multiple functions: it validates relationship integrity, enforces business rules, and provides a standardized interface for traversing custom metadata relationships. This multi-functionality reduces the need for separate validation mechanisms, managing overall system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If declarative validations with formula references are used, then validation capability is enhanced, but the difficulty of detecting and measuring validation states increases

Engineering Contradiction:
Improvemetadata validation reliabilityVSAvoidvalidation state tracking difficulty
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements feedback mechanisms where validation formulas automatically evaluate custom metadata relationships and return validation states. This feedback loop provides clear visibility into validation status without requiring manual tracking, enhancing reliability while keeping detection simple through automated status reporting.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10311107B2Techniques and architectures for providing references to custom metametadata in declarative validations
Publication Date: 2019.06.04 SALESFORCE INC
  • US10311107B2 patent drawing
  • US10311107B2 patent drawing
  • US10311107B2 patent drawing

AI summary

A definition of a custom object specifying a custom format for metadata is received within a database system where creation of the metadata is required to comply with the custom format specified within the custom object with the metadata is associated with the custom object. At least a portion of the metadata refers to another custom metadata object type. The custom object having the definition is stored within the database system. A database record is created utilizing the custom object with reference to the another custom metadata object type. At least one aspect of an application is defined utilizing the database system using the metadata of the record.