High Issue Summary
Attributes that has the type Status with a current status I.e "active" gets removed when we import data from an external source like a CSV, LDAP import for example.
This affect Insight Version 8.5.2 and forward
Steps to Reproduce
- Create an Object Type with a Status Attribute (no need to select statuses)
- Create a few Objects and make sure the Status Attribute is set to Active
- You can also configure an Automation rule to set the Status to Active when an Object is created.
- Create a CSV file to import - so that New Objects will be created, and existing Objects will be "Missing Objects"
- Configure an Import (any, but easier with CSV) and map to your object type's Attributes, do not map the Status Attribute
- On the Object Type Mapping set:
- Missing Object: Update
- Attribute to edit: Status
- New value of attribute to edit: Inactive
- Sync the import
- First time the import runs, all objects will be created. If we had create the automation rule in Step 3, those objects will have ''Status' = Active
- Update some attributes in the CSV for some objects and import again, so that some Objects will be updated
Expected Results
Updated objects should keep the Status = Active, and only affected attributes should be updated
Actual Results
'Status' attribute from the updated objects will be removed. All updated Objects will show "No Value" for Status attribute
This does not happen when Missing Objects: Ignore
Workaround
Add an automation rule:
WHEN: object Updated IF: Status IS EMPTY THEN: Attribute Value: Status to Active
NOTE:
This happens to objects that are created within the UI, manually.
Objects created within the CSV Import, then edited to be assigned a status - the status will remain.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|