• Home
  • About Us
  • Contact Us
  • Privacy Policy
  • Special Offers
Business Intelligence Info
  • Business Intelligence
    • BI News and Info
    • Big Data
    • Mobile and Cloud
    • Self-Service BI
  • CRM
    • CRM News and Info
    • InfusionSoft
    • Microsoft Dynamics CRM
    • NetSuite
    • OnContact
    • Salesforce
    • Workbooks
  • Data Mining
    • Pentaho
    • Sisense
    • Tableau
    • TIBCO Spotfire
  • Data Warehousing
    • DWH News and Info
    • IBM DB2
    • Microsoft SQL Server
    • Oracle
    • Teradata
  • Predictive Analytics
    • FICO
    • KNIME
    • Mathematica
    • Matlab
    • Minitab
    • RapidMiner
    • Revolution
    • SAP
    • SAS/SPSS
  • Humor

Back to Basics: Microsoft Dynamics 365 Terminology

June 30, 2018   Microsoft Dynamics CRM
ballpen business cell phone 796602 300x225 Back to Basics: Microsoft Dynamics 365 Terminology

If you’re new to and learning about Microsoft Dynamics 365, you have probably come across some terminology or functionality you do not fully understand. In this blog, we are going back to the basics to offer alternative explanations for a few Dynamics 365 definitions that may need further clarification.

An overview of what we will cover:

  1. Publishers and their role when you deploy solutions
  2. Connections vs Relationships
  3. Tabs vs Sections on record forms

Publishers

The main purpose of the Publisher is to identify the user who created a specific solution. Why is it important? Even out of the box Dynamics 365 has over 20 solutions, but there may be more once you start customising the system. If you have large development teams, especially from different consulting companies, Publisher will help you identify who created what solution. Also, if you buy a solution, you will know the vendor and how to contact them.

Publishers can be identified by the prefix and name. The prefix is used for custom entities and fields, while name is used for the solution. The name needs to be created by the user, while the prefix can be either system generated (new) or set up individually, but again, for the purpose of the identification, it is recommended to set up unique prefix.

062918 1757 BacktoBasic1 Back to Basics: Microsoft Dynamics 365 Terminology

Connections vs Relationships

Connections show the association between records. It is an entity and requires you to specify the connection role each time you create a connection, such as spouse, colleague, or friend. You can create Connection between virtually any entity or record.

Relationships show the association between entities. While it is also an entity, unlike Connections, Dynamics 365 does not have a view where you can see relationships. Therefore, unlike Connections, you cannot see the Relationships entity in Advanced Find. The relations can be 1:N, N:1, or N:N. Unlike Connections, Relationships are not an entity. The Relationship between entities is configured in Settings.

Please do not confuse Relationship Roles and Relationships. Relationship Roles are being deprecated and will not appear in future releases of Dynamics 365. Relationship Roles are now replaced by Connection Roles. Relationships Insight (a feature in Sales) and Product Relationships (Cross-Sell, Upsell, Substitute and Accessory) are also very different from Relationships.

Tabs vs Sections

Tabs contain Sections and Sections contain Fields. On the picture below, Details is a tab that contains several Sections – Company Profile, Description, Contact Preferences, Billing, and Shipping.

You can see the list of tabs for each form when you press Form Navigation drop-down, the button 062918 1757 BacktoBasic2 Back to Basics: Microsoft Dynamics 365 Terminology next to the record name.

062918 1757 BacktoBasic3 Back to Basics: Microsoft Dynamics 365 Terminology

Hopefully these explanations help in your Dynamics 365 journey! Make sure to subscribe to the PowerObjects blog for all information Dynamics 365.

Happy Dynamics 365’ing!

Let’s block ads! (Why?)

PowerObjects- Bringing Focus to Dynamics CRM

Back, Basics, Dynamics, Microsoft, Terminology
  • Recent Posts

    • Syncing Dynamics 365 User Permissions with SharePoint
    • solve for variable in iterator limit
    • THE UNIVERSE: A WONDROUS PLACE
    • 2020 ERP/CRM Software Blog Award Winners
    • Top 10 CRM Software Blog Posts in 2020
  • Categories

  • Archives

    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • March 2020
    • February 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    • December 2016
    • November 2016
    • October 2016
    • September 2016
    • August 2016
    • July 2016
    • June 2016
    • May 2016
    • April 2016
    • March 2016
    • February 2016
    • January 2016
    • December 2015
    • November 2015
    • October 2015
    • September 2015
    • August 2015
    • July 2015
    • June 2015
    • May 2015
    • April 2015
    • March 2015
    • February 2015
    • January 2015
    • December 2014
    • November 2014
© 2021 Business Intelligence Info
Power BI Training | G Com Solutions Limited