Unified Data Dictionary Explorer for Multi-Tenant Database Dependency Visualization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional database development tools are inefficient in displaying information about all entities defined in a data dictionary, including basic information, fields, dependencies, metadata, and standard/custom objects, and fail to provide dependency information in a visual format that aids developers in understanding database system dependencies.

Innovation Solution

The development of a Unified Data Dictionary (UDD) explorer tool that allows users to explore and visualize metadata in a multi-tenant database system, providing a graphical view of dependencies between entities, enabling better understanding and management of database entities and their relationships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If conventional database development tools are used to display information about entities in a data dictionary, then basic information can be retrieved, but the tools are inefficient and cannot display comprehensive information including fields, dependencies, metadata, and standard/custom objects in a visual format

Engineering Contradiction:
Improvecompleteness of entity informationVSAvoidefficiency of information retrieval
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent segments the data dictionary information into distinct categories (basic information, fields, dependencies, metadata, standard objects, custom objects) and presents them in an organized hierarchical structure. This segmentation allows comprehensive information display while maintaining efficiency by enabling users to access specific segments as needed rather than processing all information at once.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a visual dimension to database entity display by generating graphical representations of dependencies and relationships. This transforms traditional text-based or tabular data into visual formats such as diagrams and graphs, enabling developers to comprehend complex entity relationships more efficiently and reducing information loss through visual encoding of metadata and dependencies.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Loss of information

If comprehensive entity information is displayed in detailed formats, then completeness of information is improved, but the complexity of the tool and ease of understanding deteriorates

Engineering Contradiction:
Improvecompleteness of dependency informationVSAvoidease of understanding dependencies
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent applies visual representation to display dependency information among database entities. By transforming abstract dependency relationships into visual formats such as graphical diagrams showing connections between entities, the system maintains complete dependency information while significantly improving ease of understanding. The visual dimension allows developers to quickly grasp relationship structures without being overwhelmed by textual complexity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The patent implements local quality by providing different levels of information detail in different parts of the interface. Summary views provide high-level dependency overviews for quick understanding, while detailed views allow drilling down into specific entity attributes, fields, and metadata. This localized variation in information density maintains completeness where needed while preserving ease of understanding in overview areas.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If all entity types (standard and custom objects) are included in the data dictionary, then versatility is improved, but the device complexity increases

Engineering Contradiction:
Improvecoverage of entity typesVSAvoidcomplexity of data dictionary tool
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universality by designing a unified data dictionary tool that handles multiple entity types (standard objects, custom objects, fields, dependencies, metadata) through a single integrated interface. The system provides consistent operations and visual representations across all entity types, reducing the need for separate tools or complex conditional logic. This multi-functional approach maintains versatility while managing complexity through standardized handling procedures.

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

Solution Approach 2:

The patent segments different entity types into distinct categories within the unified tool, allowing the system to manage complexity through organized classification. By dividing standard objects, custom objects, fields, and dependencies into separate but integrated segments, the tool can apply type-specific processing rules while maintaining a consistent user interface. This segmentation strategy enables comprehensive entity type coverage without overwhelming system complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8972439B2Method and system for exploring objects in a data dictionary
Publication Date: 2015.03.03 SALESFORCE INC
  • US8972439B2 patent drawing
  • US8972439B2 patent drawing
  • US8972439B2 patent drawing

AI summary

Mechanisms and methods for exploring objects in a data dictionary may enable embodiments to provide a simple and efficient tool for understanding dependencies between entities. The ability to provide a visual format for representing dependency information of entities may enable database developers to efficiently explore objects in a data dictionary and better understand the dependencies of entities in the database. In an embodiment, methods for exploring objects in a database can be applied to multi-tenant database systems.