Team with same name in different BU

(0) Share

Report

Posted on by Robert Fleminks

Does anyone know how to work with this?

We have several business units and a team with the same name can be a part of that business unit but its not the same team.
It is important that the name is used in this case. An example: Accountmanager (team) in BU A AND Accountmanager (team) in BU B.
Dynamics gives a duplicate message.

It will not let me change the DD rule for it.
It will not let me create a workflow to perhaps fill another functional custom name field.

I thought it would be quite a normal situation but apparently it is not. Is there something I am missing?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (4)

Verified answer

Wayne Walton 13,730 on at

Like (0)

Report

IT's not normal, because Teams are frequently used to cross business units for users who need access to two at the same time. You might have to do the opposite, create a custom field with your standardized team names, and then use the out of the box field with things like "Accoutmanager - BU A" instead.

Was this reply helpful? Yes No
Verified answer

Mahadeo Matre 17,021 on at

Like (0)

Report

Hi,

I don't think so you will able to change DD on business unit name, but you should able to create workflow on Team entity.

Was this reply helpful? Yes No
Verified answer

gdas 50,091 Moderator on at

Like (0)

Report

Hi Robert,

For me instead of same team name ,you can simply create team with BU name like "Account Manager -BU Name".There is no need to do additional customization , just you need to train user accordingly.

Was this reply helpful? Yes No
Verified answer

Kokulan 18,054 on at

Like (0)

Report

When are you getting the error and can you share the detail about the error?

I tried creating two teams with same name in two different BUs and it allowed me user it in a workflow, for example, to assign record.

I also modified the lookup view to include a business unit name so that you can easily differentiate instead of having a separate field to have your unique name.

Note: A and B are the business unit names

However, you will have issues when importing data owned these teams as the import goes by display name to resolve lookups. I normally get around this by importing using my own script. You might also have issues in workflow activation of you deploy to a different environment as the activation will fail and you will have to select the team again and activate. But if you are okay with Appending the Business Unit to the team name, you will be saving a lot of time in the future.

Hope this helps.

Was this reply helpful? Yes No
Robert Fleminks on at

Like (1)

Report

It is possible to create teams with the same name in different Business Units.

The error I am getting is a mystery at this point. There is no existing record that the message is referring to as a duplicate. But it showed on the first time I was creating the teams so I assumed it was an ootb thing. My bad!

I will let the technical gang here see if they can find anything.

@kokulan: Thanks for the view tip

Was this reply helpful? Yes No