Skip to the next paragraph if you're not interested in my rant. I regularly get an export from my FP&A department of all transaction lines with incorrect Account/Dept/Region attributes. The list includes the transactions' Internal IDs and the Line ID of the specific line with the incorrect GL impact. The list is typically ~1,000 lines, and using the csv import function in NetSuite requires that we do a separate import per transaction type and separate imports for "expense" lines vs "item" lines. This means a typical batch of imports is made up of 10 separate imports. To add to the the inconvenience, for some transaction types, certain fields are inexplicably inaccessible via the csv import dialogue, even if they are visible/accessible on the default form for that transaction.
Anyway, that's my rant - below is the format of the csv import I'm using. I'd like to create a single data loader flow in Celigo that can update multiple transaction types in a single run. The unique identifier for each transaction line item would be "Internal ID"+"Line ID"+"Trx Type".
Is there any way to achieve this? I tried setting the Import record type to "Transaction" hoping I could match on the Internal ID, Line ID, and Transaction Type, but I get an "invalid record type" error, and there are only 8 non-GL impacting fields that I can map to.
Ideally I would have the data loader branch to multiple imports depending on the "Trx Type", but alternatively if I could run a data loader that passes the same file to a list of chained flows, with each of the flows handling a different transaction type, that would be great. My least favorite option is clicking "play" 12 different times and selecting the same csv to kick of the 12 different transaction type flows.
Please sign in to leave a comment.