Hi, does anyone have a sample Celigo mapping to cr...
# integrations
s
Hi, does anyone have a sample Celigo mapping to create a 'Parent' inventory item / inventory part? I have a flow that creates an inventory item fine but when I set the Matrix Type to "PARENT" it fails with "Failed to create, update/transform record because Cannot find function getSelectOptions in object Field." Got a bit stuck with this one, all help gratefully received
t
Try to map in "use dynamic mode" and set to true and move that to the top of your mappings
s
Thanks @Tyler Lamparter - gave that a try, but still throwing the same error.
t
Try to remake the import step using SuiteApp 1.0. It's under advanced settings when you initially create the import step
Also maybe reorder your mappings to be in order of how you would do it in the UI
s
The SuiteApp 1.0 is greyed out. Do I need to install a bundle for that?
t
When I've seen that error before, it's related to SuiteApp 2.0 and using the use dynamic mode with your fields order fixes it
You can't change after making the import step, so you have to remake and select it prior to saving
s
OK - I've tried dynamic / reorder and the error disappeared. Amazing - huge thank you. It is quite slow - would Suitescript 1.0 speed it up at all?
Also, I couldn't get it to populate the supplier or price - are there any tricks to that you're aware of? (Doesn't throw an error but doesn't populate the fields in NS)
t
I would check your netsuite concurrency connection settings in celigo and increase it if it's slow. Most likely it is defaulted to blank which equals 1. It wouldn't be any faster on 1.0
Can you debug the connection and show what IO is sending to netsuite?
s
Thanks @Tyler Lamparter - I moved it to suitescript 1.0 and re-ordered the import somewhat and it is now nice and fast. It also imports the supplier and price information now. So, all good. I do have a follow-up question. I can now create the parent items. I'd like to create the children items next. Do you know if there is anyway to have another import step in a data loader to create the child items. Alternatively, is there any way I can leverage the 'file picker' in data loader (or something like that) to allow users to load a file from their local machine to create items in Netsuite? Thanks again!
t
Do you happen to have the old version of the flow prior to changing to SuiteApp 1.0? I want to send it internally to engineering so we can compare the differences. Also, data loader only allows for 1 import step. You would need to move this to S3 buckets or google drive, or ftp server as the source to then have multiple steps to make subsequent child items
s
Hi @Tyler Lamparter - yes, here's the SuiteApp 2.0 version with the original mapping. (I assume this is OK for you - I also have a word doc with screenshots if not)
I was hoping to avoid asking the users to transfer to an ftp server. Been down that route before... I might try sharepoint as we're an Office 365 house. (I don't suppose it's possible to call another flow with the file info that has already loaded ?)
t
Can you send the working suiteapp 1 as well and a sample file they can use to load?
Also unfortunately not. The data loader is sort of locked down given it's free to use
s
Yes, sure - will be later tonight (my time)
Hi - SuiteApp 1 and sample file
👍 1
Hi @Tyler Lamparter - hope that's useful. To get round the data loader limitation, I used dl to load the data into a custom record and then read that data into a flow to create the items. Slightly convoluted but seems to do the job. Last question, I hope! For the child items I'd ideally like to iterate over the import that creates the child items in Netsuite. e.g. if the size range was S, M, L it would be called 3 times, once for each size and if XS, S, M, L, XL 5 times etc. Is that possible in Celigo? (I have seen something similar where they put the flow in a myAPI and then called the flow for each size. But wondering if there might be an easier approach?
t
@Stewart I'm not sure I fully follow you. Are you familiar with the one-to-many setting on import steps? Could you group your initial data by SKU, then you would have 1 record per sku with each variant