CSV to NetSuite - Single Data Loader csv to Update Line Attributes for Multiple Transaction Types
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.
-
Matthew Morrill unfortunately NetSuite doesn't allow imports to go to the generic "transaction" record type and they require each record type to be explicitly specified. Also, I feel your pain on the NetSuite native csv import lol.
That being said, I do have a pretty good solution for you. You can use data loader and then have the import step be an api call to a webhook that is sitting on another flow. On that other flow, you would then have a branch to each unique transaction type and you'd be golden. Here is an example of what I mean.
Also, here is the sample integration zip file: https://drive.google.com/file/d/101f8Xw43UMXlvC4LA2qMmRQWi1pDE5Ui/view?usp=sharing
1 -
Tyler Lamparter - This is exactly the type of solution I've been looking for. Thank you! As you can probably tell, I'm an accounting manager and sort of a novice in Celigo. Our C-level is not currently allowing any spend on 3rd-Party integration support, so I've been reading up as much as I can and 'trial & error'ing in Sandbox environments to find solutions. I'd love to become an Integrator.io pro. This middleware is very user-friendly and covers a huge amount of corporate use-cases relevant to Accounting and Financial Reporting.
I'll revert on this thread with any updates
0 -
Tyler Lamparter - I opened a new thread related to the issue I’ve run into. https://docs.celigo.com/hc/en-us/community/posts/18288432359835-Updating-Line-Items-in-NetSuite-Import-with-Error-more-than-one-match-found
I thought I properly understood the steps to use a child record field as a key field in the matching process, but apparently I haven’t set it up properly. Do you happen to see the issue?
0
Please sign in to leave a comment.
Comments
3 comments