Custom Object Field Mapping for Batch Data Import

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Third-party data management systems often fail to accommodate custom data management needs of individuals and organizations, as they rely on standard tables and fields that cannot store unique data requirements.

Innovation Solution

A data management system that allows customization by generating custom objects and fields, configuring data import objects with staging fields, and creating mappings between staging and target fields to import and manage custom data effectively.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If third-party data management systems use standard tables and fields, then the system structure remains simple and reliable, but the system cannot accommodate custom data management needs

Engineering Contradiction:
Improvecustom data management capabilityVSAvoidsystem structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments data storage into standard objects and custom objects. Custom objects are created as separate entities with their own fields, allowing custom data management without modifying the core standard system structure. This segmentation enables adaptability while preserving system reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements nesting by allowing custom objects to be associated with standard objects through parent-child relationships. Custom objects can be nested within standard objects, enabling hierarchical data organization that accommodates custom needs while maintaining the integrity of the standard system structure.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Adaptability or versatility

If custom objects and fields are generated to store custom data, then data management flexibility is improved, but the system complexity increases

Engineering Contradiction:
Improvedata management flexibilityVSAvoidsystem configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-defining the structure of custom objects and their relationships to standard objects before data import. Field mappings are established in advance, and custom objects are created with their fields configured beforehand, streamlining the data import process and reducing operational complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces field mappings as intermediaries between custom objects and standard objects. These mappings serve as mediators that define how data from custom objects is transferred to standard objects during import, simplifying the complexity of integrating custom data structures with the standard system.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If field mappings are created between staging fields and target fields, then data import accuracy is improved, but the configuration process becomes more complex

Engineering Contradiction:
Improvedata import accuracyVSAvoidmapping configuration complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system implements self-service by automatically generating field mappings based on the structure of custom objects and their relationships to standard objects. The mapping configuration is performed automatically during object creation, eliminating manual mapping configuration and reducing complexity while maintaining accuracy.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11429570B2Batch data import advance mapping
Publication Date: 2022.08.30 SALESFORCE INC
  • US11429570B2 patent drawing
  • US11429570B2 patent drawing
  • US11429570B2 patent drawing

AI summary

A method for batch data import using advance matching. The method includes: generating a target field for a custom object in an application including a plurality of objects; configuring a data import object with a custom staging field; generating a custom object group for the custom object specifying a parent/child relationship between the custom object and a standard object of the plurality of objects; generating, after generating the custom object group, a field mapping between the custom staging field and the target field in the custom object; and storing the field mapping between the custom staging field and the target field.