-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
10.2.0, 5.12.15, 5.17.5, 10.1.2
-
1
-
Severity 3 - Minor
-
Issue Summary
This is reproducible on Data Center: (yes)
During object import, objects are duplicated when object type mapping has two identifiers and one is another referenced object
Steps to Reproduce
- Create object type called "City" in your schema (with just default attributes). City object Type should not have any objects.
- Also create an object type called "Employee" with the default attributes and an attribute of "City" of the City object type created in step 1
- Create an import configuration in your schema with the attached CSV file
- After the configuration is created, create an object type mapping within the configuration selecting the Employee object type created in step 2 and set the identifiers of the mapping to be "Name" and "City" and ensure both are ticked (See screenshot for end result of import configuration)
- Ensure that for the Employee object type mapping, Missing objects are ignored
- Execute import and check that the objects were correctly imported
- Execute import another time without making any changes
Expected Results
There should not be any duplicates.
Actual Results
It creates duplicate.
Workaround
Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JSDCLOUD-10045 Import duplication when object type mapping has two identifiers and one is another referenced object
-
- Closed
-
- links to
[JSDSERVER-16054] Import duplication when object type mapping has two identifiers and one is another referenced object
Status | Original: Needs Triage [ 10030 ] | New: Short Term Backlog [ 12074 ] |
Support reference count | New: 1 |
Labels | New: ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 990744 ] |
Description |
Original:
h3. Issue Summary
This is reproducible on Data Center: (yes) During object import, objects are duplicated when object type mapping has two identifiers and one is another referenced object h3. Steps to Reproduce # Create object type called "City" in your schema (with just default attributes) # Also create an object type called "Employee" with the default attributes and an attribute of "City" of the City object type created in step 1 # Create an import configuration in your schema with the attached CSV file # After the configuration is created, create an object type mapping within the configuration selecting the Employee object type created in step 2 and set the identifiers of the mapping to be "Name" and "City" and ensure both are ticked (See screenshot for end result of import configuration) ## Ensure that for the Employee object type mapping, Missing objects are ignored # Execute import and check that the objects were correctly imported # Execute import another time without making any changes h3. Expected Results There should not be any duplicates. h3. Actual Results It creates duplicate. !Screenshot 2025-02-21 at 4.33.17 PM.png|width=391,height=474! h3. Workaround Required, if there is no workaround please state: Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
This is reproducible on Data Center: (yes) During object import, objects are duplicated when object type mapping has two identifiers and one is another referenced object h3. Steps to Reproduce # Create object type called "City" in your schema (with just default attributes). City object Type should not have any objects. # Also create an object type called "Employee" with the default attributes and an attribute of "City" of the City object type created in step 1 # Create an import configuration in your schema with the attached CSV file # After the configuration is created, create an object type mapping within the configuration selecting the Employee object type created in step 2 and set the identifiers of the mapping to be "Name" and "City" and ensure both are ticked (See screenshot for end result of import configuration) ## Ensure that for the Employee object type mapping, Missing objects are ignored # Execute import and check that the objects were correctly imported # Execute import another time without making any changes h3. Expected Results There should not be any duplicates. h3. Actual Results It creates duplicate. !Screenshot 2025-02-21 at 4.33.17 PM.png|width=391,height=474! h3. Workaround Required, if there is no workaround please state: Currently there is no known workaround for this behavior. A workaround will be added here when available |
Link |
New:
This issue is related to |