Business rule core function is to enable business analysts and power users to configure Microsoft Dynamics entity forms and perform actions without writing a single line of client-side code (JavaScript). Business Rules can be set up using the graphical interface, and in the back end Dynamics 365 automatically generates the client-script to perform the configured action. The automatically generated code is not available to users, so from their perspective, there are only point-and-click configurations.Business rule was introduced by Microsoft in CRM 2013. Dynamics 365 business rule UI will be different from previous version. In the UI component that can be dragged and dropped in the design area.

As we said business rule will perform the action like client side code. The action can be run only when the form loads and when field values change. They do not run when a record is saved, unless the scope for the rule is set at an entity level.

2

Actions Used In Business Rule:

  • Show error message: This action will display an error message if the specified condition is not met. For example, if the data entered in a field does not meet certain validation criteria then Business Rules can be configured to display an error message to the user and restrict them from saving invalid data in CRM.
  • Set field value: This action can be consumed to set a field’s value based on the condition. International business could use the country field value to automatically fill the country’s dialing code.
  • Set business required: By choosing this action, the mandatory field can be marked as non-mandatory and vice versa.
  • Set visibility: This action can hide and show fields on the entity forms. It enables the power users or customizers to change the visibility of the fields dynamically based on the specified condition.
  • Lock or unlock field: This action can be consumed to lock or unlock (enable or disable) fields dynamically. Unlocked or Enabled fields are editable and Locked or Disabled fields are read-only.
  • Set default value: Setting a default value should be used when you want a field to appear with a set value on load. Being able to set a default value is a standard feature for option sets. Using the Set default value feature allows you to set default values for numeric, text, and lookup fields as well. Set your condition and under actions select Set default value.
  • Recommendation: This feature is added in dynamics 365 previous version will not have this feature.With this action, an icon will be added next to a field that will provide some information and show a message that the user can take action upon.  During definition of the Show Recommendation action, you provide the message to display along with the action that will occur if the user clicks on “Accept” on the recommendation.Recommendation is an action added in Business rules in addition to existing actions like: set business required, clear field, set value, set visible etc.

Flow Used In Business Rule:

  • Condition: This is used for checking condition to execute the action. We can create multi branching condition. Up to 10 conditional branch can be used for single business rule.

Scope Of Business Rule:

  • Specific Form: Business rule will only work for selected form.
  • All forms: Business rule will be applied to all the Main forms and the Quick Create form, as long as the form includes all the fields referenced by the rule.
  • Entity:Business rule will work in all form and server side. Server side means while importing the data business rule will work.

1

Minimap: Minimap can be used to navigate to the components of the business rule.It will show miniature model of the business rule.

3

Business Rule (Text View): This will automatically build the code for the business rule based on the steps added. Text view is a quick and easy way to read through your business rule.

4

Snapshot: Snapshot is a great way to quickly take a picture of your Business Rule to review.Once the snapshot is clicked our business rule will be downloaded as image file with png format.\ to our lock system.

5

Validate:Validate feature will help you validate your business rule against any errors prior to activating the Business Rule and show where the error is occurred.If the business rule is success then success message will be displayed.

6

7

 

 

How To Create Business Rule:

To create user should have  System Administrator or System Customizer security role or equivalent permissions.

  • Go to Settings>Customizations.
  • Click Customize the System.
  • Open the entity you want to create the business rule for (for example, open the Account entity), and then double-click Business Rules.

8

  • Click NEW,this will take us to new business rule design window.By default one condition will be appear in the screen. business rule will not get created without even single condition. Based on the condition one or more action will be executed.

9

  • Add name in the business rule name column.
  • Add description about the business rule in description column.
  • We can add more than on condition.
  • Drag the Condition component from the Components tab to a plus sign in the designer.

10

  • To set properties for condition by clicking the condition components in designer window properties tab will be visible on right side of the window and we can set conditions.
  • We can add additional clause to the condition,click New in the Properties tab to create a new rule, and then set the properties for that rule. In the Rule Logic field, you can specify whether to add the new rule as an AND or an OR.
  • Once the properties is set,user has to click apply button or else the properties wont set.
  • Adding Actions,
  • Drag one of the action click components from the Components tab to a plus sign next to Condition component. Place the action next to the plus mark if the condition is true.If condition is false place the action next to the ‘X’ mark.

13

  • Am Adding recommendation:
    • In this example if account name contains data and if city equal to chennai set state equal to tamilnadu. This will show message “if city is equal to chennai” if user think it match then click apply state field value automatically get filled.

This feature is available only in dynamics 365.

14

  • To validate the business rule, click Validate on the action bar.
  • To save the business rule, click Save on the action bar.
  • To activate the business rule, click the activate button.

15

16

Limitation:

  • Business rules work only with fields. If you need to interact with other visible elements, such as tabs and sections, within the form you need use form scripts.
  • When you set a field value by using a business rule, any OnChange event handlers for that field will not run. This is to reduce the potential for a circular reference, which could lead to an infinite loop.
  • If a business rule references a field that is not present on a form, the rule will simply not run. There will be no error message.
  • Whole Number fields that use the formats for TimeZone, Duration, or Language will not appear in the rule editor for the conditions or actions, so they cannot be used with business rules.
  • You can’t add more than ten if-else conditions in a business rule.
  • For Microsoft Dynamics 365 for tablets, the definition of the business rules are downloaded and cached when Dynamics 365 for tablets opens. Changes made to business rules are not applied until Dynamics 365 for tablets is closed and re-opened.
  • When you set the value of a lookup field, the text of the primary field value that is set in the form will always match the text that is visible in the rule definition. If the text representing the primary field value of the record you are setting in the lookup changes, the value set by your rule will continue to use the text portion of the primary field value defined by the rule. To fix this, update the rule definition to use the current primary name field value.

 Charts In Dynamics 365,Custom Colors For Charts

Charts is basically a graphical representation of data from multiple record of an entity,charts are a very useful way to display data for quick, high-level, visual analysis.  They are built from the query on the data.When the query is updated for the data,the associated charts also get updated automatically.

  • Easily drill down to see the records in the chart.
  • Customize your dashboards with the charts.
  • Customize by pie, bar, line, funnel charts and more.
  • Present multi-series charts.
  • Save personal charts that you create and share with others.

12

Dynamics 365 includes system charts (built-in charts that come with Dynamics 365) and user charts (created by users). In earlier versions of the product admins and customizers could delete or deactivate system charts. Starting with CRM 2015 SP1, system charts can’t be deleted or deactivated, however.

There Two Types Of Charts:

System Charts: User with System Administrator or System Customizer role only can create system charts.By Default system charts are visible to all user.User access can only be configured to all or none.System chart cannot be shared.

User Charts: User charts can created by user who has user level access. These charts can be seen only by the user who created the chart or whom these charts are shared with.Charts can be shared only if the owner has share privilege.

Charts In Microsoft Dynamics 365 Is Classified Into:

  • Single-series charts: Charts that display data with a series (y) value mapped to a category (x) value.
  • Multi-series charts: Charts that display data with multiple series values mapped to a single category value. Multi-series charts include stacked column charts, which vertically display the contribution of each series to a total across categories, and 100% stacked column charts, which compare the percentage that each series contributes to a total across categories. You can combine different compatible chart types in multi-series charts.

Multi-category charts can be created through the web application or by modifying the XML strings described here.

Variants Of Chart:

There are nine variants of chart available in dynamics 365.

Column Chart:

A column chart displays a series as a set of vertical bars that are grouped by category. Column charts are useful for showing data changes over a period of time or for illustrating comparisons among items. The plain column chart is closely related to the bar chart, which displays series as sets of horizontal bars, and the range column chart, which displays series as sets of vertical bars with varying beginning and end points.

1

Bar Chart:

A bar chart displays series as sets of horizontal bars. The plain bar chart is closely related to the column chart, which displays series as sets of vertical bars, and the range bar chart, which displays series as sets of horizontal bars with varying beginning and end points.The bar chart is the only chart type that displays data horizontally.

2

Area Chart:

An area chart displays a series as a set of points connected by a line, with all the area filled in below the line.

3

Line Chart:

A line chart displays a series as a set of points connected by a single line. Line charts are used to representing large amounts of data that occur over a continuous period of time.

4

Pie Chart:

Pie charts display data as a proportion of the whole. Pie charts are most commonly used to make comparisons between groups.

5

Funnel Chart:

Funnel charts show values across multiple stages in a process.Data in each of these phases is represented as different portions of 100% (the whole).

6

Multi-Series Chart:

When multiple series are present on a chart, you must determine the best way to compare the series. You can use a stacked chart to show relative proportions of each series. If you are comparing only two series that share a common category (x) axis, use the secondary axis. This is useful when showing two related series of data, for example, price and volume, or income and tax.

7

Comparison Chart (Stacked Chart):

Columns of data plotted to the same Value (Y) axis will be stacked in a single column when the stacked column subtype is selected. To achieve a combination of stacked and unstacked columns that appear side by side, both data manipulation and the use of a second Value (Y) axis is required.

8

Comparison Chart (100% Stacked Chart):

The 100% stacked bar chart is great to display the relative amounts within a series.However, for some reason the 100% stacked bar chart comes without labels to indicate what the percentage is for each group.

9

Creating Chart:

  • Navigate to Settings > Customizations. Choose Customize the System.

Capture

  • Expand the entities from the default solution.Choose entity where we have to create chart.

10

  • Click new button from chart

11

  • Select the view according to that data will be loaded in the chart.
  • Enter the name for the chart
  • In the Legend Entries (Series) area, select the field you want to chart and choose the aggregate.
  • Select your label for the horizontal axis

Save the chart and publish.Then Charts can be used in dashboard.

Charts can be import and export.

Changing Custom Color In Chart:

In dynamics 365 charts comes with basic colors and all the charts will comes with these colors only. We can change these colors according to our custom colors to show more presentable in the dashboard.

  • Navigate to Settings > Customizations. Choose Customize the System.
  • Expand the entities from the default solution.Choose entity where we have to change the color of chart.
  • Select the entity one we have to change the color of the chart.
  • Then click more option from the menu and click export chart.

20

  • Once the export button is clicked save option window will open. Save the xml file into desired location.

21

  • Open the save xml file.We can change the color under PaletteCustomColor property. Usually chart colors are mentioned in  Color code . Spot the PaletteCustomColor in the xml file to change the color.The supported format for color in chart are
    • RGB Decimal (example: 97, 142, 206)
    • RGB HEX (example: #4169E1)
    • Named colors (example: Blue)
    • ARGB (127, 97, 142, 206)

22

  • It always easy to use name of the colors in PaletteCustomColor property.Each color codes are separated with semi colon. I have changed color to brown in PaletteCustomColor property using name of the color the save the xml file. Then import the file back to the same entity using same step how we exported the file.

23

24

  • After clicking the import button it will ask whether to replace the existing chart or duplicate the chart. I have chosen replace and import the chart.

25

  • Once the chart is imported kindly publish and see the changes.

Before                                                        After

 

Dynamics 365 Personal,System and Public View

View is a list of record showed in dynamics 365 application for specific entity.A drop-down list of views is frequently displayed in the application so that people have options for different views of entity data.The records that are visible in individual views are displayed in a list, sometimes called a grid, which frequently provides options so that people can change the default sorting, column widths, and filters to more easily see the data that’s important to them.

Types Of View :

There are three types of view in dynamics 365

Personal views : 

Personal view is for individual user or a set of users who wants to view there own required view.User who has at least User level access to actions for the Saved View entity can also create personal views.System administrator can modify the access level for each action in the security role to control the depth for the user.User can create personal views by saving a query that you define by using Advanced Find or by using the Save Filters as New Views and Save Filters to Current View options in the list of views. While user can create a new personal view based on a system or public view, user cannot create a system or public view based on a personal view.Personal view cannot be included in solution.

Creating Personal View:

  • Navigate to the entity where we want to create personal view.

1

  • Click the drop down arrow of the current view and select Create Personal View in the drop down menu.

2

  • Once create personal view is clicked it will take us to advance find screen.

3

  1. Look for: This drop down should populate with the entity you are in
  2. Use Saved View: [new] –this will create a brand new view, the rest of the dropdown will populate with options to copy other system or personal views you have access to (this is in case you like another view, want to copy the filter settings, but customize it yourself)
  3. Select: This allows you to set additional filter criteria
  4. Saved views: This allows you to see all of your personal views, allows you to share your personal views with others, and allows you to delete any personal views you no longer use.
  5. Results: This section shows a preview of the view you have created
  6. New: Opens a new window to create a new view
  7. Save: Saves your view
  8. Save As: Prompts you to set the title and description for your view
  9. Edit Columns: This allows you to change the order of the columns, add or remove columns, and customize sorting (see aforementioned instructions)
  10. Edit Properties: This allows you to set the title and description for your view
  11. Clear: Removes all filter criteria
  12. Group AND & Group OR: These serve as functions to help with the filtered criteria
  13. Details: This allows you to edit you filter data once it has been saved
  14. Download FetchXML: This is utilized for reporting instead of SSRS reports from SQL
  • Once the personal view is ready for user requirement. Click SAVE AS and name the new personal view.

4

5

  • Now personal view will be visible under My view menu. Only user who create can see the view until user share with other user or team.

6

Edit Personal View:

  • User can edit the personal view by going to specific entity and click advance find option.

7

  • This will take us to advance find screen and select the personal view that has to be modified from the use saved view

8

  • Then Click DETAIL  button to modify the query.

9

  • Once the modification is done save the view and see the result.

 

System View:

System view are special view it comes with the application, which exist for system entities and system view are created automatically  when we create custom entity.System administrator or system customizer can only edit the system view.

In earlier versions of the product you could delete or deactivate system views. Starting with CRM 2015 SP1, you can’t delete or deactivate system views.

 

These views are system generated view while installation of application and while creating custom entity. These views are not shown in the view selector and you can’t use them in sublists in a form or as a list in a dashboard. You cannot delete or deactivate these views.System views are owned by the organization so that everyone can see them.If you have a sub-grid of another entity on your form and you want to select a particular view to show in that sub-grid, you must use a system view.System View cannot be shared with other user or team members.

Creating System View:

  • Navigate to Settings > Customizations > Customize the System.

Capture

  • Expand the entities from the default solution.

10

  • Select the entity where system view to be create or edited. Now Click new button in the view screen.

11

  • You need to name the system view to be created.

12

  • Select a column you want to act upon and then utilize one of the functions listed under Common Task

13

  • Common Task Detail:
    • Arrows: This allows you to change the order of the column
    • View properties: This allows you to change the title of the view and add a description
    • Edit Filter Criteria: This allows you to filter data to specific record types
    • Configure Sorting: This allows you to configure how the data is sorted (ascending or descending)
    • Add Columns: This allows you to add additional columns
    • Change Properties: This function allows you to change the properties of a column (change the pixel – length size – of a column) and view the properties of the record
    • Remove: This allows you to remove a column

14

  • Once the system view is ready save and publish the system view.

15

Editing System View: 

  • Navigate to Settings > Customizations > Customize the System.

Capture

  • Expand the entities from the default solution.

10

  • Select the system view you want to edit and double click the view.Now you can add Columns , remove columns, edit filter , change properties

16

  • Once the editing is done save the changes and publish the view.

 

Public views:

Public views are general purpose views that user can customize as user requirement fit. These views are available in the view selector and user can use them in sub-grids in a form or as a list in a dashboard. Some public views exist by default for system entities and for any custom entity. You can create custom public views. You can delete any custom public views you create in an unmanaged solution. You cannot delete any system-defined public views. Custom public views added by importing a managed solution may have managed properties set that can prevent them from being deleted, except by uninstalling the managed solution.

For example, when you create a new custom entity, it will have the following combination of public and system views.

Name

Type

Active<entity plural name>

Public

Inactive<entity plural name>

Public

Quick Find Active<entity plural name>

Quick Find

<entity name>Advanced Find View

Advanced Find

<entity name>Associated View

Associated

<entity name>Lookup View

Lookup

17

All the public view can be modified by system administrator or system customizer. User can create custom public views. User can delete any custom public views you create in an unmanaged solution. User cannot delete any system-defined public views. Custom public views added by importing a managed solution may have managed properties set that can prevent them from being deleted, except by uninstalling the managed solution.

 Dynamics 365 Main Form,Mobile Form,Quick Create Form,Quick View Form

In Microsoft Dynamics 365, forms provide the user interface that people will use to interact with the data they need to do their work. It is important that the forms people use are designed to allow them to find or enter the information they need efficiently.Forms provide the user interface (UI) that people use to create, view, or edit entity records. Use the form designer in the customization tools to create and edit entity forms.

To view the forms:

Setting – > Customization – > Customize the system – > Select the entity – > Select form

or

Setting – > – > Customization – > Solution – > Select the solution – > Select the entity – > Select form.

1

Types Of Form:

Main Form :

This is used in the web application, Dynamics 365 for Outlook and Dynamics 365 for tablets.These forms provide the main user interface for interacting with entity data. The main form is used by every client except Microsoft Dynamics CRM for phones.This form can be used as portal form also.Security role can be assigned to main form.

Main form is important form where user will view, edit, give the input to store the value. In this form major design,customization and configuration will be done according to business needs.

2

  • Body. The body of the form is where all the editable information is stored. Users have the option of scrolling down the form or using the tabs.
  • Header. The form header is the part of the form that is visible even as the user scrolls down or moves across tabs.
  • Footer. The footer is similar to the header, but shown at the bottom.
  • Navigation. Form navigation includes links to related records, web resources or external links.

To Create New Main Form:

  1. Settings > Customizations > Choose Customize the System.
  2. Expand the Entities node and select the entity you want to create a new main form
  3. Expand the entity and select the Forms node.
  4. Choose New and select Main Form.

To Edit Main Form:

Double-click or tap any form with a form type of Main.

Changes the form design in any following way:

  • Add a tab to a form
  • Add a section to a form
  • Add a field to a form
  • Add or edit a form IFRAME
  • Add or edit a sub-grid on a form
  • Add or edit a form web resource
  • Add Knowledge base Search
  • Quick View Form
  • Add Spacer between fields
  • Add Timer control
  • Add Bing Map
  • Add or edit form navigation for related entities

4

 

  • Edit form headers and footers
  • Remove a tab section field or IFRAME
  • Enable or disable the Form Assistant
  • Edit the properties for parts of the form
    • Edit form properties
    • Edit form field properties
    • Edit tab properties
    • Edit section properties
  • Add event scripts, as needed.
  • Determine which security roles will be able to see the form.Assign security role to a form.
  • Add Business rule

5

When we finish editing the form, click Save As, enter a name for the form, and then click OK.To see the changes we have done we need to publish it.

Mobile Form:

This is used  for the Microsoft Dynamics 365 for phones pages. This simplified form is designed to be used for mobile devices.Microsoft Dynamics CRM for phones uses a form that is optimized for use with a phone.

This form used only for mobile page design.In this form we cannot do much customization.While editing the form, you select which fields you want to display the order in which you want them to appear. You can make certain fields read-only, but can’t use form scripting in the CRM for phones express forms.

3

To Create Mobile Form:

  1.  Settings > Customizations > Choose Customize the System.
  2. Expand the Entities node and select the entity you want to create a new mobile form
  3. Expand the entity and select the Forms node.
  4. Choose New and select Mobile – Express
  5. If you don’t see this option, the entity is not enabled for CRM for phones express. You can change this for some entities.
    1. Settings > Customizations > Choose Customize the System.
    2. In Entity Information page we can see Outlook & Mobile section.
    3. Click Enable for phone express and enable for mobile.
    4. save the change and publish.
  6. Save the form and publish.

6

To Edit Mobile Form:

To edit existing mobile form Double-click or tap any form with a form type of Mobile Express in the expanded entity.

  • Choose what fields to include in the form.
  • Choose where to position the fields.
  • Decide whether to make certain fields read-only.
  • Publish customizations when changes are done.

By default, all fields that are business or system required are included in the form and can’t be removed.

Quick Create :

This form provide a basic form optimized for creating new records. Quick create forms appear when you click the plus(+) button in the navigation bar or when you choose + New when creating a new record from a lookup or sub-grid. With quick create forms, you can have a streamlined data entry experience with full support for logic defined by form scripts and business rules.The mobile apps use quick create forms for creating new records.This feature was introduced in Microsoft Dynamics 2013.

11

Main feature of quick create form is form will opens without overtaking the current window. This save lots of time without going to another entities.Only some entities will have allow quick create by default or else we need to enable quick create option.

16

In above example after clicking the new button from test look up field.New Quick Create Form will slid down from the top the screen.This helps us from swapping between screens.

9

To Enable Allow Quick Create For Entity :

  1. Settings > Customizations > Choose Customize the System.
  2. In Entity Information page we can see data services section.
  3. By Clicking allow quick create we can enable and disable the option.
  4. Save the change and publish.

7

To Create Quick Create Form:

  •  Settings > Customizations > Choose Customize the System.
  • Expand the Entities node and select the entity you want to create a new quick create form.
  • Expand the entity and select the Forms node.
  • Choose New and select Quick Create Form.
  • Drag any fields from the Field Explorer into the sections in the form.
  • Save the form and publish.

To Edit Quick Create Form:

To edit existing quick create form Double-click or tap any form with a form type of quick create in the expanded entity.

Controls Cannot Be Added To Quick Create Forms:

  • Sub-grids
  • Quick View Forms
  • Web resources
  • IFRAMEs
  • Notes
  • Bing Maps

Quick View :

In Microsoft Dynamics 365, a quick view form can be added to another form as a quick view control. It provides a template to view information about a related entity record within a form for another entity record. This means you do not need to navigate to a different record to see the information you need to do your work.Data in quick view controls cannot be edited and quick view forms do not support form scripts.Security roles cannot be assigned to quick view forms and they cannot be activated or deactivated.

Quick view controls are associated with a lookup field that is included in a form. If the lookup field value is not set, the quick view control will not be visible.

15

In the above screen shoot Test Quick View is Quick View Form.

 

To Create Quick View Form:

  • Settings > Customizations > Choose Customize the System.
  • Expand the Entities node and select the entity you want to create a new Quick View form.
  • Expand the entity and select the Forms node.
  • Choose New and select Quick View Form.
  • Drag any fields from the Field Explorer into the sections in the form.
  • Save And Publish.

To Edit Quick Create Form:

To edit existing quick view form Double-click or tap any form with a form type of quick view in the expanded entity.

How To Add Quick View Form:

Open the main which should have quick view form.

Click insert – > select Quick View Form.

12

Then Quick View Form properties page will be opened.

13

Name : Required: The unique name for the quick view form that is used when referencing it in scripts.

Label : Required: A label to display for the quick view form.

Display label on the Form : Displays the label on the form.

Lookup Field : Choose one of the lookup fields included in the form.

Related entity : This value depends on the Lookup Field you choose. It is usually the primary entity for the 1:N entity relationship for the lookup.

Quick View Form : If the Related entity has any quick view forms you can select them here. Otherwise, click New to create one.

After All details Filled click OK and Quick View Form Will be displayed in the main form.

14

Then Save the form and publish.

10

Now we can test the Quick View Form.

 Dynamics 365 Data Types,Calculated Field and Rollup Field

Datatype is very important for designing the application and storing correct data in the database.A data type, in programming, is a classification that specifies which type of value a variable has and what type of mathematical, relational or logical operations can be applied to it without causing an error.Each data type will have different format we can use these format based on our business logic.

1

 

Single Line of Text –

  • Single line of text is a string attribute.The length for string can be defined from 1 to 4000 characters.This datatype has different format option.

Format:

  • Email – The text provides a mailto link to open the user’s email application.
  • Text – This option simply displays text.
  • Text Area – This format option can be used to display multiple lines of text. But with a limit of 4000 characters, the Multiple Lines of Text field is a better choice if large amounts of text are expected.
  • URL – The text provides a hyperlink to open the page specified. Any text that does not begin with a valid protocol will have “http://” prepended to it.
    Only HTTP, HTTPS, FTP , FTPS, ONENOTE and TEL protocols are allowed in this field.
  • Ticker Symbol – For most languages, the text will be enabled as a link to open the MSN Money website to show details about the stock price represented by the ticker symbol.
  • Phone – In the web application, fields will be click-enabled to initiate calls using either Skype or Lync if a client for either is installed on your computer. The telephony provider choice is at the bottom of the General tab of System Settings.

Option Set 

This data type is drop down or pick list field.A user is allowed to select only one option from given values.A blank values is also acceptable and default value can also be defined.Each options has value and label.

There are two types of option set :

  • Global – Created in solution and can be refered to any local optionSet.
  • Local – Specify to entity only.

Two Options 

Two option is boolean value.Yes/No is default option, can be renamed as needs and can set default value to the field.This datatype will have O(No) and 1(Yes).Fields can be displayed as pick list, radio buttons or check box this can be customized after field is placed in the form.

Image 

This datatype stores image of the entity.Each entity that supports images can have one image field. When an entity has an image field, it can be configured to display the image for the record in the application.There are 24 system entities where an image field is
available.

Supported Format:

  • BMP, GIF, JPG, JPEG,PNG, TIFF, TIF

Whole Number –

This datatype stores only integer value from  -2,147,483,648 to 2,147,483,647,the range can be set according to the business logic.This datatype has different format option.

Formats:

  • None: This is the default integer format.
  • Duration: This option provides a drop-down field with value options for minutes, hours, and days; this option should be only used when we want to represent time: durationTime zone.
  • Language: This option can be used to select language options based on the language packs installed.
  • Time Zone: This option displays a select list of time zones such as (GMT-12:00) International Date Line West and (GMT-08:00) Pacific Time (US & Canada). Each of these zones is stored as a number.

Floating Point Number –

This datatype is used store fraction value from  -100000000000 to +100000000000, range can be changed with decimal points upto 5.Floating point numbers store an extremely close approximation of the value.Use floating point numbers when you store data that represents fractions or values that you will typically query comparing to another value using greater than or less than operators.

Decimal Number –

This datatype is used store decimal numbers from  -100000000000 to +100000000000, range can be changed with decimal points upto 10.Decimal numbers are stored in the database exactly as specified.Use decimals when you need to provide reports that require very accurate calculations, or if you typically use queries that look for values that are equal or not equal to another value.

Currency 

This datatype is used to store money value from -922,337,203,685,477 to 922,337,203,685,477 with decimal points upto 4. Based on your currency settings, the correct currency symbol is also displayed such as the dollar sign or euro symbol.

Multiple Lines of Text –

Multiple Lines of Text is a string attribute. It is similar to Single Line of Text but can store more characters upto 1,048,576.You can set a maximum length to less than this. When you add this field to the form you can specify the size of the field.

Date and Time –

This datatype is used to store date and time data.You can choose to have both the Date and Time displayed or only the Date portion.Data values automatically converted to the date and time format selected in the user’s personal settings.Value are stored as Coordinated Universal Time (UTC).This datatype has different format option.

Format:

  • Date Only
  • Date Time

Lookup –

This datatype represents a link to another entity.When you create a new lookup field you are creating a new Many-to-One (N:1) entity relationship between the entity you’re working with and the Target Record Type defined for the lookup. But all custom lookups can only allow for a reference to a single record for a single target record type.

Not every lookup behaves this way. There are several different types of system lookups

  • Simple – Allows for a single reference to a specific entity. All custom lookups are this type.
  • Customer – Allows for a single reference to either an account or a contact record. These lookups are available for the Opportunity, Case, Quote, Order, and Invoice entities. These entities also have separate Account and Contact lookups that you can use if your customers are always one type. Or you can include both instead of using the Customer lookup.
  • Owner – Allows for a single reference to either a team or a user record. All team or user-owned entities have one of these.
  • PartyList – Allows for multiple references to multiple entities. These lookups are found on the Email entity To and Cc fields. They’re also used in the Phone and Appointment entities.
  • Regarding – Allows for a single reference to multiple entities. These lookups are found in the regarding field used in activities.

Customer 

A lookup datatype that you can use to specify a customer, which can be an account or contact.

This feature was introduced in Dynamics CRM 2016 Service Pack 1 On-Premises and Dynamics CRM Online 2016 Update 1.

Multi-Select Option Sets –

Multi-select option set is similar to option set datatype but in this we can select more than one value.This was introduced in dynamics 365 from July update. Older version will not be able to see this data type.

Features of the new Multi-Select option set include:

  • New AttributeType: MultiSelect Option Set
  • The ability to add them to forms, views, and quick create forms, and read-only and editable grids
  • Can add up to 150 values available for selection
  • Select All and Clear selection feature
  • Can leverage existing (select a global) and new option sets
  • Supported in Web Client and the new Unified Interface (coming in July as well)
  • Supported in Advanced Find and FetchXML queries
  • Multi-select option set fields cannot be a calculated or rollup field

Field Properties:

2

Every time you create new field, remember that there are several properties that you can configure this field

  • Display Name: The label of the field, visible in all the places where field is
    referenced such as forms, views, and reports.
  • Name: The logical name of the field; it is used while coding for Microsoft
    Dynamics 365
  • Description: This is used to provide additional information or setup tooltips
    for the field.
  • Field Requirement: The requirement level of the fields. It has three options:
    • Business Required, which is mandatory;
    • Business Recommended, which means it is recommended for business: and Optional.
  • Searchable: This property defines whether we can query the entity record
    based on this field or not using advanced find.
  • Field Security: Used to protect fields based on the field level security profile;
    we can configure the field level security for both custom and system fields.
  •  Auditing: Used to keep track of the changes in field value; provides two
    options, Enable or Disable.
  • Date Type: Available data types in Microsoft Dynamics CRM 2015; we can
    select them based on the data that we want to store in a field.
  • Field Type: Dependent on the data type selected. It has three options:
    • Simple,
    • Calculated
    • Rollup.
  • Format: Allows us to format fields based on the data type selected.

Calculated Fields:

In Microsoft Dynamics 365, calculated fields let you automate manual calculations used in your business processes.System administrators can now easily define a field to contain the value of many common calculations without having to work with a developer. Developers can also leverage the platform capabilities to perform these calculations rather than within their own code.First we need to select calculated field from field type from field property. Calculated field was introduced in Microsoft Dynamics CRM 2015.

3

Datatype Available For Calculated Field:

  • Single line of text
  • Option Set
  • Two Options
  • Whole Number
  • Decimal Number
  • Currency
  • Date and Time

Calculated Field Capabilities:

  • The calculated fields comprise of calculations that use the fields from the current entity or related parent entities.

  • The expression support is available on the current entity and the related parent entity fields in the Condition sections and the Actionsections.
  • A rich conditional support provides branching and multiple conditions. The logical operations include AND and OR operators.
  • The visual editing capabilities include modern user interface and intellisense in the ACTION section.
  • A seamless integration of the calculated fields with the forms, views, charts, and reports is available in real time.

 

If you updated your Online organization to December 2016 update for Microsoft Dynamics 365 (online), you can configure calculated fields to use custom controls.

Available Functions:

 

Function SyntaxData typesDescriptionReturn type
ADDDAYS
whole number, date and timeReturns a new date and time that is equal to the given date and time, plus the specified number of days.Date and Time
ADDHOURS
whole number, date and timeReturns a new date and time that is equal to the given date and time, plus the specified number of hours.Date and Time
ADDMONTHS
whole number, date and timeReturns a new date and time that is equal to the given date and time, plus the specified number of months.Date and Time
ADDWEEKS
whole number, date and timeReturns a new date and time that is equal to the given date and time, plus the specified number of weeks.Date and Time
ADDYEARS
whole number, date and timeReturns a new date and time that is equal to the given date and time, plus the specified number of years.Date and Time
SUBTRACTDAYS
whole number, date and timeReturns a new date and time that is equal to the given date and time, minus the specified number of days.Date and Time
SUBTRACTHOURS
whole number, date and timeReturns a new date and time that is equal to the given date and time, minus the specified number of hours.Date and Time
SUBTRACTMONTHS
whole number, date and timeReturns a new date and time that is equal to the given date and time, minus the specified number of months.Date and Time
SUBTRACTWEEKS
whole number, date and timeReturns a new date and time that is equal to the given date and time, minus the specified number of weeks.Date and Time
SUBTRACTYEARS
whole number, date and timeReturns a new date and time that is equal to the given date and time, minus the specified number of years.Date and Time
CONCAT
single line of text, single line of text, … single line of textReturns a string that is the result of concatenating two or more strings.String
TRIMLEFT
single line of text, whole numberReturns a string that contains a copy of a specified string without the first N-characters.String
TRIMRIGHT
single line of text, whole numberReturns a string that contains a copy of a specified string without the last N-characters.String
DIFFINDAYS
date and time, date and timeReturns the difference in days between two Date and Time fields. If both dates and times fall on the same day, the difference is zero.Whole Number
DIFFINHOURS
date and time, date and timeReturns the difference in hours between two Date and Time fields.Whole Number
DIFFINMINUTES
date and time, date and timeReturns the difference in minutes between two Date and Time fields.Whole Number
DIFFINMONTHS
date and time, date and timeReturns the difference in months between two Date and Time fields. If both dates and times fall on the same month, the difference is zero.Whole Number
DIFFINWEEKS
date and time, date and timeReturns the difference in weeks between two Date and Time fields. If both dates and times fall on the same week, the difference is zero.Whole Number
DIFFINYEARS
date and time, date and timeReturns the difference in years between two Date and Time fields. If both dates and times fall on the same year, the difference is zero.Whole Number

Disadvantage Of Calculated Field:

  • You cannot use fields on a related entity in the calculation.
  • You cannot change existing fields to calculated fields.
  • Calculated fields are not available for floating number or Lookup type fields.
  • Maximum 10 calculated field can be created for single entityM
  • Maximum 100 calculated field can be created for single organization

How To Create Calculated Field:

Once the calculated is created Click edit button near to field type and it takes us to another window.

4

 

We can have condition to trigger our calculated field.Set the action according to our business need and save the field. Now we can test the calculated field.

5

In the above example if Test field contains data it will trim test field value from left of 3 character and give the result in Test1 field.

Rollup Field:

In Microsoft Dynamics 365, rollup fields are designed to help users obtain insights into data by monitoring key business metrics. A rollup field contains an aggregate value computed over the records related to a specified record. Rollup fields are calculated by Asynchronous System Jobs which runs in background. By default, Mass Calculate Rollup Field job runs every 12 hours after a Rollup field is created or updated. This delay is needed to assure that Mass Calculate Rollup Field job runs during the non-operational hours of an organization.But in some business scenarios, users need this calculation in real-time and on demand. Rollup field was introduced in Microsoft Dynamics CRM 2015.

6

Datatype Available For Rollup Field:

  • Whole Number
  • Decimal Number
  • Currency
  • Date and Time

Rollup Fields Capabilities:

  • Visual editing is easy. You can create rollup fields by using the Field Editor, just like you do when you create a regular field.
  • Full filter support for aggregation. You can set various filters for the source entity or related entity while setting multiple conditions.
  • Seamless integration with the user interface. You can include the rollup fields in forms, views, charts and reports.
  • Rollup fields are solution components. You can easily transport the rollup fields as components between organizations and distribute them in solutions.
  • Rollup fields and the calculated fields are complementary to each other. You can use a rollup field as a part of the calculated field, and vice versa.

If you updated your Online organization to December 2016 update for Microsoft Dynamics 365 (online), you can configure rollup fields to use custom controls.

Available Functions:

  • SUM – Total or sum of the value.
  • COUNT – Count total number of record.
  • MIN – Gives the minimum of the value.
  • MAX – Give the maximum of the value.
  • AVG – Gives the average of the value.

Disadvantage Of Rollup Field:

  • We can define a maximum of 100 rollup fields for the organization and up to 10 rollup fields per entity.
  • A workflow can’t be triggered by the rollup field updates.
  • A workflow wait condition cannot use a rollup field.
  • A rollup over the rollup field is not supported.
  • A rollup can’t reference a calculated field that uses another calculated field, even if all the fields of the other calculated field are on the current entity.
  • The rollup can only apply filters to the source entity or related entities, simple fields or non-complex calculated fields.
  • A rollup can’t be done over the N:N relationships.
  • A rollup can’t be done over the 1:N relationship for the Activity entity or the Activity Party entity.
  • The business rules, workflows or calculated fields always use the last calculated value of the rollup field.
  • The maximum number of records during the rollup refresh is limited to 50,000 records.

How To Create Rollup Field:

Once the rollup is created Click edit button near to field type and it takes us to another window.

6

Source entity: We specify the entity for which the rollup field is defined and whether or not you aggregate over a hierarchy. You can add filters with multiple conditions to specify the records in the hierarchy you want to use for rollup.

Related entity: We specify the entity over which you aggregate. This section is optional when you choose to rollup over the hierarchy on the source entity. You can add filters with multiple conditions to specify which related records to use in the calculation.

Aggregate: We specify the metric you want to compute. You can choose available aggregate functions, such as SUM, COUNT, MIN, MAX or AVG.

7

In the above example it will count the number account is related to the record.

8

We can see in Test field value the number account is associated the test record.

 By default, the job will run 12 hours after you created or updated a field.

At some time we need to see the result immediately. User can refresh the value and see the result manually by clicking the refresh button in the right of the field.

9

Each Rollup Field Is Comprised Of Three Physical Fields:

  • Fieldname – stores the calculated value
  • Fieldname_date – stores the last time the field was updated
  • Fieldname_state – this appears to track if a rollup calculation has failed or is in a “bad” disposition – although I have not seen a state field in a non-zero value yet, the underlying database objects suggest non-zero values are possible.

 Solution Components

A solution can be used to package the following components customized using default, unmanaged, or managed solutions.

1

Entities:

The entities are used to model and manage business data in Microsoft Dynamics 365. For example, entities such as account, campaign, and incident (case) can be used to track and support sales, marketing, and service activities. An entity has a set of attributes and each attribute represents a data item of a particular type. For example, the account entity has Name, Address, and OwnerId attributes.

Practically, an entity is like a database table, and the entity attributes correspond to the table columns. Creating an entity record (or, simply a record) in Microsoft Dynamics 365 is like adding a row in a database table.

Option Set:

An option set is a type of field that can be included in an entity. It defines a set of options. When an option set is displayed in a form it uses a drop-down list control. Option set is also called as “picklist”.

Option Set can be defined within itself(locally) or it can be defined by global option set.you use global option sets to set fields so that different fields can share the same set of options, which are maintained in one location. You can reuse global option sets. Global option sets are useful when you have a standard set of categories that can apply to more than one entity.

Client Extensions:

This contains information about changes developers and customizers can make to extend Microsoft Dynamics 365 (online & on-premises) in the clients provided for Microsoft Dynamics 365 — the web application, Microsoft Dynamics 365 for phones, and Microsoft Dynamics 365 for tablets — by using JavaScript and web resources. These clients are designed to allow you to add extensions that can be applied for all clients rather than each one separately.Client extensions can provide a very rich and responsive experience for users because the code runs on their device. However, critical business logic should not be applied only by client-side scripts.

Web Resources:

Web resources are virtual files that are stored in the Microsoft Dynamics 365 database and that you can retrieve by using a unique URL address.Web resources are typically used by developers to extend the web application using files that are used in web development. As a Microsoft Dynamics 365 user you may need to manage web resources provided by a developer or designer.

Web resources represent files that can be used to extend the Microsoft Dynamics 365 web application such as html files, JavaScript, and Silverlight applications. You can use web resources in form customizations, the SiteMap, or the application ribbon because they can be referenced by using URL syntax.web resources are stored within the Microsoft Dynamics CRM database, they can be reused throughout the system in different forms or entities and can be deployed using Solutions.Web resources can move them to different organizations by exporting them as part of a solution and importing the solution into a different organization.Web resources are limited to specific types of files. Web resources can only be files that would be loaded into a web browser.

Processes:

Processes is used to automate the task and make the business process in a flow.Processes enable you to model real-life business processes.

Processes are divided into four category :

  • Action
  • Business Process Flow
  • Dialog
  • Workflow

Plug-in assemblies:

A plug-in assembly represents an assembly that contains one or more plug-in or custom workflow activity types.All users have read access to this entity. It is an unsafe practice to save logon credentials within this entity or within the assembly itself.

 Sdk Message Processing Steps:

This defines how a plug-in or custom workflow activity should be registered in a stage of the event execution pipeline and under what conditions it should be executed.

Service Endpoints:

A service endpoint represents a Microsoft Azure platform endpoint. This entity stores the configuration information of a service endpoint. The schema name for this entity is ServiceEndpoint.

Dashboards:

Dashboards in Microsoft Dynamics 365 provide an overview of business data ‒ actionable information that’s viewable across the organization.Dashboards are collections of view lists, charts,iFrames,web resource and Power BI   that can pull in things like website information that you can modify to show key performance indicators and other important data.

There are two types of Dashboard :

  • User dashboards. A user dashboard can be created by any user in the user’s work area: Sales, Service, or Marketing. A user dashboard doesn’t have to be published to be visible, but it’s only visible to the person who created it, unless shared with others. A user dashboard can be set as the default dashboard, in which case it overrides the system dashboard for that user.

  • System dashboards. A system dashboard is created by a system administrator or customizer in the Settings area. A system dashboard must be published to be visible. After it’s published, it’s visible to everyone in the organization, unless hidden by the admin or customizer. The admin or customizer can set a particular dashboard as the default dashboard for the whole organization.

Reports:

Reports help you manage your progress towards your goals by helping you see how you’re doing.The Microsoft Dynamics CRM report wizard is a tool that helps users quickly and easily create sophisticated reports with charts, tables and drill-through capabilities.

Connection Roles:

In Microsoft Dynamics 365, you can create and view the relationships between records for many entities using Connect. Connections enable you to easily associate users, contacts, quotes, sales orders, and many other entity records with each other. When you open a record and select Connections, you can view all of the connections between it and other records.

When creating a connection, you assign it a role. There are many different roles you can use to identify your connections, such as Account Manager or Colleague. Connection roles define how records are related to you, to your organization, or to one another, such as manager to employee. There are eight types of connection roles. Your system administrator can add new connection roles.

Article Templates:

Article templates help you create new articles for your organization’s knowledge base library. You can also create templates with boilerplate text to help article writers use consistent language and messaging.The new knowledge articles in Microsoft Dynamics 365 enable you to create rich knowledge articles along with versioning and translation support. When you create and publish a knowledge article, it become available to users in your Dynamics 365 instance so that they can use information in the articles to effectively service the customers.

Articles are essentially pieces of information that can be easily distributed. They can be as simple or as complicated as the need requires them to be. They are just contains of information and are based on a very simple concept – Knowledge Transfer. Microsoft Dynamics CRM provides the user the distributive capabilities through the system itself either through views, dashboards, cases, embedded emails & enhanced search functionality.

Contract Templates:

In Microsoft Dynamics 365 (online & on-premises), a contract is an agreement to provide support during specified coverage dates or for a specified number of cases or length of time. When customers contact customer service, the level of support they receive is determined by their contract.In order to manage and keep track of the agreements that have been made with customers, Microsoft Dynamics CRM has a Contracts.

Email Templates:

Email templates contain prefilled data that you specify, so you don’t have to reenter the same information for each article this will Save time when creating multiple email messages by making email templates.An email template is attached to an email activity after the activity is created. Typically, each type of email activity has its own email template.

Mail Merge Templates:

Mail merge templates with Microsoft Office Word to create customer-ready letters, faxes, e-mail messages, and quotes.We can use Microsoft Dynamics 365 for Outlook with Microsoft Office Word to create documents for your customers that display Microsoft Dynamics 365 data.Microsoft Office Word templates are created and edited in Word, but can be uploaded to Microsoft Dynamics 365 to use with mail merge and share with other users. Only Word .xml documents can be used as templates.

Security Roles:

Microsoft Dynamics 365 (online) the fundamental concept in role-based security is that a role contains privileges that define a set of actions that can be performed within the organization. A security role defines how different users, such as salespeople, access different types of records. To control access to data, you can modify existing security roles, create new security roles, or change which security roles are assigned to each user. Each user can have multiple security roles.They are grouped under different tabs based on their functionality. These groups include: Core Records, Marketing, Sales, Service, Business Management, Service Management, Customization and Custom Entities.

Field Security Profiles:

Field Level Security in Microsoft Dynamics CRM allows you to expand your security model beyond entities to include specific fields.You can use a field security profile to manage the permission of users and teams to read, create, or write in secured fields.

Routing Rule Sets:

Use routing rules in Microsoft Dynamics 365 to automatically route cases to the right people at the right time without any manual intervention.We can set up different queues based on different business scenarios and then define case routing rules to route cases to these queues .

Record Creation and Update Rules:

In Microsoft Dynamics 365, you can automatically create or update system or custom records from incoming Dynamics 365 activities, such as emails, social activities, or custom activities, without writing any code by using record creation and update rules. We can create multiple dynamics 365 record by setting up rule for conversion.Similarly to all other CRM components or Web resources, rules can be added to the CRM solution and can be exported and imported to other Dynamics 365 organizations.

Service Level Agreements (SLA):

Service Level Agreements offer an easy and convenient way to track the time taken by service representatives to solve support requests. It is possible to see them as timers on record forms, where they indicate remaining time until (or time passed since) or the prescribed time it takes to solve a support request.

 

Entities In Microsoft Dynamics CRM

The entities are used to model and manage business data in Microsoft Dynamics 365. For example, entities such as account, campaign, and incident (case) can be used to track and support sales, marketing, and service activities. An entity has a set of attributes and each attribute represents a data item of a particular type. For example, the account entity has Name, Address, and OwnerId attributes.

Practically, an entity is like a database table, and the entity attributes correspond to the table columns. Creating an entity record (or, simply a record) in Microsoft Dynamics 365 is like adding a row in a database table.

Entities Are Divided Into Three Categories:

  • System entities are used by Microsoft Dynamics 365 to handle all internal processes, such as workflows and asynchronous jobs. You cannot delete or customize system entities.
  • Business entities are part of the Microsoft Dynamics 365 default installation and they appear under “Customization” menu. An account, contact, and letter are examples of business entities.
  • Custom entities in Microsoft Dynamics 365 are created by users and is used to address business specific needs of the organization.

In a Microsoft Dynamics 365 Solution, you can set business and custom entities and attributes to be either customizable or non-customizable. You can modify a customizable entity by renaming it, adding new attributes, or changing various settings, such as duplicate detection or queue support settings. You cannot modify a non-customizable entity.

Creating Custom Entity :

Step 1 − Click the top ribbon button followed by Settings option. Click Customizations option from the Customization section

Capture

Step 2 − Now click Customize the System option.

Capture1

This will open up the Default Solution window.

Capture2

Step 3 − Expand the Entities option from the left panel.

Capture3

Step 4 − Now click New → Entity.

Capture4

Step 5 − In the Entity Form, enter the Details.

Capture5

Capture6

Custom entity options :
There are lots of options to consider when creating a custom entity. It’s important
to know how to choose the right options so that your custom entity meets your
requirements.

Entity definition:

  • Display Name: This is the name of the entity your users will see. It can be
    changed later.
  •  Plural Name: This is the plural name of the entity your users will see. It can
    be changed later.
  • Name: This is the schema name of the entity that your developers will use. It cannot be changed later. This name is prefixed with the customization prefix set by the publisher of the entity’s solution. This name is used as the table name in the SQL Server database.
  • Primary Image: System entities that support images will already have an Image field. You can choose whether to display data in this field as the image for the record by setting this field to [None] or Default Image.For custom entities you must first create an image field. Each entity can have only one image field. After you create one, you can change this setting to set the primary image.
  • Ownership: This field determines whether records of this entity will be owned by a user or a team or by an organization. The records owned by a user or a team can be assigned to a user or team whereas the records owned by an organization cannot be owned by anyone. You can apply the security privileges at the user, business unit, parent-child business unit, or organization level to the user- or team-owned entities, but the security privileges at the organization level can be applied only to the organization-owned entities. This option cannot be changed later, so it is important to consider your security requirements carefully before creating a new entity.
  • Define as an activity entity: This field determines whether your custom entity will be a custom activity entity. Activity entities—such as task, appointment, and e-mail—have special properties. For example, they can be associated with many other entities using the Set Regarding field and they can make use of the Activity Party field to be associated with multiple accounts, leads, or contacts in a single field. However, you cannot apply security privileges to the custom activity entities (activity security privileges apply to all types of activities) and you cannot synchronize custom activity entities with Outlook.
  • Display in Activity Menus: This checkbox determines whether the entity
    will be displayed in activity menus or not.

Areas that display the entity:
The options in this section represent the high-level navigation groups (defined in
the SiteMap). The standard areas are Workplace, Sales, Marketing, Service, Settings,
Resource Center. If you have customized the SiteMap, the navigation group options
may vary.Selecting an option causes your custom entity to be available in the corresponding navigation group.

Process:

Business process flows: Create business process flows for this entity.

Communications and collaboration:

  • Feedback : Let customers write feedback for any entity record, or rate entity records within a defined rating range by enabling entities for feedback.For example, you can enable feedback or ratings on the Case entity to receive feedback on the support experience the customer received. When several customers are rating a record, the ratings can be consolidated for each record through a custom rollup field. In a sales scenario, you can enable the Product entity for feedback to get users’ feedback on the products you sell.By default, feedback is enabled for the Knowledge Article entity and the rollup field that stores the rating is added to knowledge article form.This feature was introduced in CRM Online 2016 Update 1 and in CRM 2016 SP1 (on-premises).
  • Notes (includes attachments): This option enables notes and attachments
    for your custom entity. Once you enable this option, it cannot be disabled.
  • Activities: This option enables the activities for your custom entities so that
    activity records can be associated with this entity. If this option is enabled,
    the Activities and Closed Activities navigation links are added to the entity
    forms. Once you enable this option, it cannot be disabled.
  • Connections: This option enables connections for your custom entity so that
    you can create connections between this entity’s records and other records.
    If this option is enabled, a Connections navigation link is added to the entity
    forms. Once you enable this option, it cannot be disabled.
  • Sending e-mail: This option enables direct e-mail messages to be sent
    to the records of this entity from the entity’s grid screen. Unless there is
    already an e-mail field, a new e-mail field called E-mail Address will be
    created. Once you enable this option, it cannot be disabled.
  • Mail merge: This option enables the mail merge feature for records of
    the entity.
  • Document management: This option enables the SharePoint-integrated
    document management feature for this entity.
  • Access Teams : New type of team in Dynamics CRM 2013. Fundamentally they are different from the traditional owner teams we know in CRM 2011 in that they are not used to grant ownership to a record but instead they grant access to records via sharing. In addition, with access teams, you can create multiple teams that can each be granted varying levels of access to a single record. As we know, in CRM 2011, only a single team could be provided ownership (and thus access) to a record.Access teams provide an alternate way of exposing and sharing records across functional teams without the need to modify or update the base security model in CRM via Business Units, Security Roles, or Teams.
  • Queues: This option enables the records of this entity to be added to a
    queue to help you manage workloads.
  • Automatically move records to the owner’s default queue when a record
    is created or assigned: Every user and team has a default queue. Selecting
    this option will cause all records assigned to the user or team to appear in
    the user’s or team’s default queue.
  •  Enable for SLA:In earlier versions of CRM, the SLA feature was only applied to the Case Entity. Now, with Dynamics CRM 2016 Update 1 release, you can enable Enhanced SLA for other entities as well.Below are the entities for which you can enable SLA in CRM.
    • Contact, Account, Lead, Opportunity, Quote, Order, Invoice.
    • Custom Entities and Custom Activities.
    • Also for some activity entities as email, phone, and appointment except for the recurring appointment.

Data services:

  • Allow Quick Create: This feature was introduced in Dynamics CRM 2013 are very useful to create a record without navigating from current screen.
  • Duplicate detection: This option enables duplicate detection for
    the entity. The duplicate detection rules can only be defined for
    the duplicate detection-enabled entities.
  • Auditing: This option enables changes to this entity’s records to
    be audited. The global auditing settings must be configured before
    entity-level auditing starts.
  • Change Tracking: This feature was introduced from Dynamics CRM Online 2015 Update 1.The change tracking feature in Microsoft Dynamics CRM provides a way to keep the data synchronized in a performant way by detecting what data has changed since the data was initially extracted or last synchronized.

Outlook and mobile:

  • Enable for phone express: Make this entity available to the Microsoft Dynamics 365 for phones express app.
  • Read-only in mobile: This will make the entity read only in mobile app.
  •  Reading pane in Dynamics 365 for Outlook : Records for this entity can display in a read-only view in Dynamics 365 for Outlook.
  • Offline capability for Dynamics 365 for Outlook:
  • People using Microsoft Dynamics 365 for Outlook can choose to include data from this entity with the data they take offline.

Primary Field:

Each custom entity has a primary field. This is defined in the Primary Field tab. This field is used when records for the entity are displayed in a list. The primary field is typically a link that opens the record. This field must be a Single Line of Text field with the format of Text. When creating the entity the only value that can’t be changed later is the Name. By default the Display Name is “Name” and the Name is your solution publisher customizations prefix, an underscore, and “name”. If this isn’t what you want, change this before you create the entity. After you save the entity, you can’t edit the primary field values from the Primary Field tab for the entity. You must locate this field in the entity fields. You’ll be able to edit it there like any other single line of text field.

Entity Ownership:

  • Organization Owned: Contains data involving something that belongs to or that can be viewed by the whole organization. Organization-owned entities cannot be assigned or shared. For example, products are owned by the organization. These entities have an attribute named organizationid. There are 68 organization-owned system entities. These include Article, Article Template, Competitor, Currency, and Web Resource.
  • Business Owned: Entities that belong to a business unit. These entities have an attribute named owningbusinessunit. There are 12 business-owned system entities. These include Business Unit, Calendar, Team, Security Role, and User.
  • User or Team Owned: Assigned to a user or to a team. These entities contain data that relates to customers, such as accounts or contacts. Security can be defined according to the business unit for the user or team. These entities have attributes named owningteam and owninguser. There are 59 user or team owned system entities. Because these records are owned by a user or team, they’re connected to a business unit and specific security roles for the business unit. Therefore, these entities participate in role-based security.
  • None: These entities are not owned by another entity.There are 127 system entities that don’t have an owner, but most of these aren’t visible in the solution explorer. These mostly consist of intersect entities created to support Many-to-Many relationships or where access to the record is controlled by a parent record. For example, Opportunity Product records must be accessed through a user or team owned Opportunity record.

Step 6 − Save the detail and publish the created entity in your organization.

Totally we can create 300 custom entity for single organization

 Introduction To Solutions

Solutions which was introduced in 2011 are one of the fundamental parts of CRM customization and CRM Development, they  provide a way to manage and package your changes in CRM and importantly a way to move customizations between CRM instances.

Components of Solution: A solution can be used to package the following components:

Component TypeComponent
SchemaEntities
Attributes
Relationships
Global Option Sets
User InterfaceApplication Ribbon
SiteMap
Forms
Entity Ribbons
Web Resources
AnalyticsDashboards
Reports
Visualizations
Process/CodeProcesses
Dialogs
Workflows
Plugins
Assemblies
Processing Steps
TemplatesMail-merge
Email
Contract
Article
SecuritySecurity Roles
Field Level Security Profiles

There are three different types of solutions: default, managed and Un-managed.

Default Solution:

Default solution also known as Vanilla solution includes out-of-the-box Microsoft Dynamics CRM software as well as the pre-deployment customizations. You can access a default solution by navigating to SettingsCustomizations, and Customize the system

Managed Solution

A managed solution is a solution that is completed and intended to be distributed and installed. Managed solutions can be installed on the top of the system solution or other managed solutions.

Important Points regarding Managed Solutions

  • If you export a managed solution from one organization and import it to another, you can’t edit the solution in the new organization.

  • A managed solution does not directly reference the system solution.
  • Uninstalling a managed solution uninstalls all the customizations associated with the solution.
  • By default, a managed solution can’t be customized in the target organization. However, using the concept of managed properties you can define whether a solution component will be customizable and if yes, then which specific parts of the component will be customizable once the solution gets exported as a managed solution.

  • User can’t export a managed solution.

Un-managed Solution

An un-managed solution is a solution that is still under development and not intended to be distributed. An unmanaged solution contains all the unmanaged customizations of CRM components including any added, modified, removed, or deleted components. By default, any new solution is an unmanaged solution. However, you can export an unmanaged solution as a managed or unmanaged solution.

Important Points −

  • If you export an unmanaged solution from one organization and import it to another, you can edit the solution in the new organization.

  • An unmanaged solution directly references the system solution. Hence, the changes made to one unmanaged solution will be applied to all the unmanaged solutions that references the same components, including the system solution.
  • If you delete a solution component from an unmanaged solution, the component gets deleted permanently from the system and will no longer be available. In case you just want to remove the component from specific unmanaged solution, use remove instead of delete.
  • Uninstalling an unmanaged solution does not remove the associated customizations. It just deletes the solution from the system, but the changes you made will still be there.

Creating Solution :

Step 1 − Navigate to Settings → Solutions. Click New.

1

2

Step 2 − In the window that follows, enter the following details and click Save and Close.

3

 

Display Name − Sample Solution (This can be any name that you want).

Name − Will be automatically set based on the Display Name. However, you can change this.

Publisher − Default Publisher. Solution publisher provides a common customization prefix and option value prefix. Defining a solution publisher controls how your managed solutions can be updated once distributed. In general cases, you can set this as Default Publisher.

Version − Specify a version with the following format: major.minor.build.revision. For example: 1.0.0.0.

Step 3 −  Save the solution and publish it.

Exporting a Solution:

Once the customization and configuration for the solution is done, we can export the solution from one environment to another environment or for backup purpose of the solution we can export.

Step 1 − Navigate to Settings → Solutions.

1

2

Step 2 − Select the solution to be exported and click export button

4

Step 3 − In the Publish Customizations window, click Publish All Customizations and then click Next.5

Step 4 −In the window that follows, you can optionally select any system setting such as auto-numbering, calendar settings, etc. to be exported with the solution.

6

Step 5 − In the package type window you can select either managed solution or unmanaged solution to export.

7

Step 6  − user can see the source version of CRM that you are using and can select the target version. Click Export.

8

Step 7 − The solution will be exported as a zip file. Save this zip file at a desired location on your system.

9

Importing a Solution:

We need import the solution zip file to our new target organization.

Step 1 − Navigate to Settings → Solutions.

1

10

Step 2 − Click import button

11

Step 3 − Browse the zip file from where user has saved and click Next.

12

Step 4 − User can view the solution package details if needed. By clicking the next the import process will start.

13

Step 5 − Once the import process completes, it will show the status of success or failure. If the process succeeds, click Publish All Customizations. In case the solution importing fails, by clicking download log file we will get detailed error log on which step of the import process failed.

14

Step 6 − The solution will be successfully imported to the target organization. Click Close.

2

Clone a Patch:

A patch represents an incremental minor update to the parent solution. A patch can add or update components and assets in the parent solution when installed on the target system, but it can’t delete any components or assets from the parent solution

If you add an entity to a solution and export the solution, the entity and all of its related assets are exported in that solution. These assets include attributes, forms, views, relationships, and visualizations, and any other assets that are packaged with the entity. Exporting all objects means that you can unintentionally modify objects on the target deployment, or carry over unintended dependencies.

To address this, you can create and publish solution patches that contain sub components of entities rather than publishing the entire entity and all of its assets. The original solution and one or more related patches can be rolled up (merged) at a later time into an updated version of the solution, which then can replace the original solution in the target Microsoft Dynamics CRM organization.

You can apply patches to either managed or unmanaged solutions and include only changes to entities and related entity assets. Patches do not contain any non-customized system components or relationships that it depends upon because these components already exist in the deployed-to organization. At some point in your development cycle, you can roll up all the patches into a new solution version to replace the original solution that the patches were created from

image

Clone a Solution:

Clone a solution – merges the patches with base solution and creates the new solution

A cloned solution represents a replacement of the base solution when it’s installed on the target system as a managed solution. Typically, you use a cloned solution to ship a major update to the preceding solution.

If you select your Base solution and choose Clone Solution, all of your patches are rolled into your Base solution leaving with you with ONE solution to manage.

image

 Dynamics 365 With Power BI

Power BI is a suite of business analytics tools to analyze data and share insights. Power BI dashboards provide a 360-degree view for business users with their most important metrics in one place, updated in real time, and available on all of their devices. With one click, users can explore the data behind their dashboard using intuitive tools that make finding answers easy. Creating a dashboard is simple, thanks to hundreds of connections to popular business applications, complete with prebuilt dashboards to help you get up and running quickly. And you can access your data and reports from anywhere with the Power BI Mobile apps, which update automatically with any changes to your data.

If you are a data analyst delivering reporting and analytics to your organization, Power BI lets you be productive and creative with what you build. Power BI Desktop is a feature-rich data mashup and report authoring tool. Combine data from disparate databases, files, and web services with visual tools that help you understand and fix data quality and formatting issues automatically. With over 20 built-in visuals and a vibrant community of custom visualizations, create stunning reports that communicate your message effectively. With the Power BI service, publish reports securely to your organization and setup automatic data refresh so everyone has the latest information.

Power BI can unify all of your organization’s data, whether in the cloud or on-premises. Using the Power BI gateways, you can connect SQL Server databases, Analysis Services models, and many other data sources to your same dashboards in Power BI. If you already have reporting portals or applications, embed Power BI reports and dashboards for a unified experience.

Microsoft is building lots of cloud based technologies these days and Microsoft Dynamics CRM is not an exception. With a powerful data visualization tool like Power BI Microsoft took a great step to integrate Dynamics CRM and Power BI which means you can easily connect from Power BI website and Power BI Desktop to a cloud based Microsoft Dynamics CRM instance. In this article I express a step-by-step tutorial to be able to connect to connect to Dynamics CRM from Power BI website as well as Power BI Desktop.

Prerequisites:

  • You can only connect to Dynamics CRM Online (Cloud based Dynamics CRM) from both Power BI Desktop and Power BI website. If you have an older version on-premises Dynamics CRM and you’re willing to create visualizations on Power BI then you need to connect to the CRM database on SQL Server instance just like any other SQL Server databases.
  • First we need to enable Power BI for Dynamics 365 Organization.
  1. After browsing your CRM Online, click “Administration” from “Settings” then click System setting

Embed Power BI Tiles

     2. From here, navigate to the Reporting tab and select Yes to enable Power BI.

Embed Power BI Tiles

  • You need to have a valid OData URL for a Dynamics CRM Online instance and an administrator must enable the OData endpoint in the CRM site settings. To find the OData endpoint address, refer to the below mentioned steps:

After browsing your CRM Online, click “Customizations” from “Settings”

Dynamics CRM OData for Power BI

     Click “Developer Resources”

Dynamics CRM OData for Power BI 2

  • You can see OData URL under “Organization Data Service”

Dynamics CRM OData for Power BI 3

  • Copy the OData URL, we’ll need this URL to connect to Dynamics CRM Online from both Power BI website and Power BI Desktop
  • You should connect to Dynamics CRM Online using the same user account as your Power BI website. So if you have a different Power BI account then unfortunately you need to create a new account in Power BI which is identical to your CRM account.
  • Your browser’s popup blocker should be disabled or you should exclude  from your popup blocker.

Power BI Website and Dynamics CRM:

Get Data:

  • Browse and sign in to Power BI website from a browser
  • From “Microsoft AppSource” click “Services”

1

  • Search and Click “Dynamics 365” then click “Get Now”

2

  • Paste the OData URL you copied earlier and enter any “Fiscal Year End Month Number”, click “Next”

3

  • If you get the error message “Parameter validation failed, please make sure all parameters (Backslash) are valid.” then you probably forgot to remove the forward slash (/) from the OData URL.

image

The OData should be something like this:

https://%5Btenant%5D.crm5.dynamics.com/XRMServices/2011/OrganizationData.svc

rather than

https://%5Btenant%5D.crm5.dynamics.com/XRMServices/2011/OrganizationData.svc/

  • Select “oAuth2” from “Authentication Method” drop down list then click “Sign In”

4

  • Now you’re connecting to Office 365. Sign in to your office 365 account and click on “Work or school account”. Remember, you should use the same user account as your Dynamics CRM Online account here.

Office 365 Credentials

NOTE: Your popup blocker should be disabled.

  • Sign in to your Office 365 account
  • You can see a predesigned dashboard ready to use in your Power BI website.

Schedule Refresh:

  • Find the Dynamics CRM in “Datasets” pane then click “Open Menu” ellipsis

Dynamics CRM and Power BI 2

  • Expand “Data Source Credentials” and “Schedule Refresh” and setup the desired schedule

Dynamics CRM and Power BI 3

Power BI Desktop and Dynamics CRM:

Get Data:

  • Open Power BI Desktop
  • Search for “CRM” to easily find the connector then click connect

Dynamics CRM and Power BI 4

  • Paste the OData URL you copied before
  • Remember to remove the last forward slash from the end of the URL
  • Click OK

Dynamics CRM and Power BI 5

  • You can search the tables and select those ones you need then click “Load”

Dynamics CRM and Power BI 6

  • Now you can create your visualizations. I’m not going to explain how to do that as it had been covered here.
  • Publish the visualization to Power BI website by clicking on the “Publish” button from the ribbon bar

Dynamics CRM and Power BI 7

Schedule Refresh:

  • From Power BI website find your newly published dataset from “Datasets” pane
  • Click “Open Menu” ellipsis

Dynamics CRM and Power BI 8

  • Click “Schedule Refresh”
  • Click “Edit Credentials” under “Data Source Credentials”
  • Select “oAuth2” from “Authentication Method” drop down then “Sign In”

Dynamics CRM and Power BI 9

  • Connect to Office 365 using your credentials
  • Expand “Schedule Refresh” and setup the desired schedule

Dynamics CRM and Power BI 10

Power BI Dashboard in Dynamics 365:

Once the dashboard is ready in power bi

Embed Power BI Tiles

We can insert Power BI dashboard directly into dynamics 365 dashboard using below screenshot

5

Select a Power BI dashboard and a tile.

Embed Power BI Tiles

Complete the dashboard, Save, and close.

That’s it! You now have a Power BI dashboard built in CRM. Users no longer need to navigate specifically to Power BI to interact with the powerful analytics.

Embed Power BI Tiles

If you click on any component, a new window is launched which allows for further filtering or drilling into the Power BI site.

Embed Power BI Tiles

Embed Power BI Tiles

 

 Dynamics 365 Portals

A Dynamics 365 portal provides your audience an online location to communicate and collaborate. Depending on the audience that the portal is geared toward (such as whether it’s for customers, business partners, or internal team members), a Dynamics 365 portal can allow people to get support for issues, search knowledge guides and how-to guides, collaborate with communities, suggest new ideas, and learn more about your products and services.

There will be no new hardware to procure, certificates to install, or web servers to provision. In a few clicks, your new integrated web presence is ready to go and waiting for you to mold it into the online game-changer we both know it can be.

Implementing a portal can help you give the right people access to the right data—without giving them full access to your CRM system. With a portal, you can,

  • Increase revenue opportunities
  • Increase productivity by providing timely access to information
  • Extend your CRM system outside your organization and enable input from external parties
  • Allow users to access information themselves when they need it
  • Improve customer and/or partner communication and satisfaction
  • Build stronger business relationships

Dynamics 365 Portal Types

Dynamics 365 has four pre-configured Portal solutions. You can start with one of these and then add your own pages and business logic.

Custom Portal
Custom Portals come with minimal set of pre-defined page templates where you can start creating a Portal of your own per your tailored needs.

Customer Self-Service Portal
Customer Self Service Portal is used by the customers of the organization. This portal is their own space of use where they can login and view as well as register their own support cases and manage the same. Along with that, Knowledge Base can be accessed and Forums topics can be started on this portal.

Partner Portal
Partner Portal enable business partner to build business by working on Opportunities of your organization.

Community Portal
Community Portal serves to grow a community of people by sharing ideas, voting them and starting forum discussions about a certain topic.

Configure Your Own Dynamics 365 Demo Portal:

Traditionally Managed Solution are added by selecting the Instance Tab from the Dynamics 365 Administration Center via the Solutions Buttons for the instance. Instead Navigate to the ‘Applications’ tab in the Dynamics 365 Administration Center, you should now see a new Portal Add On Application that would have appeared when you added your Portal Subscription with the Status of ‘Not Configured’, and click ‘Manage’ for the ‘Portal Add-on’ to configure it;

Step 1 – Navigate to your Dynamics 365 Administration Center

Then open the Dynamics 365 Admin center:

Step 2 – Click over to Applications and observe your Portal Add-On 

Step 3 – Click on “Manage” and get ready for the hard part

  • Provide some starting parameters for your new Portal:
    • A Name
      • Just something to identify your portal instance. you can change this later.
    • A Portal URL (You can convert this to a vanity URL at a later time)
    • Select your CRM instance
    • Select a Language
    • Select an Administrator (If you’ve made it this far that’s probably you! Congratulations!)
    • Select an Audience
      • Partners – These folks might not be true employees but we want them to have some level of interaction with our CRM data to help deliver services or close deals.
      • Customers – External folks who we can serve better by surfacing some things through an external portal such as customer service or community building.
      • Employees – Support your own internal workforce though tailored portal applications such as Employee Self-Service.
    • Select your portal template
      • Customer Self-Service
      • Community
      • Partner
      • Custom Portal

13

 

Step 4 – Wait

You’ll be asked to login to your portal and grant some rights,

Note that you can check on the status at any time from your Dynamics 365 Admin center by opening the Solutions link in your instance.

14

 

Observe that our customer self-service portal template is in the Installing phase.

15

 

Manage the Portal Installation:

Once the Portal has been installed you can go back to into the Applications Tab and Click the Manage button for the Portal Add-on. Here you can configure the following portal setting and even restart the portal installation if you feel it was not completed successfully.

 

Navigating to the URL you specified for the Portal

Once the Portal Solution is installed you should be able to see the solution installed and the Portals Application menu appear in the Dynamics 365 menu.

Configure Portal Contact Web Roles

In order for your User account to configure the Portal you will need to assign the Administrators Web Role for the corresponding Portal Contact record that is created during the installation. Navigate to the Dynamics 365 Contacts, you should be able to find the Contact record that corresponds to your user account. The Portal Contact form will have a Web Roles tab, Check it has the Administrator Role, If not you can add the web role as shown below.

 

16

Login to the Portal:

The portal can be accessed by the following user set:
  • Registered CRM Users
  • External Users (Through Registration &  Redeem Invitation)
Now that you have assigned the Privileges to your Portal User, Clicking the Sign in Button on the Portal homepage, and pressing Azure AD will allow you to sign in with your Office 365 logged in credentials.
Now that you Portal User account is configured you can login to access your Portal Site and Portal Configurations in Dynamics 365, you can begin customizing your Portals.
17
Logging in with your Portal User Account configured with Administrators Privilege will display the Wizziwu widget in the top right corner allowing you to edit the Portal forms, you can use this to directly edit the pages.
19
18
I hope you find it useful, Further information for configuring / Customizing Dynamics 365 Portals can be found on the following links provided below,