-
Suggestion
-
Resolution: Unresolved
-
None
-
10
-
17
-
When using a CSV import to import a data set that should update the existing Objects already in Insight (needs to update two attributes on these Objects).
If the Object is not present based on the identifier, it should not create a new Object.
Another example will be:
- I would like to create computer Accounts based on the data available in SCCM.
- Also, I would like some additional information for the accounts available in SCCM from the Active Directory.
The problem I'm running into is that, as most ADs I've seen too far, it's not the cleanest system and there's a lot of outdated or unused computer accounts, which would now also be created as objects.
So in this case I would like the SCCM import to be the "main system" to be able to create objects and I would like the AD import only to add data to existing objects.
Long story short: We need an option in the import "do not create new objects, only update existing ones"
- links to
[JSDSERVER-7160] Import feature - "Do not create new objects"
A workaround I received was to do something like the following:
Let's say I have a "Server" object type that is populated by Insight Discovery and I only want Server objects created by Insight Discovery in my Schema, so any new objects in a different CSV import for updating attributes on "Server" objects would get ignored. With the following configuration, only the "Server" objects that exist in the Schema would get updated and no new objects would get created.
The Insight Discovery Import populates an "Object Hash" attribute on the "Server" object type for each "Server" object being imported. To make this a required field, I will select the gear icon next to the "Object Hash" attribute on the "Server" object type. From there, set the "minimum cardinality" to 1. You can then import a CSV like this with empty "Object_hash" values:
Name,Test_attribute,Object_hash
new-server-object,this_object_wont_even_get_created_because_of_cardinality_constraint,
existing-server-object1,i_will_update_the_Test_attribute_value,
...And the "new-server-object" object won't get created because since it doesn't already exist in Insight, Insight will try to create it -> hit the cardinality constraint -> fail to create this record. The "existing-server-object1" object already exists, so the "Test_attribute" for it will still get updated and its "Object_hash" will not get wiped out assuming that the "Empty Values" config is set to "Ignore" for the object type mapping configuration on the import. Although this does appear to mark the "result" of the Import as "OBJECT_TYPE_ERRORS" instead of "FINISHED", so the feature in this Jira would still be a much better solution.
I'm with Richard, this is a much needed option when extending your dataset from other (secondary) resources.
Three years old Issue in RIADA and it is suggestion?
2. second problem, also connected to this one... required Label in import - it is really anoying
- if I do aditive import from second source, when I have same IDs with Insight Object attribute ID, why I should rename original Insight label field?
- it is aboslute without any logic, If I am pairing source data by some Identifier, why I has to map Name to another attribute?
- .... oh I know, becuase this stupid import create new object, and without label it is not possible
Hello, this is really big problem in Insight
If we have more imports and only one is "initial" and then we need to ADD values only to existing Objects, it is not possible, because all objects from additional import are created.
how to import object from one database and add info from another, where are milions of rows?
the same Jira import
the same multiple cascade CSV
is not there some workaround?
for example use Filter data source by IQL - ${Source.ID} == ${Insight.Id}
?
Needed