# US 2021/0240676 A1 · Batch data import advance mapping

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0240676 A1
- Document ID: US20210240676A1
- Status: Published application
- Kind: A1
- Application number: 16/985,989
- Filed: 2020-08-05
- Published: 2021-08-05
- Earliest claimed: 2020-01-31
- Assignees: salesforce.com, inc.
- Applicants: salesforce.com, inc.
- Inventors: Alison MEYER; Patrick TEWSON; Charles ALLEN
- Web page: https://patentgrep.com/patent/US20210240676A1

## CPC

- G06F 16/213: {with details for schema evolution support}
- G06F 16/2386: {Bulk updating operations (data conversion details G06F16/258)}
- G06F 16/2282: {Tablespace storage structures; Management thereof}
- G06F 16/2423: {Interactive query statement specification based on a database schema}
- G06F 16/258: {Data format conversion from or to a database}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

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.

## Claims

### Claim 1

A method, comprising:
generating a target field for a custom object in an application comprising 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.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
loading the batch data from the file into a plurality of staging records of the data import object comprising the custom staging field;
generating, based on the field mapping and the plurality of staging records, a first set of records in the custom object comprising the target field; and
generating, based on the plurality of staging records, a second set of records in the standard object.

### Claim 3 (depends on 2)

The method of claim 2, wherein the file is a comma-separated value (CSV) file comprising a column corresponding to the custom staging field.

### Claim 4 (depends on 2)

The method of claim 2, wherein the custom object group further specifies a field of the first set of records linking the first set of records to the second set of records based on the parent/child relationship.

### Claim 5 (depends on 2)

The method of claim 2, further comprising:
accessing a help text attribute of another custom staging field in the data import object, wherein the help text attribute references another target field; and
storing another field mapping between the another custom staging field and the another target field,
wherein the plurality of staging records further comprises the another custom staging field.

### Claim 6 (depends on 5)

The method of claim 5, wherein:
the another target field is for the standard object,
the second set of records comprises the another target field,
the another field mapping is stored in an object group associated with the standard object, and
generating the second set of records is further based on the another field mapping.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
configuring the data import object with an import status field and an imported record field associated with the custom object,
wherein the custom object group identifies the import status field and the imported record field in the data import object.

### Claim 8 (depends on 1)

The method of claim 1, wherein the plurality of objects comprises an accounts object and an opportunity object, and wherein the standard object is a contacts object.

### Claim 9

A system, comprising:
one or more computer processors; and
a memory storing instructions that when executed by the one or more computer processors, cause the one or more computer processors to:
generate a target field for a custom object in an application comprising a plurality of objects;
configure a data import object with a custom staging field;
generate 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;
generate, after the custom object group is generated, a field mapping between the custom staging field and the target field in the custom object; and
store the field mapping between the custom staging field and the target field.

### Claim 10 (depends on 9)

The system of claim 9, wherein the instructions further cause the one or more computer processors to:
load the batch data from the file into a plurality of staging records of the data import object comprising the custom staging field;
generate, based on the field mapping and the plurality of staging records, a first set of records in the custom object comprising the target field; and
generate, based on the plurality of staging records, a second set of records in the standard object.

### Claim 11 (depends on 10)

The system of claim 10, wherein the file is a comma-separated value (CSV) file comprising a column corresponding to the custom staging field.

### Claim 12 (depends on 10)

The system of claim 10, wherein the custom object group further specifies a field of the first set of records linking the first set of records to the second set of records based on the parent/child relationship.

### Claim 13 (depends on 10)

The system of claim 10, wherein the instructions further cause the one or more computer processors to:
access a help text attribute of another custom staging field in the data import object, wherein the help text attribute references another target field; and
store another field mapping between the another custom staging field and the another target field,
wherein the plurality of staging records further comprises the another custom staging field.

### Claim 14 (depends on 13)

The system of claim 13, wherein:
the another target field is for the standard object,
the second set of records comprises the another target field,
the another field mapping is stored in an object group associated with the standard object, and
generating the second set of records is further based on the another field mapping.

### Claim 15 (depends on 9)

The system of claim 9, wherein the instructions further cause the one or more computer processors to:
configure the data import object with an import status field and an imported record field associated with the custom object,
wherein the custom object group identifies the import status field and the imported record field in the data import object.

### Claim 16

A non-transitory computer readable medium (CRM) storing instructions that when executed by one or more computer processors, cause the one or more computer processors to:
generate a target field for a custom object in an application comprising a plurality of objects;
configure a data import object with a custom staging field;
generate 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;
generate, after the custom object group is generated, a field mapping between the custom staging field and the target field in the custom object; and
store the field mapping between the custom staging field and the target field.

### Claim 17 (depends on 16)

The non-transitory CRM of claim 16, wherein the instructions further cause the one or more computer processors to:
load the batch data from the file into a plurality of staging records of the data import object comprising the custom staging field;
generate, based on the field mapping and the plurality of staging records, a first set of records in the custom object comprising the target field; and
generate, based on the plurality of staging records, a second set of records in the standard object.

### Claim 18 (depends on 17)

The non-transitory CRM of claim 17, wherein the custom object group further specifies a field of the first set of records linking the first set of records to the second set of records based on the parent/child relationship.

### Claim 19 (depends on 17)

The non-transitory CRM of claim 17, wherein the instructions further cause the one or more computer processors to:
access a help text attribute of another custom staging field in the data import object, wherein the help text attribute references another target field; and
store another field mapping between the another custom staging field and the another target field,
wherein the plurality of staging records further comprises the another custom staging field.

### Claim 20 (depends on 19)

The non-transitory CRM of claim 19, wherein:
the another target field is for the standard object,
the second set of records comprises the another target field,
the another field mapping is stored in an object group associated with the standard object, and
generating the second set of records is further based on the another field mapping.
