Skip to main content

Notifications

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) / Error trying to set th...
Microsoft Dynamics CRM (Archived)

Error trying to set the value of a "Two Options" choice Calculated field

(0) ShareShare
ReportReport
Posted on by Community Member

I have created a “Two Options” (Yes/No) field on a custom entity, and want this to be a Calculated field instead of the default “Simple” type.  When I edit the Calculated field to set the values of the new field, I am receiving the error “The new_isexistingpartner field has an invalid XAML formula definition”.  If I set the type of field to an Option Set I can use it, but I need to create a new Boolean set for Yes/No, and I don’t think I should have to do that.  This is about as simple as it gets (setting a Yes/No option based on the value of another field), but it doesn’t seem to be working for me.

Any input on this issue is appreciated!  Thanks...

 Field Definition:

7571.Field.png

Formula Definition:

Formula.png

Exception:

7824.Error.png

*This post is locked for comments

  • Andrew Gallery Profile Picture
    Andrew Gallery on at
    RE: Error trying to set the value of a "Two Options" choice Calculated field

    We've just encountered this exact same issue. The issue occurs on a custom entity, even when deleting and re-creating the calculated field. It also occurs on existing entity, so looks like a product bug.

    The workaround we used was to define an Option Set with Yes/No values instead of a "Two Option" field - not ideal but does the job.

  • Suggested answer
    Aric Levin Profile Picture
    Aric Levin 30,188 Moderator on at
    RE: Error trying to set the value of a "Two Options" choice Calculated field

    I am not sure if this will help, but take a look at the following:

    abedhaniyah.blogspot.com/.../issue-resolution-field-formula-rollup.html

    It is possible that you have an issue with the length of the field (this is actually the relationship name).

    Try delete the field, and create a new one, and just enter a very short name "new_exp"

    I am not sure if this is the issue, but worth a try. Possibly Microsoft will have a resolution for it.

    Hope this helps.

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

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,575 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,493 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans