web
You’re offline. This is a read only version of the page.
close
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) / The type 'Solution...
Microsoft Dynamics CRM (Archived)

The type 'SolutionComponentDefinition' already contains a definition for 'EntityLogicalName'

(0) ShareShare
ReportReport
Posted on by EnriqueMdz 1,067

Hi all,

Today after generating the Entities(Early bound) file so we can use it in our plugins assembly I started to see the next issue:

"The type 'SolutionComponentDefinition' already contains a definition for 'EntityLogicalName'"

"Ambiguity between 'SolutionComponentDefinition.EntityLogicalName' and 'SolutionComponentDefinition.EntityLogicalName'"

Not sure why it appears. I tried to fix it changing the framework, adding OptionSets/Actions file and renaming the namespace but none of them worked. Also, I didn't find much info about this problem so I was wondering if someone has a workaround for this.

Thanks in advance!

*This post is locked for comments

I have the same question (0)
  • EnriqueMdz Profile Picture
    EnriqueMdz 1,067 on at

    _

  • Shwaa77 Profile Picture
    Shwaa77 175 on at

    What version of the CRM are you using and what tool are you using to generate your early bound entities?

  • EnriqueMdz Profile Picture
    EnriqueMdz 1,067 on at

    Hi Shwaa77, thanks for your answer. I'm using XRMToolbox(on the latest version) to generate the Entities.cs and our CRM is 365 online.

  • EnriqueMdz Profile Picture
    EnriqueMdz 1,067 on at

    Hi Shwaa77, thanks for your answer. I'm using XRMToolbox(on the latest version) to generate the Entities.cs and our CRM is 365 online.  

  • Community Member Profile Picture
    Community Member on at

    Experiencing the same issue using CRMSvcUtils..

  • Dynamics365 Rocker Profile Picture
    Dynamics365 Rocker 7,755 on at

    Try to use developer toolkit.

  • Community Member Profile Picture
    Community Member on at

    same issue 

  • Verified answer
    AK3800 Profile Picture
    AK3800 72 on at

    We are also seeing the issue when building entities with crmsvcutil.exe.  We are opening a case with Microsoft to get an explanation and long-term resolution, but in the mean time you can just remove the EntityLogicalName property from the code, section starting with "Public Property EntityLogicalName() As String".  This will be fine as long as you don't need to actually reference this in any code you're building.  You could also remove the entire SolutionComponentDefinition class, "Partial Public Class SolutionComponentDefinition".

  • EnriqueMdz Profile Picture
    EnriqueMdz 1,067 on at

    That's the solution we applied as well. Thanks for the answer.  

  • Community Member Profile Picture
    Community Member on at

    Worked for us aswell!

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans