Explore topic-wise InterviewSolutions in .

Field LEVEL SECURITY profile CONTAINS all the fields from all entities which are ENABLED for field level security.

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

• A FIELD that is enabled for field level security is added to all field level security PROFILES in CRM.
• It will AUTOMATICALLY be added to all Field Level security ROLES with Read, Create and Update all set to No.

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

Below are the security PERMISSION that we can restrict the users/teams on INDIVIDUAL FIELDS:

• Read
• CREATE
• UPDATE

Below are the security permission that we can restrict the users/teams on individual fields:

• 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).

• 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 Default PANE and Default Tab

• Single LINE of text
• Multiple LINES of text
• Currency
• Date and Time
• Whole Number
• Decimal Number
• FLOATING Point Number
• OPTION set
• Two Options
• IMAGE
• Lookup

• Click on settings Icon at TOP RIGHT corner of the CRM instance
• SELECT Options
• Under format tab
• Click on “Customize”
• Here, user can CHANGE the format of Number, Currency, DATE and Time

The maximum limit of RECORDS can be DISPLAYED in CRM grid view is 250.

The maximum limit of records can be displayed in CRM grid view is 250.

StringMapBase

StringMapBase

• FIELD level security : DISABLE
• AUDITING : ENABLE

• OPTIONAL
• BUSINESS RECOMMENDED
• REQUIRED

2-8

2-8

It will be created on 1:N RELATIONSHIP mapping and will be PLACED at “N” side ENTITY

It will be created on 1:N relationship mapping and will be placed at “N” side entity

The MAXIMUM CHARS LIMIT For “MULTILINE TEXTBOX” is 1048576

The Maximum Chars limit For “Multiline textbox” is 1048576

NAVIGATE to Settings –> CUSTOMIZATIONS –> DEVELOPER RESOURCES

Navigate to Settings –> Customizations –> Developer Resources

If USER prepares an object with secure FIELDS to Create/Update a record then it will show “INSUFFICIENT PERMISSION” error on creating/updating the record.

If user prepares an object with secure fields to Create/Update a record then it will show “Insufficient permission” error on creating/updating the record.

When USER CALL the Retrieve/RetrieveMultiple messages, CRM evaluates if the user has ACCESS to each retrieved RECORD and each secured field. CRM wont show error message if the retrieve column set contains secure fields instead null values are returned for secured fields.

When user call the Retrieve/RetrieveMultiple messages, CRM evaluates if the user has access to each retrieved record and each secured field. CRM wont show error message if the retrieve column set contains secure fields instead null values are returned for secured fields.

A user with access to a SECURED field in a record can CHOOSE to share it with another user or team. The user can only give the access that they have on the record. For example, to share the record and grant Update PRIVILEGES, the user must have update privileges.
You can share a secured field on a particular record with READ and/or Update with a security principal (user or team). The user or team members with whom the record was shared now have that type of secured field access only on the shared secured fields on only that particular record, even if the user or team member to whom it was shared does not have a field security profile that gives them access.

A user with access to a secured field in a record can choose to share it with another user or team. The user can only give the access that they have on the record. For example, to share the record and grant Update privileges, the user must have update privileges.
You can share a secured field on a particular record with Read and/or Update with a security principal (user or team). The user or team members with whom the record was shared now have that type of secured field access only on the shared secured fields on only that particular record, even if the user or team member to whom it was shared does not have a field security profile that gives them access.

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.

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.

Only the SECURED field VALUES that you have access to REPLICATE into the OFFLINE DATABASE. If you don’t have access to the data, it is not saved offline.

Only the secured field values that you have access to replicate into the offline database. If you don’t have access to the data, it is not saved offline.

Below data and operations can be audited in CRM:

• Create, update, and DELETE operations on records.
• Changes to the shared privileges of a RECORD.
• N:N association or disassociation of records.
• Changes to security roles.
• Audit changes at the entity, attribute, and organization level. For example, enabling audit on an entity.
• DELETION of audit logs.
• When (date/time) a user accesses MICROSOFT Dynamics CRM data, for how long, and from what client.

Below data and operations can be audited in CRM:

There are thousands of attributes from all entities those can SECURED with field LEVEL SECURITY. We can get those attributes in 2 simple ways:

1. Install metada TA browser for the customized CRMs and query the entity metadata for the following properties CanBeSecuredForCreate, CanBeSecuredForRead and CanBeSecuredForUpdate.
2. Open EntityMetadata.xlsx file for uncustomized CRM and query the entity metadata for the following properties CanBeSecuredForCreate, CanBeSecuredForRead and CanBeSecuredForUpdate.

There are thousands of attributes from all entities those can secured with field level security. We can get those attributes in 2 simple ways:

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.

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.

User/Team RECEIVES the LEAST RESTRICTIVE PERMISSIONS

User/Team receives the least restrictive permissions

SYSTEM Administrator : The System Administrator field SECURITY profile gives FULL access to all SECURED fields in Microsoft Dynamics CRM. By default, all users who have the System Administrator security role have this profile. This profile is system managed and can’t be updated or deleted.

System Administrator : The System Administrator field security profile gives full access to all secured fields in Microsoft Dynamics CRM. By default, all users who have the System Administrator security role have this profile. This profile is system managed and can’t be updated or deleted.

To ensure acceptable performance and the USABILITY of the user interface, there are some limitations you need to be AWARE of when you plan to use business process flows:

• There can be no more than 10 activated business process flow processes PER entity.
• Each process can CONTAIN no more than 30 stages.
• Multi-entity processes can contain no more than five ENTITIES.

To ensure acceptable performance and the usability of the user interface, there are some limitations you need to be aware of when you plan to use business process flows:

we have TOOL synchronous event ORDER in TOOLBOX by USING we can able to update Rank of workflow.

we have tool synchronous event order in ToolBox by using we can able to update Rank of workflow.

javascript method is CLIENTSIDE program and syncronous and business rules are ASYNCHRONOUS process so javascrit execute FIRST.

javascript method is clientside program and syncronous and business rules are asynchronous process so javascrit execute first.

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

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

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 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

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”.

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 neccesary. ONE can use in-house or EXTERNAL SMTP and POP3 SERVICES.

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

E-mail router in MS CRM forms the software COMPONENT which creates an INTERFACE between the Organization’s messaging system and the microsoft dynamcs CRM DEPLOYMENT.

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

The user requires an system ADMIN or system customizer security role and MEMBERSHIP in the development ADMINISTRATOR group, in ORDER to register a plug-in with platform. WHEREAS, the user can use the web application for workflow.

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

Dialogs refers to SYNCHRONOUS processes which requires user INPUT, a wizard like interface. Where as WORKFLOW refers to Asynchronous process which requires no user input and its an BACKGROUND process

Dialogs refers to synchronous processes which requires user input, a wizard like interface. Where as Workflow refers to Asynchronous process which requires no user input and its an background process

A plug-in is an 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.

A plug-in is an 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.

Append' and 'Append To' priviledges works together. 'Append To' priviledge will allow other entities to get ATTACHED with the entity. 'Append' priviledge will allow the entity to attach the records to the entity with 'Append To' privildege.

Let us understand this with simple example:Let us say that you WANT to attach a note to a case then note entity should have 'Append' ACCESS right and case entity should have 'Append To' access right.

Let us take one more example to understand this. Suppose you have two custom entities called 'TestCustomEntity1' and 'TestCustomEntity2'. You want to attach the 'TestCustomeEntity2' records to 'TestCustomEntity1'records. For this you need to have 'Append' access right on 'TestCustomEntity1' entity and 'Append To' access right on 'TestCustomEntity2'.

Now guess will I be able to attach the records? Answer is "NO" because we need to create a 1:N relationship between 'TestCustomEntity1' and 'TestCustomEntity2'.

Now the user who has above mentioned access right in his SECURITY role will only be able to add 'TestCustomEntity2' records to 'TestCustomEntity1'.

Append' and 'Append To' priviledges works together. 'Append To' priviledge will allow other entities to get attached with the entity. 'Append' priviledge will allow the entity to attach the records to the entity with 'Append To' privildege.

Let us understand this with simple example:Let us say that you want to attach a note to a case then note entity should have 'Append' access right and case entity should have 'Append To' access right.

Let us take one more example to understand this. Suppose you have two custom entities called 'TestCustomEntity1' and 'TestCustomEntity2'. You want to attach the 'TestCustomeEntity2' records to 'TestCustomEntity1'records. For this you need to have 'Append' access right on 'TestCustomEntity1' entity and 'Append To' access right on 'TestCustomEntity2'.

Now guess will I be able to attach the records? Answer is "NO" because we need to create a 1:N relationship between 'TestCustomEntity1' and 'TestCustomEntity2'.

Now the user who has above mentioned access right in his security role will only be able to add 'TestCustomEntity2' records to 'TestCustomEntity1'.

USING DYNAMIC ENTITY.

Using Dynamic Entity.

USING Linked entity. You should always TRY to minimize the number of SWS calls that we make in the DATABASE. Often during CODE review it is explored that the number of Microsoft CRM web-service could have been reduced by making use of the Linked-entity CONCEPT. So we should always look for the opportunity to minimize the effort.

Using Linked entity. You should always try to minimize the number of SWS calls that we make in the database. Often during code review it is explored that the number of Microsoft CRM web-service could have been reduced by making use of the Linked-entity concept. So we should always look for the opportunity to minimize the effort.

 No; We will have to re-install MSCRM.

 No; We will have to re-install MSCRM.

The 21st USER will GET CREATED in MSCRM but that user will be in DISABLED state.

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

Eight.

Eight.

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".

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".

If you have multiple worker processes configured then not all of the requests are HANDLED by the same process and THUS not the same SINGLETON. so if multiple singleton are handling requests then obviously multiple OBJECTS will be created. 

If you have multiple worker processes configured then not all of the requests are handled by the same process and thus not the same singleton. so if multiple singleton are handling requests then obviously multiple objects will be created. 

Yes we can hide PARTICULAR section USING following line of code.
Xrm.Page.ui.tabs.get("tab_name").sections.get("section_name").setVisible(FALSE);

Yes we can hide particular section using following line of code.
Xrm.Page.ui.tabs.get("tab_name").sections.get("section_name").setVisible(false);

Entityname+Base , EntityName+ExtensionBase

EXAMPLE: if you created an ENTITY bank then following tables will be created at crm DATABASE new_bankbase , new_bankentensionbase

Entityname+Base , EntityName+ExtensionBase

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

When CRM creates a new user, it writes data to three different tables: [MSCRM_CONFIG].[DBO].[SystemUserAuthentication] [MSCRM_CONFIG].[dbo].[SystemUserOrganizations] [XX_MSCRM].[dbo].[SystemUserBase] The STEPS for creating the user in CRM is as follows: The first table is populated as soon as you PRESS ‘Save’. Amongst other data, the users GUID in Active Directory is added to the table. NEXT it tries to bind the user to the chosen organization. Lastly CRM POPULATES the table in wich is used to display CRM users in CRM. 

When CRM creates a new user, it writes data to three different tables: [MSCRM_CONFIG].[dbo].[SystemUserAuthentication] [MSCRM_CONFIG].[dbo].[SystemUserOrganizations] [XX_MSCRM].[dbo].[SystemUserBase] The steps for creating the user in CRM is as follows: The first table is populated as soon as you press ‘Save’. Amongst other data, the users GUID in Active Directory is added to the table. Next it tries to bind the user to the chosen organization. Lastly CRM populates the table in wich is used to display CRM users in CRM. 

• Navigate to Settings – Solutions
• SELECT the solution that you want to export
• CLICK on “Export”
• Follow the Wizard and select “MANAGED” solution type in “PACKAGE Type” page.
• Follow the remaining STEPS in wizard and save the solution