Organization Owned Entity – Visibility across all users in organization.

e.g. Master Data of City, State

User Owned Entity – Control visibility.

Security can be defined according to the business unit for the user or team. These entities have attributes named owningteam and owninguser.

e.g. Sales Rep data should not be visible to other Sales Rep.

The user requires a system admin or system customizer security role and membership in the development administrator group, in order to register a plug-in with the platform. Whereas, the user can use the web application for workflow.

E-mail router in MS CRM forms the software component which creates an interface between the Organization’s messaging system and the Microsoft Dynamics CRM deployment.

The metadata of MSCRM holds the information about the attribute and the entity. For instance, platform name, datatype of attribute, size of the attribute, display name, etc.

The discovery services function for determining the correct organization and URL. MSCRM has many servers, each of which it, might be dedicated to multiple organization.

No. We will have to re-install MSCRM. It can be renamed.

Maximum limit is 8.

Dialogs refer to synchronous processes which require user input, a wizard-like an interface. Whereas Workflow refers to Asynchronous process which requires no user input and it is a background process.

A plug-in is a custom business logic which functions for integrating Microsoft Dynamics CRM 2011 with Microsoft Dynamics CRM online. This integrating is to augment or modify the standard behavior of the platform.

Workflow involves the automation of business processes from one party to another whose actions are in accordance with a set of rules.

The user requires a system admin or system customizer security role and membership in the development administrator group, in order to register a plug-in with the platform. Whereas, the user can use the web application for workflow.

Here the answer would likely be that it depends on the characteristics of the functionality that is under consideration. And the same thing applies to plug-in.

One can use the following pathway to ensure this: Navigate to Customization >> Open the Entity >> Open Forms and Views >> Open Form >> Select Form Properties >> Open Display Tab >> Check/Uncheck the “Enable the Form Assistant” and “Expanded by Default”.

No, it is not necessary. One can use in-house or external SMTP and POP3 services.

By using Dynamic entity.

The 21st User will get created in MSCRM but that user will be in disabled state.

Managed solutions are a kind of completed package with the help of which one can distribute and install in the respective CRM organizations.

No, we cannot export default solution as a managed solution.

An unmanaged solution can be defined as a collection of customizations unmanaged in nature. It is worthwhile to note that customized solution unmanaged in nature and its components may be interrelated with some unmanaged solutions. One can export a solution as a managed solution. Moreover, the customizations cannot be rolled back once they are imported into CRM.

There exist two Dynamic CRM solutions. They are unmanaged and managed. One can answer that default solution is also there in Microsoft Dynamics of an instance.

No for Online and On-Premise.
Online – Delete instance and re-create
On-Premise – Delete organization and re-create
What is need to change name of root business unit?

Online – Enable Tracing logs for online or within the registration tool use the profiling for debugging.

On Premise – Write in File for On-premise

Use F12 and Breakpoints in debugging mode.

Batch Mode – Scheduler or exe.
Real Time – Web Service (ASMX/WCF – Windows Communication Foundation).
Push Mechanism.
Pull Mechanism.

Asynchronous – Background execution of custom logic , no impact on user screen behavior.
Synchronous – Execution custom logic in which user has to wait for complete execution of logic.

1. Pre-Validation: is before the record even reaching the stage of pre-operation, so means not yet saved, it is the first layer, usually used for validation, but not many people use this, usually will just use pre-operation.

2. Pre-Operation: is also before the record created, not yet database transaction committed.

This is usually used to modify attribute value by system (logic code), validation as well.

Any changes of attribute in the pre-validation would be dismissed if you modify the attribute from this stage.

Since mentioned before, this is not yet created, so, there is no ID created at this point.

3. Post-Operation: is after the record created, database transaction committed, and you would get the GUID.

In case of Pre-image you will get the image of the record which is stored in the SQL database before the CRM Platform action has been performed. You will get all the Values before update.
Post Image, returns the image of the record after the CRM Platform action has been performed. You will get all updated values in case of post Image.

Secure Configuration- 
Imagine that you include a plugin, plugin steps and activate them in solution. Later solution was exported as Managed Solution to another environment. In this scenario, the supplied Secure configuration  information would NOT be available in the new environment. The simple  reason behind this is to provide more security to the contents of Secure Configuration.
Unsecured Configuration –
Imagine that you include a plugin, plugin steps and activate them in a solution. Later solution was exported as Managed Solution to another environment. In this scenario, the supplied Unsecured configuration values would be available in the new environment.

Using SLA you can configure escalation
entitlement – It is an agreement of service

 Article Template
 Chart
 Contract Template
 Email Template
 Entity Relationship
 Field Security Profile
 Mail Merge Template
 Option Set
 Process
 SDK Message Processing Step
 Service Endpoint
 Web Resource
 Business Rule
 Connection Role
 Dashboard
 Entity
 Field
 Form
 Message
 Plug-in Assembly
 Report
 Security Role
 Site Map

Managed properties will help you in identifying the components of the managed solutions that can be customized. If you
wish to apply managed properties, then you need to include an entity using a managed solution and download it into
another environment. These settings will give the power to Solution makers to restrict or impose restrictions on the
users to make customizations. If you wish to set managed properties for an entity all you need to do is select the entity
from the menu bar and click on the Managed Properties.

Workflow refers to the Asynchronous process and requires no user input. It is a background process. Whereas dialogue
works based on the synchronous process and a user needs to give input.

Following are the privileges need to create a solution:
 Read-write of solutions
 Read-write of web resources
 Publish customizations
 Read-write of Customizations
 Read-write of publishers
 Import and Export customizations

In MS CRM each solution has a publisher. The publisher component works closely with data sources to track
modifications over a specific time period. The Microsoft dynamics comes with a default publisher named with “Default
Publisher for”. You can also have a chance to create a customized publisher for a solution.

The web resources are nothing but components of CRM to develop HTML, JS, Images, Silverlight, and style sheet files.
Following are the various web resource we have in CRM:
 Webpage (HTML)
 Script (JScript)
 Image (PNG)
 Image (GIF)
 Style Sheet (XSL)
 Style Sheet (CSS)
 Data (XML)
 Image (JPG)
 Silverlight (XAP)
 Image (ICO)

Following are the list of data types we have in CRM:
 A single line of text
 Date and Time
 Multiple lines of text
 Decimal Number
 Floating Point Number
 Option set
 Lookup
 Currency
 Whole Number
 Two Options
 Image

Following are some of the widely used tools for CRM development:
 CRM Developer toolkit
 Ribbon Workbench
 Xrm Toolkit
 Plugin Registration.

No, it is not possible to update the components in a managed solution.

List the components which are required to publish when they are updated in the system
Following are the components which need to be published when updated
 Application Ribbon
 Entity Relationship
 Form
 Option Set
 Web Resource
 Entity
 Field
 Message
 Site Map

The maximum character limit of the “Multiline textbox” is 1048576.

Microsoft Dynamics CRM is offering two products which are CRM online and CRM On-premises.
CRM Online
This is a cloud-based service offered by Microsoft in which all the services such as application servers, deployments,
licensing, databases, setups, etc are managed on Microsoft owned servers. CRM online is a subscription-based service
suitable for organizations who are unable to manage the technicalities involved in CRM implementation. Setting up an
online CRM will take only a little time from weeks to months.
CRM On-Premise
This is the more robust and highly customizable offering from Microsoft Dynamics CRM. In this module, all the
applications and databases would be deployed on client-server rather than Microsoft servers. CRM on-premises gives
you overall control on things such as customizations, database, backups, deployments, licensing and a lot more other
setups. This is best suitable for those who require customized CRM solutions and better integration capabilities.

An Entity in CRM helps in modelling and managing business data. Various types of entities are Cases, Contacts, Accounts,
Opportunities, Leads, Activities, etc. It acts as a database table and stores the information which is organized format and
easy to retrieve.

It is one among the advanced features available in Microsoft Dynamics CRM. It comes with the out-of-the-box with CRM
and available as a search icon on top of the ribbon bar on your Microsoft Dynamics irrespective of your screen size and
type.

Object level – Using Security Roles, set permission to object level e.g. Account
Field level – By using Security Profile
Form level – Can apply security role to specific form of an entity

The 21st User will get created in MSCRM but that user will be in disabled state.

OData is the primary method to retrieve information from related records

The purpose of access teams are to easily share records with a team of people where the members of the team are not static.

Mention – Metadata is the data about data.  CRM has lots of Metadata, types of field, options value, auditing etc.

To retrieve Metadata you need use web services, RetrieveEntityRequest for entity Metadata and RetrieveAttributeRequest.

The big difference is you can’t see or modify the CRM server and SQL server.  CRM Online limitations, such as Sandbox plugins, workflow limit of 200, custom entities 300, storage is a monthly fee.

Reading and understanding code is important because code spends most of its time in a maintenance state.  Developers will need to read and understand code to extend the code, debug the code.

CRM Async services stopped, APP Pool service account password, SQL Server services, Disk space, Active Directory

Entityname+Base , EntityName+ExtensionBase

For example: if you created an entity bank then following tables will be created at crm database                          new_bankbase , new_bankentensionbase.

Yes we can hide particular section using following line of code.

Xrm.Page.ui.tabs.get(“tab_name”).sections.get(“section_name”).setVisible(false);

Filtered views will not return data for the secured fields if the calling user does not have authorization for the fields. When no field security is applied for any of the view’s attributes, the filtered views return complete data.

No, there are a few additional rules that apply to certain attribute data types.

• Boolean attributes can be secured for create and update operations but not for read.
• Option set attributes can be secured for create, update, and read when a default value is unspecified.

• Click on settings Icon at top right corner of the CRM instance
• Select Options
• Under General tab, select Default pane and Default Tab

• Click on settings Icon at top right corner of the CRM instance
• Select Options
• Here, user can update general settings like default module, #records per grid view, tmezon, currency, email settings, format settings, synchronization settings, email templates and etc.

• Click on settings Icon at top right corner of the CRM instance.
• Select Options.
• Under General tab, select the value for Records per page (25, 50, 75, 100 and 250).

• Enable field-level security for an attribute.
• Associate users or teams with the profile.
• Create a field-level security profile.
• Add specific field permissions, such as Create, Update or Read for a specific attribute to the profile.

It will automatically be added to all Field Level security roles with Read, Create and Update all set to No.

Field level security profile contains all the fields from all entities which are allowed for field level security.

Relevance search is more like a search engine search, it is more fast than the Categorized search.

Note : Add the searchable columns in Quick Find.