web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Workflows: Explain the...
Microsoft Dynamics CRM (Archived)

Workflows: Explain the logic here

(0) ShareShare
ReportReport
Posted on by vgow 2,620

Please explain in plain english what the following means when creating CRM workflows using the 'edit assign step parameters' screen.

Assign:  Contact  to {Owning Team(Contact)}

Assign:   Contact  to {Team(Owning Team (Team))}

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    ScottDurow Profile Picture
    ScottDurow 21 on at

    Hi,

    Both of these expressions effectively will do the same - it means that the Contact will be assigned to the Team that owns the Contact that the workflow is being run on.

    The difference is that the first one is selecting the Owning Team attribute directly from the Contact, but the second is selecting the related Team via the 'Owning Team' relationship and then selecting the TeamId attribute on that team entity.

    hth,

    Scott

  • vgow Profile Picture
    vgow 2,620 on at

    Hi Scott,

    Thanks for your expert explanation previously - that certainly makes things much clearer.

    Essentially I would like to create a workflow that assigns a newly created record (account/contact) to the team of the user.

    E.g If user A creates a record then assign to user A's team, Team A, if user B creates a record assign to user B's team, Team B etc... Each user is assigned to only 1 team.

    How would you suggest I go about this? What must I select in the'edit assign step parameters' screen?

  • Suggested answer
    ScottDurow Profile Picture
    ScottDurow 21 on at

    The issue you have is that you can only pick a value from the user via a N:1 relationship - where as the the team relationship is N:N. Although you are ensuring that a user can only be a member of one team, the system allows a user to be a member of multiple teams, so it wouldn't know which one to pick - hence the restriction.

    I suggest you create a N:1 relationship between User and Team and populate that value on the users record with their primary team (You could even create a plugin to populate it when a user is added to a team). You will then be able to select the Owning User and your custom team attribute to use in the Assign Workflow Activity.

    hth,

    Scott

  • vgow Profile Picture
    vgow 2,620 on at

    Thanks for this invaluable information Scott. I will have to look into your answer a little more as Im new to CRM and havent played around with customisations much.

  • ScottDurow Profile Picture
    ScottDurow 21 on at

    Glad to be of help - can you close this thread as answered.

    Thanks!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

#2
Mark Eckert Profile Picture

Mark Eckert 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans