Skip to main content

Notifications

Service | Customer Service, Contact Center, Fie...
Suggested answer

Auto case creation is not taking into account the owning business units

Posted on by Microsoft Employee

We have an issues where Auto case creation is not taking into account the owning business units of Contacts/Companies.

We currently have Business Unit A owned Cases auto-creating from queues but some are linking to Business Unit B owned Contacts/Companies based on email address. This leads to crossover data, Business Unit A users seeing case resolution activities against their Companies & Contacts which should not be happening. 

Is there a way to put in place a logic where the auto case creation takes into account the owning business unit when trying to match a contact based on email. If a contact does not exist owned by Business Unit A then a new contact is created, the system must not link to simply any business unit owned record that matches?

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Auto case creation is not taking into account the owning business units

    Hi Eatsam

    The way is logically possible.
    But I can't guarantee the specific operation and its consequences, maybe you can test whether it is feasible

    Regards,

    Leah Ju

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Auto case creation is not taking into account the owning business units

    Hi Leah Ju

    Thank you for your reply.

    Do you mean adding another condition after Retrieve Sender Contact step as show in the screenshot below? Also would this logic also create the case in the correct business unit?

    pastedimage1622795079959v1.png

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Auto case creation is not taking into account the owning business units

    Hi Eatsam,

    Have you created a ‘Record Creation and Update Rule’ record, you can notice that a case record has created in the power automate, so you can add other steps in the flow to specify contact’s owning business unit.

    pastedimage1622701411096v2.png pastedimage1622701224281v1.png

    Click the link to open the flow to edit it (Following screenshot show the overview of the flow):

    pastedimage1622701528599v3.png

    Now, you need expand 'Is this email sender a contact or an account' step and 'Is email sender a contact' step.

    pastedimage1622702259720v5.png

    In the box I drew on the picture:

    1.Under Yes branch, Add one condition to specify contact's owning business unit lookup field value behind 'Retrieve sender contact' step and create new contact for the sender if owning business unit is not A.

    2.Under No branch, Add new step to retrieve sender account and specify account's owning business unit lookup field value and create new account for the sender if owning business unit is not A.

    Regards,

    Leah Ju

    Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,240 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,149 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans