Just wondering if anyone managed to work with Netsuite custom transactions with Celigo.
It looks like there is a limitation on the fields shown in the Lookup Criteria to find existing records as only custom fields are shown even though there is plenty of standard fields on the custom transaction I created.
In this case I wished to have the external id as a lookup criteria
If anyone has any knowledge to share that would be appreciated!
Thanks for posting this to the community!
It looks like you're working with our Support team on this, which is great since they can look into your issue. I'll also follow that ticket.
Anitha
Was this resolved? I still don't see the ability to use standard fields for lookups on custom transactions, and when I use a custom field, the lookup doesn't find a match even though there is a match to be found.
@thevestedgroup, Apologies for the delay, we are still evaluating the issue as this is not happening in all NetSuite accounts. We are trying to find the patterns and reasons for this and will keep you/this post updated once we find a solution.
Thanks!
Hi The Vested Group Team,
We have fixed the above issue for custom transaction for style Basic, Headers only, Journal.
Could you please confirm, if you have created the custom transactions of Sale,Purchase style ?
@nithingollapally We are working with Custom Transaction types: Purchase.
We are noticing only custom fields are available in the NetSuite record import step "How can we find existing records." As a result, processing a lookup on any custom field returns error: "A mapping error occurred. More than one match for "["custcol_customfield]" - when in fact there is only one transaction with this reference number in the system.
Curious if there is a new fix or any other advised workarounds for this issue.
Is “Formula (Text)” in the drop down?
Negative!
We have also replicated internal id and various other transaction identifiers to custom fields and same error persists.
Is main line there?
No Main line option. There is a mix of line and header fields visible - only custom though.
Very strange. I’d suggest using the api to set the field then while we investigate. The easiest way to set via api is with this Chrome extension that @basvanditzhuijzen and @HenkKooiker made. You would first set some filter, save, then while you have the import open, open the extension, find where the filter is in the JSON, then update the NetSuite field id with the actual field id you want to filter on. If you are currently getting the multiple error, I suspect you may need to add mainline = T.
Thanks for the recommendation! That will be extremely useful now and in the future.
We are currently logging the integration batch via NetSuite custom record, so depending on resolution, we might write a script to update the custom transaction from the integration log record instead of processing in the celigo flow step. Current transaction volume is around 200 a day.
@praveenbasani confirmed this is currently expected behavior. We have an enhancement in the backlog to also fetch native fields, but need to prioritize it. You and other customers needing it help do just that! For now, the api route will work as this is just a UI limitation.
