This task requires the System Administrator or System Customizer security role A defined set of privileges. The security role assigned to a user determines which tasks the user can perform and which parts of the user interface the user can view. All users must be assigned at least one security role in order to access the system. or equivalent permissions. Customization tasks can be performed only while you are online. More information: Customization Permissions
A N:N relationship allows users to relate one or more records from another entity to a record of the current entity. More information: Entity Relationships
In the default solution This refers to all the components of the standard Microsoft Dynamics CRM software, plus any customizations your organization has added to it. The solution can only be customized by a system administrator or system customizer, or someone with equivalent privileges., you can create new relationships or edit existing ones for all entities that allow customization.
In an unmanaged solution For those with a required security role, an unmanaged solution has no restrictions on adding, deleting, updating, testing, importing, or exporting solution components. A solution is developed as an unmanaged solution. This differs from a managed solution, where you cannot add or remove components., you can create new relationships or edit existing ones for all entities that allow customization.
In a managed solution A complete solution that has been packaged. A managed solution has partial or full restrictions on customizing solution components. Package and export a solution as a managed solution to control customizing solution components when installed into another organization. While a managed solution may allow customizing one or more components, you cannot add or remove a component. This differs from an unmanaged solution, where you can add or remove components., you cannot create new relationships or edit existing relationships for entities. However, if the managed properties Managed properties control which customization tasks can be performed on a solution component. When you create new solution components, you can choose what level of customization you will allow for each. Managed properties are set for a solution component while the solution is unmanaged. The managed properties take effect only after the solution is packaged (exported) as a managed solution and installed in another organization. for an entity in the managed solution are set to allow customization, you can add or edit relationships to that entity in the Customization area of Microsoft Dynamics CRM.
In the Navigation Pane, click Settings.
Under Customization, click Customizations.
In the Customization area, click Customize the System.
Under Components, expand Entities, and then expand the entity you want.
Click N:N Relationships.
To edit a relationship or view the details for a relationship, select the relationship, and on the Actions toolbar, click Actions, and then click Edit.
- OR -To add a new relationship, click the New Many-to-Many Relationship button.
For a new relationship, in the Current Entity section, in the Display Option list, you can choose one of the following options:
Use Plural Name This will use the plural name of the current entity for the associated view.
Use Custom Label Enter a custom label in the Custom Label field. This label will be used for the associated view created for the other entity.
Do Not Display The other entity will not display an associated view for the current entity.
When the Use Entity Plural Name or Use Custom Label options are selected you can choose from the Display Area field to specify where the relationship label will be displayed on the form. You can also specify the Display Order to control where the label will be included within the selected display area.
In the Other Entity section, select the other entity in the Entity Name list.
Note
When you choose the Entity Name, default values will be set for the Name and Relationship Entity Name fields in the Relationship Definition section. If you change the Entity Name value before you save, these names will not change. Make sure these names are meaningful before saving.
In the Relationship Definition section, confirm the Name and the Relationship Entity Name.
These values must be unique among N:N relationships.
Click Save and Close to close the N:N Relationship form.
When your customizations are complete, publish them:
To publish customizations for only the component that you are currently editing, on the Home tab, in the Save group, click Publish.
To publish customizations for all unpublished components at one time, click Publish All Customizations.
Note
Any time you change user interface elements or implement form scripts for an entity, you must publish changes to apply them. Any customizations that change the data schema of Microsoft Dynamics CRM such as custom entities, relationships, or fields are applied immediately.