Team entity limitations

(0) Share

Report

Posted on by Community Member Microsoft Employee

Hello, everyone

Got an issue while working with the Team entity:

Created custom entity A, which related with Team as N:1. Created calculated field in that entity. Trying to put the formula "concat(string1, string2, new_a_teamid.Name (Name field from Team))", but the Name field doesn't populate in the list of the fields after inouting the lookup field into the formula.

I published all the changes, recreated the relation field, but the result stays the same.

So then I decided to do some workaround and created custom field B on the Team and it appeared on the list of the fields available in the formula above. So I've recreated that B field on Team as calculated, but again couldn't put the value of the Team.Name there as Name doesn't populate even on the formula of calulated field of Team entity.

Tried to do the same with the Business Rule (make custome field B equal to Name), but Name doesn't popuate on the list of fields.

Is there a way to overcome that limitation? Or JS/custom development which will copy the Team Name into some custom field is the only option?

Thanks in advance.

Categories:

Other Functionality

All responses (11)

Answers (2)

StefanS365 3,573 Most Valuable Professional on at

Like (0)

Report

RE: Team entity limitations

Super.

You might take a look at mobile.task flows for a better user experience. Select a team and then create new custom entity record. UI only though.

docs.microsoft.com/.../create-mobile-task-flow
Community Member Microsoft Employee on at

Like (0)

Report

RE: Team entity limitations

Hey, Stefan

I have another scenario - user creates the record manually by selecting 3 lookups.

Thank you for advice though, might be helpful in some other scenario.
Verified answer

StefanS365 3,573 Most Valuable Professional on at

Like (0)

Report

RE: Team entity limitations

Hi Ryzhykov,

If you create the custom entity records from the team record itself (subgrid>add new record), you are able to use the field mapping of the 1:N relationship to fill out a field with the Team name, so your calculated field will work correctly.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Team entity limitations

[quote user="Lu Hao"]

Hi Ryzhykov,

Note that System Required and Business Required are two different Field Requirements.

We create a custom field and can only set it to Business Required.

System Required is generally a key field or primary key of an entity. It does not participate in many functions of ordinary fields.

[/quote]

Got it, thank you.
Suggested answer

LuHao 40,872 on at

Like (0)

Report

RE: Team entity limitations

Hi Ryzhykov,

Note that System Required and Business Required are two different Field Requirements.

We create a custom field and can only set it to Business Required.

System Required is generally a key field or primary key of an entity. It does not participate in many functions of ordinary fields.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Team entity limitations

Hey, Lu

Not sure that is because the field is System Required. As when I create new custom field in the Team entity and define it as System Required I am able to use it in calulated field.
Verified answer

LuHao 40,872 on at

Like (0)

Report

RE: Team entity limitations

Hi Ryzhykov,

Indeed, I can't use Name field of Team in the calculated field.

This is because it is System Required.

So, as Stefan said, using workflow to update fields is the most appropriate way.

It should be noted that in the workflow's property settings, you need to separate String1, String2 and Name with spaces, add one field at a time, and add it three times. Instead of adding them all at once.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Team entity limitations

Hello, Lu

Thank you for the advice.

[quote user="Lu Hao"]

So please provide a screenshot of the field properties of new_a_teamid.Name. like this:

[/quote]

I mean that is Primary field of the Team entity. Attaching the screenshot, but it has default settings. Sorry, have interface in Russian, but the field really has default settings. If you have any particular question on the settings - please let me know< will translate it:

=============

As for the workflow - wanted to let users to edit that field on the record creation, so tried to avoid that option.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Team entity limitations

Hello, Stefan

Thank you for the suggestion. That was my decision as well.

The con is that the value of that field is not available on data entry and I wanted to let users modify that field on the record creation. But as that requirement appeared to be not crucial, decided to use the workflow.
Suggested answer

LuHao 40,872 on at

Like (0)

Report

RE: Team entity limitations

Hi Ryzhykov,

I did not encounter this problem when using the calculated field, I can successfully fill the lookup field of the parent entity into the Action.

So please provide a screenshot of the field properties of new_a_teamid.Name. like this:

In addition, if you really can't add the lookup field to the Action, you can first use the workflow to copy the value of new_a_teamid.Name to the custom field B, and then populate the field B instead of new_a_teamid.Name in the Action of the calculated field.

This custom field B is a field of entity A (not Team entity), which can be set to the value of the field of the Team entity through the workflow.