Hi @Peter Suhajda 
Could you please post a hardcopy of your job setup please?

Also it would be interesting to know if you are working with IFS Applications or IFS Cloud version

Thanks
Martina

Hello @Makede,

It is in IFS Cloud, sorry for not mentioning.

How do I post a hardcopy? Sorry I’m quite new to this. :)

@Peter Suhajda 
you should be able to simply use Copy and Paste within the reply window to paste your hardcopy

@Makede 

Sorry I meant that I don’t know how to get the hardcopy from IFS Cloud haha. I’ve tried something, but I’m not sure if it’s correct, see it attached.

@Peter Suhajda ,  May I know what is the view are you using for this particular excel migration?

Hey @Nirogini Janstin,

Sorry for the late reply, the View Name with which this was initially set up is

CUSTOMER_INFO_ADDRESS

there is also another method added 

CUST_ORD_CUSTOMER_ADDRESS

Is there no way to check what the JSON file looks like that is created from the Excel?

I’m trying to recreate an older Excel migration that was used before, but now it cannot be used because that one had ViewNameUnique as prefix option, which apparently is not supported anymore in IFS Cloud. :(

Thank you in advance!

You can check on the google chrome’s console on the inspect for viewing the generated JSON. 

I’m using the IFS Excel Add-in, that one has DevTools as well, however, I am unable to find it there because I just don’t know where to look… Sorry for my incompetence… Do you have any suggestions where it could be? 

I only have JavaScript context: top, nothing else..

This is how far I get:

Please check on the console tab on it

Hello @Nirogini Janstin, @Makede 

After further testing, it seems like this issue comes up after adding ADDRESS_TYPE_CODE to the Method List. 

Hope this helps in identifying the issue, if you need any info in particular, please don’t hesitate to ask me. Thank you for your help!