BeyondERP.Newsletter
Menu

Page · Vendor collaboration

All contacts

A page where a vendor lists its vendor collaboration contacts, adds new contacts, and starts user requests for them.

Used by
Vendor admin (external)
Business process
Onboard new suppliers
Menu item
VendVendorContactPerson
Main table
DirPerson
Data entity
None for this page's own settings
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA page where a vendor lists its vendor collaboration contacts, adds new contacts, and starts user requests for them.
What you do hereUse this page to add vendor collaboration contacts and to request that a contact is provisioned as a user, inactivated, or given different security roles.
ExampleFor example, the vendor admin of BEAT-000001 adds a new sales contact, pairs the vendor's legal entity with BEAT, and selects Provision vendor user with the contact's work email address. A Gmail address would be refused, so the contact's company address is used.
All contacts page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Setup steps on this page

Add vendor contacts and request vendor users

Create contact persons for the vendor and request their vendor collaboration user accounts.

Steps from Microsoft

  1. Go to Vendor collaboration > Contacts > All contacts.
  2. Select New.
  3. Enter the contact person details.
  4. Select a Legal entity in my company / Legal entity in customer company pair.
  5. Select Create.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExampleTable column
Legal entity in my companyThe vendor-side legal entity the contact represents.Microsoft Learn The vendor's own company that the contact represents.ContactForParty
Legal entity in customer companyThe customer legal entity the contact works with.Microsoft Learn BEAT
Provision vendor userAction that starts a request to create a user for the contact. The email address is the sign-in: an address on a domain registered with Microsoft Entra must already be an Entra account, other domains get an invitation, and consumer addresses such as @gmail.com or @hotmail.com can't be used.Microsoft Learn sales.contact@vendor.example
Vendor collaboration access allowedSet per legal entity to give the new user access to vendor collaboration.Microsoft Learn Yes for the BEAT legal entity only.VendorPortalAccessAllowed
Inactivate vendor userAction that requests removal of a user's access, with a business justification.Microsoft Learn A contact who left the vendor.
Maintain vendor user rolesAction that requests a change to a user's security roles.Microsoft Learn Add Vendor admin (external) to a second administrator.

Common errors and fixes

MessageWhat to do
The user must have access to at least one vendor.Check that the vendor request is in Request approved status, that the user has the roles set up for the Vendor type in External roles, that the user is linked to a person who is a contact on the vendor record, and that Vendor collaboration is Active on the vendor. Then ask the vendor to sign in with their work account. Microsoft Learn

Test checklist

  1. On All contacts, select New, enter the contact details, pick a Legal entity in my company / Legal entity in customer company pair and select Create.
  2. Select Provision vendor user for the contact, enter a work email address (not a consumer address such as @gmail.com), set Vendor collaboration access allowed to Yes, assign roles and select Submit.
  3. Check that the request appears in the Vendor collaboration user requests list and that the user request workflow runs to completion.
  4. Sign in as the new user and check that the vendor's purchase orders are visible in the vendor collaboration interface.
  5. Submit Maintain vendor user roles to remove one role and check that the user loses that access after the workflow completes.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Add vendor contacts and request vendor usersCreate the contact first with the right legal entity pair, then provision the user with the person's work email addressA user can only be requested for an existing contact, and the email address becomes the sign-in through Microsoft Entra B2B.Who creates vendor contacts and user requests?Using a consumer email address (@gmail.com, @hotmail.com, @comcast.net) or a work address on an Entra domain that has no Entra account: the provisioning can't complete.Test: Provision a vendor user

Feature management and licence

Licence or add-inMicrosoft provides two external roles for vendor collaboration: Vendor admin (external), for contacts and user requests, and Vendor (external), for purchase orders, invoices, consignment inventory, RFQs and vendor information. External users created through a user request also get the SystemExternalUser role. On the live system, Vendor admin (external) maintains this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyA contact is paired per legal entity: Vendor collaboration access allowed is set for each customer legal entity the person works with, and a vendor admin can only make requests for vendor accounts they are a contact for. Microsoft Learn
Can it be undoneReversible: Contacts and user access can be changed later. A submitted Provision vendor user request sets Vendor collaboration access allowed to Yes for the vendor account and starts the user request workflow that creates the user and assigns roles. To take access away, set Vendor collaboration access allowed to No per legal entity or submit an Inactivate vendor user request. Roles change through Maintain vendor user roles. You can only delete contacts that you created. Microsoft Learn
If you change it laterSubmitting a provisioning request turns on vendor collaboration access for the vendor account and starts a workflow that creates the user and assigns roles. Microsoft Learn
Technical architect

6Technical

Menu itemVendVendorContactPerson Checked in Dynamics 365
FormVendVendorContactPerson Checked in Dynamics 365
TableDirPersonShown as “PEOPLE” in Record infoChecked in Dynamics 365
Data entitiessmmContactPersonV2EntityContacts V2 (the contact person records (ContactPerson table, linked to the vendor party through ContactForParty); user accounts are created by the user request workflow, not loaded) Microsoft data model
Who can open itPrivilegesMaintain contact person details for vendor external admin VendVendorContactPersonMaintain VendVendorContactPersonViewDutiesMaintain vendor contacts and vendor user request VendVendorUserRequestMaintainView contacts and vendor user requests VendVendorUserRequestView
1 security roleVendor admin (external) VendVendorContactExternalAdmin
Checked in Dynamics 365
Roles to set it up and use itTo set it up or change itVendor admin (external) VendVendorContactExternalAdminGive people one of these roles. On this system, 1 role can open this page.Checked in Dynamics 365
Actions on the page(Action Pane without tabs): New, Delete, Provision vendor user, Inactivate vendor user, Maintain vendor user rolesChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=VendVendorContactPerson
Data migrationsmmContactPersonV2Entity (Contacts V2): contact persons, loaded for each company.Load order: Load vendors first, then their contact persons. Vendor collaboration users are not migrated: provision them with Provision vendor user so the workflow creates the user and the Microsoft Entra account.Load first: vendors, external rolesChecked in Dynamics 365
Table definitionDirPerson columns and relations Microsoft data model
Everyone

8Sources