Batch data import advance mapping

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 group, wherein the field mapping comprises records of the parent/child relationship;

storing the field mapping between the custom staging field and the target field and the parent/child relationship, in the custom object group; and

importing data into the custom object in the application based on the data corresponding to the records of the parent/child relationship in the field mapping.

2. The method of claim 1 , further comprising:

loading the data from a 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.

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

4. 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.

5. 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.

6. 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.

7. 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.

8. 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.

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 group, wherein the field mapping comprises records of the parent/child relationship;

store the field mapping between the custom staging field and the target field and the parent/child relationship, in the custom object group; and

import data into the custom object in the application based on the data corresponding to the records of the parent/child relationship in the field mapping.

10. The system of claim 9 , wherein the instructions further cause the one or more computer processors to:

load the data from a 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.

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

12. 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.

13. 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.

14. 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.

15. 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.

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 group, wherein the field mapping comprises records of the parent/child relationship;

store the field mapping between the custom staging field and the target field and the parent/child relationship, in the custom object group; and

import data into the custom object in the application based on the data corresponding to the records of the parent/child relationship in the field mapping.

17. The non-transitory CRM of claim 16 , wherein the instructions further cause the one or more computer processors to:

load the data from a 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.

18. 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.

19. 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.

20. 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

generate the second set of records is further based on the another field mapping.