Best Of

Creating a support case, meeting with OKTA and talking with everyone will not negate the need to create the employee in NetSuite and provision them with a role.

You cannot provision a new NetSuite user via OKTA. Its not possible to do. My current client uses OKTA, and I've been through this numerous times recently. I am absolutely certain of this.

~angela

You will not be able to provision access to NetSuite directly from Okta. You will have to actually log into NetSuite and create an employee, assign them a role with SAML (roles should have this enabled if they are using OKTA).

~angela

Got it, @Ken Davies ! Thank you! Will get back to you on this.

Hi @Meherin. I agree with @MTL_MIA. For reference, you can visit SuiteAnswers ID 9769 Customer Statuses.

Thank you.

Hello @Meherin,

Good day and thank you for posting this new thread!

Hello everyone! We'd greatly appreciate your support in this matter.

Hi @Dext3r ,

Glad to have you with us today. Thank you for creating this thread. 😊

Hi, Everyone! You are welcome to join the conversation and share your insights.

Hi @Dext3r ,

Could you confirm the Internal ID of the Next Approver on this transaction and if it's only happening on this transaction/on this particular approver or is it happening on all approval transactions?

Thanks,
Grace

Hi @Dext3r ,

Just following up in case you've missed it:

Thanks

Hi @Dext3r ,

I apologise for the delay and upon checking on this and consulting with our team, I will have to recommend for you to create a case with our support team because this condition is specific and have to be tested with you or technical support's internal QA environment:

As this is not reproducible on our test account with the multiple states (with conditions) on your workflow, please open a case for better support.

And once you have this case solved, please feel free to share your solution on this thread for our other community members to know whether or not it's time to create a case for their concern as well.

Thanks,
Grace

Hi @KevinWong, yes that's right so that the saved search would be able to pull SuiteTax related fields from the record.