Microsoft Dynamics CRM Customization & Configuration

In Microsoft Dynamics CRM 2011, the default security settings for custom entities are that the System Administrator and System Customizer roles have full access. This means that these roles have the ability to create, read, update, and delete records in the custom entities. Other roles, on the other hand, do not have any access or have read-only access to the custom entities.

To move a business unit in the Microsoft Dynamics CRM organizational hierarchy, you should change the business unit's parent business unit. This means assigning a new parent business unit to the business unit you want to move. By changing the parent business unit, the business unit will be repositioned in the organizational hierarchy accordingly.

Microsoft Dynamics CRM 2011 does not support modifying the website files and settings of the CRM. This means that users cannot customize the CRM by directly editing the website files or changing the settings related to the website. However, other types of customization such as customizing the schema, automating business processes through dialogs, creating entities, fields, forms, and charts, and extending CRM using application event programming are all supported by Microsoft Dynamics CRM 2011.

In Microsoft Dynamics CRM 2011, you can create field-level security profiles with privileges to data in both custom fields in standard entities and custom fields in custom entities. This means that you can define specific security settings for these fields to control who has access to view, edit, or delete the data in those fields. However, you cannot create field-level security profiles for standard fields in either standard entities or custom entities.

In Microsoft Dynamics CRM 2011, the change to block file extensions on attachments is made in the system settings. This allows for a centralized approach to managing file extensions and ensures that all users are subject to the same restrictions. By making this change in the system settings, it applies to all attachments across the CRM system, regardless of the specific user or email settings.

The correct answer is "Organization Read access and User Create access." This is because the requirement states that users should be able to view Conferences owned by any user, which indicates the need for Organization Read access. Additionally, users should not be able to create Conferences owned by other users, so User Create access should be granted instead of Business Unit Create access.

When a business unit is disabled in Microsoft Dynamics CRM 2011, the users assigned to that business unit will not be able to log on to the CRM system. Additionally, the users assigned to any child business units that are subordinate to the disabled business unit will also not be able to log on to the CRM system.

Both Microsoft Dynamics CRM 2011 on-premises and Microsoft Dynamics CRM Online 2011 allow offline synchronization with Microsoft Outlook 2010.

To attach a note to an organization-owned custom entity in Microsoft Dynamics CRM 2011, the user needs to have the "Append" privilege on the Note entity, which allows them to add notes, and the "Append To" privilege on the custom entity, which allows them to associate the note with the custom entity. These privileges ensure that the user has the necessary permissions to perform both actions required to attach a note to the custom entity.

The Share privilege in Microsoft Dynamics CRM 2011 allows users to share records with other users and other teams. This means that users can grant access to specific records to other individuals or teams within the organization. However, the Share privilege does not allow sharing with any child business unit or any other business unit.

A task-based privilege refers to a specific permission or authority granted to perform a particular task or action. In this context, "Publish Articles" is considered a task-based privilege as it grants the user the ability to publish articles. This privilege is typically given to individuals who have the responsibility or role of creating and sharing content on a platform or website.

After installing a Microsoft Dynamics CRM 2011 managed solution, you cannot remove solution components from the managed solution. Deleting the managed solution will uninstall all of its solution components.

The correct answer is the Pricing Decimal Precision system setting. This setting allows you to configure the decimal precision for all currency fields in the organization. By setting the Pricing Decimal Precision, you can ensure that all currency calculations and display values adhere to the desired precision level. The Precision setting on each currency attribute, the Personal Standards and Formats setting, and the Organizational Standards and Formats setting may affect other aspects of currency display and formatting, but they do not specifically control the decimal precision for currency fields.

When adding a user to Microsoft Dynamics CRM 2011 using the Add User wizard, only the security roles contained in the business unit of the new user are available. This means that the user can only be assigned security roles that are specific to their business unit, limiting their access and permissions within the CRM system. The option of selecting both built-in and custom security roles or adding security roles after the user is created is not available in this scenario.

Creating a custom security role in the new business unit is the correct answer because it allows you to create a security role that is tailored specifically for the new business unit. Copying and modifying the existing security role may not be ideal as it may not align with the unique requirements of the new business unit. Linking the existing security role or sharing it with the new business unit would not create a separate security role for the new business unit.

In Microsoft Dynamics CRM 2011, when creating a solution, you can add new solution component types such as entities and connection roles. Entities represent the various data objects that can be managed within CRM, while connection roles define the relationships between different entities. These components are essential for designing and customizing the CRM solution to meet specific business requirements.

The Salesperson security role can be assigned to the new user in two possible ways. Firstly, the role can be assigned to the user upon creation, ensuring that the user has the necessary permissions from the start. Secondly, the user can be assigned to a team that already has the Salesperson role assigned, allowing them to inherit the permissions associated with that role.

The Microsoft Dynamics CRM 2011 platform includes features such as raising events for workflow processes, controlling access to objects through security, and controlling access to the database through the data access layer. These features allow users to automate processes through event triggers, manage and restrict access to data and objects based on user roles and permissions, and control data access at the database level. Additionally, the platform allows for the enforcement of required custom fields on records, ensuring that important data is captured and populated correctly.

The Microsoft Dynamics CRM system settings manage the minimum times for synchronization processes and the interval between sending Microsoft Dynamics CRM email messages. These settings are controlled by the CRM system and can be configured to meet the organization's needs. The synchronizing client and the process of updating parent accounts when contacts synchronize are not managed by the CRM system settings.

The Can be customized managed property can be edited for a custom component that is part of a default solution and a custom component that is part of an unmanaged solution. This means that if you have created a custom component and included it in either a default or an unmanaged solution, you have the ability to edit the Can be customized managed property for that component.

To implement a managed solution in Microsoft Dynamics CRM 2011, the user needs to have the following privileges:
1. Read privileges for the Solution entity: This allows the user to view and access the solution entity, which is necessary for implementing a managed solution.
2. The Import Customizations privilege set to On: This privilege enables the user to import customizations, including managed solutions, into the CRM system.
3. The Publish Customizations privilege set to On: This privilege allows the user to publish the customizations made, including the managed solution, making them available for use by other users.