Single Record Access Across Multiple Database Instances

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In organizations, contact records stored in a database are often managed by multiple separate units, leading to data duplication and separation issues, as each unit maintains its own data instances, resulting in the need for multiple copies of contact records across different units.

Innovation Solution

A system that allows access to data in multiple instances through a single record, where a primary database stores contact records and multiple instance databases associated with secondary applications can sync data selectively, enabling users to switch between different instance databases while maintaining data integrity and reducing redundant storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If each unit maintains its own data instances for contact records, then data separation and unit-specific data access are improved, but data redundancy and storage complexity increase

Engineering Contradiction:
Improveunit-specific data accessVSAvoiddata redundancy
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent segments data access rights and instances by unit while maintaining a single centralized contact record. Each unit receives a customized view of the contact record through its own data instance, allowing unit-specific access without duplicating the actual contact data stored in the primary database.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces data instances as intermediary objects that mediate between the primary contact record and each unit. These instances act as virtual copies or projections that provide unit-specific data views without physically duplicating the underlying contact record data.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple copies of contact records are stored for each unit, then data separation between units is improved, but device complexity and storage requirements increase

Engineering Contradiction:
Improvedata separationVSAvoidstorage structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges all contact record data into a single primary database record, eliminating the need for multiple physical copies. Different units access this single record through their respective data instances, which provide customized views without requiring separate storage structures for each unit.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If selective synchronization is enabled between primary and instance databases, then data management efficiency is improved, but synchronization complexity and processing requirements increase

Engineering Contradiction:
Improvedata management efficiencyVSAvoidsynchronization mechanism
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies local quality by enabling selective synchronization based on specific criteria for each unit's data instance. Not all contact records need to be synchronized with all units; the system allows configuration of which records should be synced to which instances based on unit-specific requirements, optimizing data management efficiency.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11494504B2Access to data in multiple instances through a single record
Publication Date: 2022.11.08 SALESFORCE INC
  • US11494504B2 patent drawing
  • US11494504B2 patent drawing
  • US11494504B2 patent drawing

AI summary

Systems, devices, and techniques are disclosed access to data in multiple instances through a single record. A selection of a record may be received through a user interface. The record may be stored in a database. Aspects of the record may be received from the first database. and displayed on the user interface. A first additional aspect associated with the record may be received from a first instance database associated with a first instance of a secondary application and displayed on the user interface. A selection to switch to a second instance of the secondary application may be received through the user interface. A second additional aspect associated with the record may be received from a second instance database associated with the second instance of the secondary application and displayed on the user interface the in place of the first additional aspect associated with the record from the database.