Hi @
@Jonas "Jones" Melgaard.
Thanks again for your reply.
It is not the Prospective vendor user request workflow that is the issue, it is the Vendor request workflow.
Repro steps:
1. prospective vendor registration request > Input vendor information and email address.
2. Invite user
3. Approve Prospective vendor User request > Collaboration user gains access and Vendor prospect (External) security role is assigned.
4. Sign in to Dynamics with the Collaboration user account.
5. Complete Registration wizard and submit.
6. Review the Vendor request and select the Vendor group.
7. Complete Vendor request workflow (currently configured to auto approve for testing purposes).
Expected result: Vendor request is completed and a Vendor record is created. Vendor user should be assigned the Vendor admin (external) security role.
Actual result: Vendor request workflow completes and is in a completed state. The Vendor request record status is @SCM:VendorRequestReview. Vendor user does not receive the Vendor admin (external) security role.
The Vendor request workflow has now modules for automated processes such as with the User request workflow.
I do not know if this is a bug, as I have tested in multiple environments. From what I have read on the Microsoft documentation, after reviewing and approving the Vendor request, a Vendor record in the VendTable should be created with the data as entered by the collaboration user in the registration wizard.
(
https://learn.microsoft.com/en-us/dynamics365/supply-chain/procurement/vendor-onboarding).
So if you might know why the Vendor request, after workflow approval gets stuck at @SCM:VendorRequestReview, it would help a lot.
I really appreciate the amount of effort you are putting in to assist me, as my back is against the wall on this one.