I'm doing a trial with Celigo to test it out. One of the things I'm testing out is connecting Concur to NetSuite. However, based on my reading it looks like you can't connect to Concur test accounts. I guess not super surprising given how helpful/well-built Concur is sarcasm but how is one supposed to implement a new integration without being able to connect to a test account? Has anyone done this before, and how did you do it? I mean I could kinda see it being possible for a new implementation where prod isn't live, but if you're already up and running with an existing integration, I just don't see how I could go about implementing without making a huge mess for users, the org, and audit.

You could go from Concur prod to NetSuite sandbox, but yeah going the other way would be tricky

Hi James - so by Concur test account, do you mean a Concur sandbox environment? You cannot use the Celigo Concur <> NS templates to connect to a Concur sandbox; however if you have your api credentials (clientid/secretid) you could connect using the Custom HTTPs connector

There’s a few, but a vendor flow from Netsuite to concur is one where I’d definitely need to connect to concur test to be able to implement.

so when you pull up your Concur test instance, do you see App Center tab at the top?

Nope

yeah, there's the issue, you can't get the Celigo JWT tokens without that app center link, you'd have to get app clientid/secret created on your test environment