Christian, Great news, I'm so glad! The exact same mechanism works with the HTTP connector. You'll just store you key and password in the Encrypted section under the Advanced tab: Then in the token...
Hey Christian, So if you're seeing that error, it means that our tool has not tried to generate a refresh token. Our tool should've gotten back the response above, seen that it was an "unauthorized...
Hey Christian, That's getting close! When we're using the refresh token mechanism, in the Token field you can just enter something random like abc123. The tool will attempt to use this token, recei...
Hey Christian, To support this kind of connection, you should use the Token authentication type and configure the Refresh Token settings. Even though this says "Relative URL", if you use an absolut...
Hey Hristina, Yes, you need to use a role which has permissions in NetSuite for Transactions > Work Order > Full. Thanks,-Lucian
ADLS2 documentation: API guide, Authentication A. Register an Active Directory app You must first create an endpoint in Active Directory to sign in via OAuth 2.0: Navigate to Azure App registrati...
Hey Todd, Yes there's currently an issue where those settings aren't always loaded properly when doing previews. We will address this in a future release. To avoid this in the interim, you can add ...
I ran into this issue today and thought I'd update here. Make sure the role you're using has permission to edit work orders! The default role does not.
Awesome, I'm glad that worked!
Hey David, You've introduced an extra level in your object there. The key would now be "responsedata.OpportunityId". Again, if you look at the preview output of just the stub function you'll see th...