WORKAROUND: We have decided to use JSON Import instead of CSV Import. We had a goal to simplify the process for our clients, but CSV Import seems to be complicating it even more than JSON Import. Not worth the time and effort to implement data from CSV Imports.
Context: I have an array of JSON objects under a field called "relationships". Each JSON object represents the CI/AWS Resource that the current CI record has relations with.
Here is an example:
What I want to achieve:
Create CIs for each JSON objects in the array, then associate it with its respective CI. This is a CSV Import from AWS Config Advanced Query.
Reason for using IE-ETL:
This was a client request to implement a temporary IE-ETL as an alternative discovery. If this is indeed a limitation, then it's time for a re-evaluation.
What I have tried:
- I tried using Multi-Script Operation w/ Multiple Output, but I don't know how to make it work.
Issue with this approach... I need to explicitly/manually create an output column and then map the data to the column. I have tried creating a column directly from script, but it doesn't seem to work. Using this approach practically requires you to assume a max number of relationships this CI can have which is not ideal.
I believe this is what ServiceNow wants me to do in the meantime? Since you can add multiple lookups for Network Adapters in the attribute/field mapping view. - I thought of creating the CI directly from the script.
But... how am I supposed to establish the relationship? One is in a staging environment, the other in a production environment. It is also not wise to do this way, as there won't be rollback options.
Utah, latest version. PDI, I can grant access for experimenting if needed.
