Microsoft Dynamics 365 | Integration, Dataverse...

Error regarding msdyn_teammember_sales and calculated field

(0) Share

Report

Posted on by JD_G

Hi folks,

When importing a solution to Production I get the following error (translated using google translate):

Unable to update the length of this field because a calculated field depends on it. Disconnect the two and try updating the length again.

This is regarding the msdyn_teammember_sales-app (Team Member) which is included in the solution.

What on earth could this be? Why isn't the field specified in the error message?

Thanks in advance!

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Community Member on at

Like (0)

Report

Hi JD_G,

Based on the error message, you could remove this field in your calculated field to have a try.

You could navigate to Settings-> Customizations->Customize the System, then expand entities and select the entity your field on.

Then you can sort by field type in the field view to got all calculated fields:

And then click Show Dependencies button to check which calculated field depend on this fields:

Finally, remove this field in calculated fields and then import your solution to try again.

Was this reply helpful? Yes No
JD_G 80 on at

Like (0)

Report

Thanks for your reply. It's not entirely clear to me what you mean but there are no fields in my solution, only views. So I wouldn't know where to start. As mentioned, the error message isn't giving me a specification of which field is causing the issue.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Hi JD_G,

Sorry for misunderstanding your issue. As you say, this error message is vague. You could try to check the views dependencies. Please make sure that all your required components are present on the target system or included within the solution being imported.

Was this reply helpful? Yes No
JD_G 80 on at

Like (0)

Report

So I found out that this is the message you get when accidentally putting more than 15 custom entities in the Team Members app. Kudos to Microsoft for handling this exception so well.

Was this reply helpful? Yes No