Trying to do JSON import into Assets. Working fine except one attribute isn't splitting by the concatenator...
Attribute is select list, with unlimited cardinality.
Incoming data = "Leadership; Soft Skills"
Concatenator for the row, I've tried setting to ";" and ";\s".
Data is still imported in as "Leadership; Soft Skills", creating a new option for the attribute.
I have another attribute that is similar where the options are split by a ";", the only difference with that one is I'm using a Regex in the row configuration to remove text...
i.e.
JSON:
Although, I just noticed that this dropping the last value.....
Any ideas why the "Topic" isn't splitting by the concatenator?
Ideas on why the last option would be dropped?
Thanks @Ethel D_ Maresca however, JSON file is a little different than CSV import though, which is what you're describing. There are no columns in JSON.
I did figure it out though... Just needed a bit more complex Regular Expressions...
For the Job Family: Job Family - ((\w*\s*\&\s*\w*)\w*|(\w*\s*\w*\s*\&\s*\w*)\w*|(\w*\s*\w*)|(\w*))
For the Topic: ((?:^|\W)Programs and Projects|(?:^|\W)Finance and Administration|(?:^|\W)Environmental, Health and Safety|(?:^|\W)Soft Skills|(?:^|\W)Supply Chain|\w*)
I also had to add some automation to fix the "Environmental, Health and Safety" because it doesn't like commas and would load that in as 4 separate options. Basically, a Listener that looks for that attribute to be updated (or on an object creation), if it has the option "Environmental", "Health", "and", and "Safety", then remove them and add "Environmental Health and Safety"
Probably not the best solution, but it worked.....
In JIRA Assets, the "Concatenator" is used to combine multiple data locators (columns from your import file) into a single attribute (field) within your Assets object. You can specify a default concatenator, like a space ("\\s"), when creating an import configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.