Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8481231
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 10, 20262026-06-10T19:30:36+00:00 2026-06-10T19:30:36+00:00

I have created a (many-to-many ) relationship between Opportunity and a custom entity. CRM

  • 0

I have created a (many-to-many) relationship between Opportunity and a custom entity.
CRM automatically breaks the relationship with a built-in table known as an “Intersect table“.

In the Plug-in Registeration Tool, I would like to add Create/Update/Delete messages on this particular table. But the problem is that it does not exist there – even many-to-many system relationships do no exist there.

People might advise me to manually break the relationship in order to be shown in the registration tool. But is there any solution to access this built-in table?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-10T19:30:38+00:00Added an answer on June 10, 2026 at 7:30 pm

    The answer unfortunately will be no. The paradigm in the CRM concerning many to many tables/relationships is that they are available for Association and Disassociation requests but not for Create, Update, or Delete requests. (In fact, there is no real Update on an intersection table – new associations are only either made (Create => Associate) or dissolved (Delete => Disassociate).)

    You can verify this in a way by looking at the AttributeMetadata for your intersection entity, and you’ll see that all the attributes in your entity have the fields ValidForUpdateAPI and ValidForCreateAPI set to false. This differs from regular entities, which have a mix of attributes that are valid for update and create calls.

    In order to solve your problem, your options are limited:

    1) Register your step against the Association message. This message, unfortunately, can’t be filtered to particular entities, so you will have to filter all association requests made in the CRM through this plugin. The IPluginExecutionContext has a property called “Relationship” in the InputParameters property bag you can use to filter out the relationship you want to develop code for.

    Relationship entityRelationship = 
        (Relationship)context.InputParameters["Relationship"];
    if (entityRelationship.SchemaName = customIntersectTable.EntityLogicalName)
    {
        EntityReference targetEntity =
            (EntityReference)context.InputParameters["Target"];
         EntityReferenceCollection relatedEntities = 
            (EntityReferenceCollection)context.InputParameters["RelatedEntities"];
        //do stuff
    }
    

    2) Make a custom intersect entity that has one to many relationships with Opportunity and your custom entity (similar to something like OpporunityProduct, which links opportunities with products). The downside here is that the GUI for this kind of thing isn’t nearly as nice for this as it is for simple intersection entities.

    Gonzalo Ruiz has a blog on this topic on MSDN as well. He pretty much says the same thing.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a many to many relationship between a Team and an Employee entity.
I created 3 tables: User User-Group Group Where I can have a many-to-many relationship.
I have created many tables using <table> tag but don't know how to get
I have the following three tables: Item Code ItemCode (many to many relationship between
I have a many to many relationship between tables A and B. Since I
I have a self-referencing many-to-many relationship between users and managers that looks like this:
I have a 1 to many relationship between two tables... say Organisation and Members
I have a simple many-to-many relationship between the User class and the Place class.
I have a standard many-to-many relationship in my database between Person and Widget. A
I have a has_many_polymorphs relationship between a Candidate and many events of various type.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.