CRM 2011 – Hosk’s Study notes – CRM 2011 Customization and configuration

These are some of the notes I have made whilst studying for the CRM 2011 customization and configuration exam.  They are not in any order or in much detail.

They are final notes before you take the exam.

They are basically exam cram notes

• a maximum of 2 columns can be used to sort a view
• The CRM Administrator can see everything
• Audit logs management is done by a system job
• decimal precision is set on each currency attribute AND in system settings
• Connection roles, security roles, optionsets, Web Resources, templates, field security profiles are all included in Solutions
• editing CRM website files is unsupported
• Auditing is enabled in System settings and then for each individual entity
• business units can have separate security roles, even with the same name!
• When assigned a security role to a user, the choice is filtered by business unit and the security roles in that business unit
• Disabling a business unit (and child business units) will mean all the users in that business unit won’t be able to login to CRM.
• Teams have security roles (this can affect which form is used)
• moving business units is done by changing the business units parent
• Managed solutions cannot be exported
• unManaged solutions can be exported
• Managed solutions can be deleted, this will delete the solution and all the entities and data
• Managed solutions can’t be changed or altered, except by the publisher/owner
• There are privileges needed to import a solution and publish it.
• Managed solutions use managed properties
• Managed solutions automatically publish on import, unmanaged solutions have to be published
• when you delete a managed solution you are only deleted the solution file, all the changes stay.
• To add 3d effects or modify charts you need to export the chart, change the XML and then import it.
• Optionsets can be used by many entities
• Many to Many relationships can be either Manual or Native
• Native many to many (N:N)  is done automatically by CRM (it creates the intersect entity but hides it)
• Manual Many to Many relationships are done manually an entity to sit between the two entities and have a 1 to many relationship with them both.
• Custom fields can be used for field level security
• built in fields cannot be used for field level security
• Each form has a fallback form
• A Teams  security role can influence what form is used
• Queue functionality cannot be unticked once it has been ticked
• Relationships – Cascade active – assigns active entities
• Relationships – Cascade all – assigns all entities
• Primary keys, created by, creation on, modified on cannot be audited
• Find columns are set in the Quick Find view for entities
• Business required fields don’t have to have a value if they are not included on a form
• importing data does not go through the same validation (e.g. business required) because validation is done only on the forms.
• an entity can only have one 1:M (one to many) parental relationship
• Display option must be filled in for Many to Many relationships
• WEB RESOURCE – Silverlight  XAP
• WEB RESOURCE – Web page HTML
• WEB RESOURCE – Script (JSCRIPT)
• WEB RESOURCE – Data (XML)
• WEB RESOURCE – Style Sheet (XSL)
• WEB RESOURCE – graphics – JPG, PNG, GIF
• Mapping fields must be the same type
• mapping optionset values must be the same
• APPEND – the entity you want to append
• APPEND TO –  The entity have things appended to it
• fields used in reports do not create a dependency and can be deleted