Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Reference Objects not mapped in Asset CSV Import

Korede Folarin November 21, 2022 edited

I have created the SIM asset along with the Network Operator and SIM Status as related objects. But when I do a csv import and use the placeholder mapping,jsm_01.png jsm_02.png jsm_03.png jsm_04.png the object references are not mapped. I have included screen shots of:

1 SIM Object Attributes
2 SIM CSV
3 Imported SIMs with Unmapped Object References - Operator and Status
4 Import Mapping showing placeholder


1 answer

1 accepted

2 votes
Answer accepted
Frederic Chartrand
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 22, 2022

Hi @Korede Folarin 

I think that the problem is that your "Operator" attribute points to another Assets object and this object doesn't have values in it (meaning, the MTN object doesn't exist). Have you tried to create the object "MTN" in your "Network operator" object type first and then try to import your CSV ? When you map data in a CSV files to Attributes, if one of the Attribute is another Assets object, it needs to be there for the mapping to work. You will not be able to create a new Assets object from an Attribute mapping.

For an attribute referencing another Assets object, the object needs to be there first.

What you could do too is to create two objects mapping in your import configuration. One that will just create the "Network operator" objects and another one that will create your "SIM" objects. This way, they'll be able to reference to something existing.

Hope this helps

Have a nice day

Frederic Chartrand

FMX Solutions - Gold Solution Partner

Korede Folarin November 22, 2022

HI @Frederic Chartrand ,
I  populated the Network Operator Schema with objects before attempting the import and the referenced operator exists.

jsm_04.png

Frederic Chartrand
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 22, 2022

Awesome.

I just saw your last screenshot, my bad. Your AQL query is not right. it should be : Name = ${OPERATOR}

You say that the NAME of the object in this attribute fits the $ value of the {OPERATOR} value in your file.

Can you confirm that it works after ?

Like • 2 people like this
Korede Folarin November 22, 2022

Hi,
First, I didn't realise that the AQL is case sensitive and once I fixed that, the references were resolved and updated.

Thanks for your help.

Like • Frederic Chartrand likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events