Here are my study notes regarding entities and fields in CRM. I hope you appreciate the picture of a field (entities and fields, get it?)
Entities and fields are probably an error where most people will have a good starting knowledge of and some experience with. Don’t get fooled into not studying the topic because there is a difference of using fields and entities and having enough knowledge to answer certification question on entities and fields.
It’s important to understand how entities and fields work and the limitations of them, e.g.
- What entities values cannot be disabled once you have enabled them?
- How does the new functionality like Image work?
- How do entities which are activities work?
- Can you delete fields referenced in a workflow?
Whilst studying these two areas I did improve my understanding of the core functionality of CRM and wrote these two blog posts
CRM 2013 – When should you create a custom activity entity?
CRM Entity ownership – How do you decide?
These notes will be added to the other study information I have created, which you can find here – MB2-703 – CRM 2013 Customization and Configuration Certification
Even if you are not studying for the MB2-703 certification, it’s interesting to have a quick read of the notes and I bet you find a fact you didn’t know
- Microsoft Dynamics CRM default instance starts with more than 260 systems entities but which many are hidden from the UI
- There are two types of entities – Custom entities and system entities
- More than 90 system entities can be customized
- Some system entities cannot be customized e.g. system job
- Entities can be created by the UI, importing records or via code using the SDK
- Entities which can be customized (system and custom) are known as customizable entities
- Not all components of a customizable entity can be customized e.g. system fields like created on cannot be deleted
- Ownership can be either user/team or organisation
- Organization ownerships does not create an owner field, there is no owner or business units
- User/team ownership adds lookup fields for business unit, user lookup, team lookup
- Entities can be owned by users or teams
- You can create custom activity entities
- Activity entities have common fields – planned started date, actual start date, actual end date, description, subject and duration
- All activity entities have a link to the ActivityPointer and can be used in the ActivityParty class
- The activityPointer allows different activities to be viewed in one view.
- Custom Entities when created by default are not viewable/usable to any users apart from System Administrator and System customizer roles. Other security roles will have to add the entity.
- Display name is the name used for the custom entity which the users will see
- Plural name is the name seen in views etc
- Name (schema name) is the customizer name, not seen by end users
- Primary image selected will add a field called image and will allow one image to be added to a each record of the custom entity.
- Primary image, once ticked cannot be unticked
- IF an entity is selected as an activity this cannot be undone
- The primary field is always a single line of text
- Entities in a lookup field will display the primary field value
- Areas that display this entity are areas where the entity will be visible. Changes will be written to the sitemap not part of the entity.
- Additional entity options
- Business process flows – this will create extra fields and cannot be turned off
- Notes, activities, Business process flows, connections, Queues, sending email cannot be disabled if selected
- Allow Quick Create – allows quick create forms which are minimized forms with important fields
- Some default entities have Allow quick create disabled and cannot be enabled.
- CRM For Phones, CRM for tablets, if selected the entities will be available on phones and tablets.
- Renaming entities is not straight forward, labels, reports and views will also need to adjusted
- Custom entities can be deleted if all dependencies have been removed
- System entities cannot be deleted
- CRM 2013 has a maximum of 1023 fields
- For some fields Microsoft adds other fields e.g. currency adds extra fields for Base Currency, exchange rate, currency value and base currency value.
- IN CRM 2011 and earlier the SQL structure was held in two tables. The base table holds the system fields and the extended tables holds the custom fields. A filtered view was created to show both tables in one view.
- CRM 2013 the two tables are merged but the filtered view is the same.
- The filtered view has been persisted to support reports written using it.
- The filtered view takes into account a user security roles and permissions
- Be careful adding lots of fields to an entity, there are constraints on the SQL database table and views.
- Single line of text can have the format of Email, Text, Text area, Url, Ticker Symbol, Phone
- Single line of text can be between 100 characters to 4000
- IME mode is for Chinese, Korean and Japanese characters
- IME Mode has four modes – Auto, Active, Inactive, Disabled
- Option set – Use Existing option Set if set to yes uses a global option set values
- Two options are always stored as 0 = no – 1 = yes
- Two options will always have a value and cannot be null
- Two options can be formed on the form to be Two radio buttons, Check box or list
- Whole numbers are the SQL server equivalent of an integer (no decimal)
- Whole number format = none, Duration, Time Zone, Language
- Whole number duration is held in minutes
- Floating points can contain a decimal
- Floating numbers are rounded, which means they can be rounded up/down and liable for small rounding errors.
- Floating number precision refers to the number of digits after the decimal, max = 5
- Decimal number is not rounded
- Decimal number precision max = 10
- When a currency field is added to a form, if it’s the first currency field then additional fields of exchange rate, currency, price and base price are also added.
- Currency precision is between 0 and 4.
- Multiple line of text field max length is 1048576 characters
- Date and time field can have the format of Date only or date and time.
- 24 system entities can have the new image field
- Account, Contact, Lead, Product, Competitor, resource, publisher and user have image enabled by default.
- You can add a maximum of one image field to a custom entity
- It is not possible to add an image field to a system entity.
- The entity image will always have the default schema name of entityimage (with no publisher prefix)
- The fixed schema name – entityimage stops more than one image field being added to a custom entity.
- Image field max size is 5 Megabytes
- Image file extensions supported are jpg, jpeg, gif, tif, tiff, bmp, png
- Uploaded images are resized to 144 x 144 pixals
- Field requirement levels are – optional, Business recommended, Business required.
- Requirement levels are form validation only. Importing and plugins do not have to supply data to business required fields
- Fields have a searchable property, if this is set to know the fields will not be displayed in advanced finds
- Auditing for fields can be turned on or off at any time.
- You can bulk edit fields to set Field requirement, Searchable and auditing properties
- Local option set is only available on one form
- Global option sets can be used in multiple forms.
- Custom and system entities have Status and Status Reason fields
- Status is active/inactive
- Status reason (schema name statuscode) has the reason for the status
- Status reason is an optionset of values for each status
- You cannot delete a field without removing all the dependencies first.
- System fields cannot be deleted.
- Fields which are referenced in workflows or dialogs cannot be deleted.
I have been working on creating some questions for all the security section for the MB2-703 -CRM 2013 Customization and Configuration certification.
I have created some quick fire – True or False questions to test your knowledge on the security section of the certification.
I have already created some questions for Solutions which you can find on the link below
Blog – Solution Test Questions
Video – Solution Test Questions
I have uploaded a power point file into slide share because this is a really easy and quick way to do the question. The security section was so large there are 27 questions and doing these should take you more than a few minutes. So test your knowledge
I go through the questions with some explanation in the video below
Don’t forget all the MB2-703 studying information can be found here
This blog contains the study notes for the MB2-703 – CRM 2013 Customization and configuration exam and for the area of Security.
Security covers a lot of topics and is worth 10-15 percent of the final exam marks, so you definitely need to know the functionality and limitations of security.
I have gone through the separate parts of security in the blogs below and there are videos going through these which you can find on the youtube playlist
All the study notes for the MB2-703 exam can be found on the page link above or clicking the link below
These notes are the to revise the key concepts of security for the MB2-703 – Microsoft Dynamics CRM 2013 Customization and Configuration certification
There is a video going through the list below with some explanation
Business Units and Security Roles
- When a business unit is disabled the users in that business unit cannot access CRM
- users of a disabled business unit will still consume a CRM Licence
- child business unit users will also not be able to access CRM
- the records of a disabled business unit user are not disabled.
- To delete a business unit you must remove all child business units and any users or teams linked to the business unit
- To delete a business unit you must disable it first
- Each business unit has a default team of the same name
- you cannot add users to a default business unit team
- you cannot delete a default business unit team
- Equipment/Facilities and Resource Groups do not need to be removed before you can delete a business unit
- business units can have separate security roles, even with the same name!
- 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.
- moving business units is done by changing the business units parent
- The Root business unit is a default business unit which has the same name as the organisation.
- You cannot delete the Root business unit, you cannot disable it
- You cannot create a business unit above the Root business unit, e.g. you cannot give it a parent.
- Business units are used to create a hierarchy and this is in a tree structure. The Root business unit will be at the top.
- none of the data is affected by disabling business units, its only the users who cannot then log in but it is important to take into account all the child business units will also be disabled. This only applies to inherited roles. Roles that are created in a BU explicitly will move with it
- The users are not disabled but cannot login into CRM whilst the business unit is disabled. As soon as the business unit is enabled they will be able to log into CRM again.
- if you want to delete the business unit then you will need to change all the users/teams that are assigned to that business unit. You also need to disable the business unit before you delete it.
- You cannot delete the default business unit team but it won’t stop you deleting the business unit because this will be deleting automatically when you delete the business unit.
- When you disable a business unit, it disables all child business unit. The users in these business units will not be able to login
- When you change the parent of a business unit, it removes and rebuilds all the security roles of the inherited security from the parent business unit. So all the users in the business unit will have no security roles and they will not be able to login
- Users can login if they are part of a team which has security roles. They won’t be able to set any personal options.
- You can change the Name of a business unit.
- You Can change the name of the root business unit.
Security Roles and Teams
- if a user doesn’t have a security role he cannot access the system, so every user must have at least one security role.
- Security roles are linked with the user business unit to calculate what records the user can access.
- Users receive their permissions to work on records or use features based on the combination of Security Roles they are assigned and the Business Units to which the users belong.
- Security roles can also be assigned to teams and if the team a user is a member of has higher security privileges then this will override their individual security roles. The user will also use the highest security levels it is assigned, whether that’s from a security roles assigned to the team or individual security role
- Users can be assigned multiple security roles, this means it’s possible to create security roles just for single purposes.
- There are 15 default security roles in CRM
- The default security roles are all created in the root business unit.
- A security role stays in the business unit it is created in and they copy down to any child business units.
- if you create a security role in the root business unit then the security role will be copied to all the child business units below it.
- User can be assigned any security role which exist in their business unit.
- only security roles which exist in the root business unit can be added to a solution file.
- it’s quicker to modify existing security roles than create new ones
- All security roles are the same except the System Administrator role which is a super role.
- The System Administrator role automatically has access to all records and entities, including all custom entities. It has the default access level of organisation for all privileges.
- At least One user must have the System Administrator role, this is by default given to the user who installed CRM
- Multiple users can be assigned the System Administrator role and you can remove the role from users but you cannot remove the role if that user is the only user who has the System Administrator role.
- The System Administrator role also is given the System Admin field level security role, which as I’m sure you can guess gives them access to all field level security.
- It’s possible to copy the System Administrator role and it will create a security role but the security role will not automatically have access to any new custom entities added and it basically won’t have the special powers of the System Administrator role.
- Teams have security roles (this can affect which form is used)
- There are some privileges which do not have organisation levels these are always show under miscellaneous privileges and these are either true or false. These are things like
Export to Excel
Manage user access, Teams and sharing
- The security authentication in CRM is not really handled inside CRM. A bit like the way CRM lets outlook/email router do all the emailing, CRM also gets another piece of software to do the authentication of users.
- the most common authentication method is active directory
- You can also used Internet facing deployment (IFD) where the authentication is either AD FS (active Directory Federation Services) or STS (Secure Token service)
- Online security – Microsoft Online Subscription Program (MSOP)
- A user can have one manager which is a user lookup field on user record
Functionality to manage users and you can find these by going to Settings – Administration
- Creating users, teams, Security Roles
- assign/move users to teams, assign security roles to teams and users
- Disable business units
- Delete Security roles, Delete teams
- Move users between teams
- You cannot delete users in CRM you can only disable them
- If you disable a user the user won’t be able to log into CRM
- a disabled user doesn’t use a CRM license
- The records assigned to the user are still active. Best practice is to assign all the records assigned to the disable user to another enabled user.
- You need to work out if the user is used in the workings of any workflows, these will still work but it’s not good practice to assign records etc to an disabled user.
- Users must always be assigned to business unit and can only be assigned to one business.
- Security roles and teams security roles are additive, so adding a user to a team won’t remove any security privileges to the user
- Teams are optional
- Two types of teams Access teams and owner teams
- Owner Team can own records
- Owner Teams can be assigned security roles
- Access teams cannot own be assigned security roles or own records.
- An owner team can be converted to an access team
- An access team cannot be converted to an owner team
- Each business unit create a default team which you cannot delete and you cannot add members to
- Teams can be assigned security roles
- Team and users can be the owner of records
Business units and default owner teams
- Business units have a team created automatically, the team name will have the same name as the business unit. Any members created and assigned to the business unit will automatically be added to the default business unit team.
- It’s a dynamic team which CRM keeps up to date.
- It cannot be edited but you can assign security roles and these security roles will apply to all members of the business unit.
- default business unit team cannot be re parented, deleted or renamed and it’s members cannot be modified.
- In CRM you can share records between users and teams. Sharing gives the user being shared to the same privileges to that individual record as the user who is sharing.
- Sharing bypasses business unit – access level parts of security because when you share records it basically ignore the level (organisation, business unit, user)
- Sharing records to a team is like sharing the record with every member of the team, except in the PrincipalObjectTable this is only one entry
- using the business unit default team you can share records to all users in different business units.
- You can share more than records, you can also share Charts, Views and Dashboards.
- Users can only share their personal views, charts and dashboards.
- When a user shares the components (charts, views and dashboards) they also choose what privileges you want the user/team to have with the component
The privileges you can share are
- Re-parenting a user/teams business unit has a drastic effect on the security roles the user or team had, it REMOVES THEM ALL.
- So if you ever change a user/teams business unit you will need to assign the user or team some security roles in the new business unit.
- This sounds drastic but it actually makes sense if you think about it logically. Each business unit has it’s own set of security roles, these are usually copied down from the parent business units. So when you move business unit, it removes all the security roles and it can’t automatically add them all back because not all the security roles may exist in the new business unit or the security roles could be vastly different with completely different privileges, so the user must add new security roles.
- This is also true if you re-parent a whole business unit because all the users will have had all their security roles removed.
- Remember users without security roles cannot log into CRM.
- If a user is re-parented they lose their security roles but they won’t be removed from any teams, this would probably allow them to login to CRM but the user won’t be able to change any personal settings, or view any components the user created.
- If a team is re-parented then every member of team will lose all their security roles because the team will have had all it’s security roles removed.
- An efficiency trick is if you want to remove all the security roles for a user or team is to move business unit
- Auditing has three levels – Global, Entity, Field
- Auditing is enabled in System settings and then for each individual entity
- Any entity can be audited
- if auditing is not enabled at organisational level, it doesn’t matter if auditing is turned on at an entity level, nothing will be audited.
- audit logs are partitioned every 3 months. These can be deleted in the audit log management screen
- User has to have the View Audit History privilege
- when you turn on auditing for an entity, all the available fields are by default enabled for auditing
- Audit logs management is done by a system job
- Some System fields are not applicable for auditing
Owning Business Unit
Access Teams and Access Team Templates
- Access teams are new functionality added in CRM 2013 (so expect some questions)
- Access Teams and Access team templates are a method to share permissions and records, which is easier to manage, quicker to add/remove users/teams because Access team templates will applying a standard set of privileges (read, write, delete, append, append to) rather than having to set this up for each individual user/team.
- Access Team templates are enabled on an entity basis and you have to enable Access Teams on the entity in the communications and collaboration section
- Access teams can be ticked and un ticked on an entity (unlike Queues)
- You need to customize the form of the entity you want to add the Access Team Template to and in my case it’s the account form
- You need to add a sub grid to the form
- Records – All TypesEntity – UsersDefault View – Associated Record Team MembersTeam Template – Hosk Account Access Team – this is the team template I created in the step before, yours is probably called something different.
- When you add a user to the user grid it will automatically create an Access Team but the odd things is you can’t view this team in the Teams section in Administration
- You can view access teams by using the advanced find, search for Teams and choose of type Access.
- You add users to the access team via the sub grid on the record.
- you can add users directly to the access team.
- You can more than one Access Team template for each entity
- The default number of access teams templates for each entity is two
- The number of access team templates you can have for each entity is controlled by theMaxAutoCreatedAccessTeamsPerEntity deployment setting.
- MaxEntitiesEnabledForAutoCreatedAccessTeams deployment setting has a default value of 5. This controls the number of entities it’s possible to enable for auto-created access teams.
- You can change the MaxEntitiesEnabledForAutoCreatedAccessTeams , MaxAutoCreatedAccessTeamsPerEntity only on Premise installations and you cannot edit them for Online.
- A system generated Access Team isn’t created for each record until you add a user to the sub grid on the entity.
- if you delete the team, this is the same removing all the members in the sub grid on the record.
- if you change the access rights on Team Template this will only change the access right to new entity records/access teams. Any records already created will use the previous set of privileges.
- Access teams with Share access right ticked will mean any user who is in access team will be able to add (share) others to the access team for that record.
- Users cannot grant privileges they do not have. So a user can only add new members to an access team where the access team template has delete privilege only if that user has the delete privilege for the entity.
- Access Teams created automatically by adding users to them are not shown in the system team views
- If you want to delete a Access Team Template you will need to remove all the sub grids using that specific Access Team Template before you can delete it.
- Owner teams in Microsoft Dynamics CRM can have security roles
- Team can own records
- Access teams cannot be granted security roles
- Access teams cannot own records
- Accesses records through sharing
- Sharing privileges are defined by an access team template but don’t change dynamically for existing records if the template changes
- Access teams are not displayed in most system views
- You can add/remove users directly on the subgrid of the record you want to share access to.
Field Level security
- Enabling or disabling of field level security by setting the IsSecured attribute cannot be audited.
- System Admin is has all privileges on all field level security fields, the user has a System Administrator field security profile where all values are set to yes and will be for any fields checked for field level security.
- Every field enabled for field level security is added to all field level security profiles
- when you turn on field level security for a field, it will automatically be added to all Field Level security roles with Read, Create and Update all set to No.
- New field level security fields can only be seen by users with the System Administrator role, so you have to go and configure the field level security privileges.
- Every field level security profile will include all fields with field level security enabled.
- Fields that are ticked for field level security will be added to field security profiles but with Read, Update, Create all set to No, so you must go in to configure
- users/teams can be added to more than one field level security profile.
- *** asterisks show if a user does not have read access to a field
- *** asterisks show even if the field is null/blank
- You cannot delete the System Administrator field level security profile
- You can only set field level security on custom fields!
The best way to prepare for an exam, is to take practice questions and test your knowledge with questions in a similar way the exam will.
I have created a YouTube video where I go through the questions and explain the answers, I would definitely recommend watching that for the first time at least
So with this in mind I have created some questions for you.
I have also created the questions as slides, which you have seen in the video
Multiple choice questions
Quickfire Yes/No Questions
HOSK’S TEST SOLUTION QUESTIONS
- Which statements are true about solutions?
- Saving your changes in a solution is mandatory
- It’s possible to export the Default Solution
- You cannot create more than 50 solutions
- Publisher is a mandatory field on a solution
- Which components can be added to a solution
- Business Rule
- Business Unit
- Which components cannot be added to a solution
- Service Endpoint
- Site Map
- What is true about solutions
- Deleting an unmanaged solutions doesn’t delete the components if there is data for them.
- Deleting a managed solutions deletes the components and the data
- You can only export the default solution as an unmanaged solution
- You can add plug-in assembly to a solution
- What is development and not customization or configuration from the list below
- Create a plug-in to run on the creation of an account to set reference number
- Create a custom entity to hold venue information
- Creating a business rule to disable a field until another field has a value
- What is removed when you delete an unmanaged solution in CRM 2013
- Just the solution record
- The solution record, the components and all the data
- The solution record and the components
- The solution record, it’s components and dependant components.
- What does the Version number show
- you import a managed solution which contains the account entity, you then import an unmanaged solution which also contains the account entity, both solutions change the Account Number field to have a different name, what name is on the account form
- Account Number, you cannot change the name of the account number
- The name given to Account number in the managed solution
- The name given to the Account Number in the unmanaged solution
- The name given in the solution which was imported last
- Which of the below is true
- You cannot export the Default Solution
- You can export the Default Solution from CRM OnPremise to CRM Online
- You need a special security privilege to import solutions
- Unmanaged solutions have to be published
- What is false about managed solutions
- Managed solutions can only be changed or altered by the publisher
- importing a managed solution is automatically published
- Managed solutions have versioning, unmanaged solutions do not.
- managed solutions are additive, you cannot remove any components by importing a managed solution
- C, D
HOSK’S QUICKFIRE QUESTION (YES/NO)
- Can you export a managed solution
- Can you export an unmanaged solution
- Can customization and configuration be used and refer to the same components.
- The correct format for version is major.minor.revision.build
- Subjects can be added to a solution
- There is no limit to the number of solutions you can create
- The prefix in the publisher is added before schema name for entities, fields
- The changes to components when importing an unmanaged solution cannot be undone
- Queues can be added to solutions
- managed properties are customizable by default
- It’s not possible to export an unmanaged solution
- managed solution must be published after importing
I have been seeing more and more tweets and blogs about people passing the CRM 2013 exams, I am just starting to study for the CRM 2013 Customization and configuration exam. Below are the links to prometric exams
MB2-700 – Microsoft Dynamics CRM 2013 Applications
MB2-701 – Extending Microsoft Dynamics CRM 2013
MB2-702 – Microsoft Dynamics CRM 2013 Deployment
MB2-703: – Microsoft Dynamics CRM 2013 Customization & Configuration
There is also some CRM Online specific certifications that I have heard about but I’m not sure when they will be released and I can’t see how different they are going to be from the normal certifications in terms of configuring and customizing CRM.
- MB2-721: Microsoft Dynamics CRM Online Fall Customization and Configuration
- MB2-722: Deploying Microsoft Dynamics CRM Online
There is some student training materials available for those with partnersource account. The download link is at the top right of the page. I find the training below the most useful, it’s free and goes through all the main criteria in the exams
Customer Service in Microsoft Dynamics CRM 2013
Sales Management in Microsoft Dynamics CRM 2013
This course introduces the capabilities of Sales Management in Microsoft Dynamics CRM 2013 that allow you to track and manage the sales process from potential to close. This course provides insight on sales process information, and introduces the tools available to analyze and report on sales information.
This course guides you through the tools that help make the internal processes simpler and easier so your sales force can focus on what is important—creating a differentiated experience for your customers
This course focuses on how an organization can nurture customer satisfaction through automation of business processes within Microsoft Dynamics CRM 2013. This course provides an insight into all of the powerful Customer Service and Service Scheduling functionality capabilities within Microsoft Dynamics CRM 2013.
Additionally, this course guides you through the process of working with your customers in Microsoft Dynamics CRM 2013, including: resolution of customer complaints and services issues cost effectively, and provides insight on managing all related correspondence, documents, contacts and conversations. This course demonstrates the rich and relevant view of your customer that provides your team with actionable insights, including the use of knowledge management in a centralized knowledge base.
Customization and Configuration in Microsoft Dynamics CRM 2013
This course describes the techniques required to customize Microsoft Dynamics CRM to meet the specialized needs of businesses. The topics covered include security; creation and configuration of entities; design of forms views and charts; auditing and solutions. The course describes each topic and how each topic relates to the other topics to produce a full configured, effective solution.
Installation and Deployment in Microsoft Dynamics CRM 2013
This two-day training course provides individuals with the skills to install and deploy Microsoft Dynamics CRM 2013. The training material focuses on the components used within a Microsoft Dynamics CRM deployment, the hardware and software requirements needed to successfully deploy Microsoft Dynamics CRM, and the installation instructions for the primary Microsoft Dynamics CRM components: the Microsoft Dynamics CRM Server, the E-Mail Router, and Microsoft Dynamics CRM for Office Outlook. The course also covers upgrading from earlier versions, configuring an Internet-facing Deployment and administration tasks.
I am (still) studying for my the Extending CRM 2011. The links below are for people who have access to partner source, reading the courses below and the CRM 2011 SDK should definitely prepare you for the exam.
The courses will lead you to a site where you can download the course in pdf files and then work through them. These courses are usually the only thing I use when study for a CRM exam
Extending Microsoft Dynamics CRM 2011
Course Number 80295
This training offers detailed and interactive information on how to develop extensions for Microsoft Dynamics CRM 2011, with focus on extension methods documented in the Microsoft Dynamics CRM SDK. It provides details on the use of a number of Common Platform Operations, on how to query and execute these operations, as well as on developing a concise understanding of business process implementation and workflows. In addition, the training describes the use of Plug-ins, application event programming, client extensions and web resources. Finally, it includes a summary overview of the integration between Windows Azure and Microsoft Dynamics CRM 2011.
- Describe how Microsoft Dynamics CRM 2011 is extended and the core extensibility features.
- Use common methods to access system and custom entities, including the Security Model, business logic, xRM Framework and exceptions.
- Execute queries in the Microsoft Dynamics CRM database including QueryAttribute, QueryByExpression, LINQ, FetchXM, filtered views and OData.
- Explain how the Organization Service web service interacts with Microsoft Dynamics CRM metadata.
- Develop custom workflow activities for use within Microsoft Dynamics CRM that run code when configured workflow or dialog rules are created.
- Debug custom workflow activity code and use declarative workflows for On-premise deployments.
- Use Plug-ins to extend the functionality of events for any entity in Microsoft Dynamics CRM 2011.
- Understand the integration between Windows Azure with Microsoft Dynamics CRM 2011.
- Use the built-in features of the Microsoft Dynamics CRM application and understand how the Dynamics CRM application behaves when forms are loaded or saved, field data changed, tabs change state, and when IFRAMES are loaded.
- Add custom buttons, menu items and modifications to the navigation areas, including interaction with the Site Map and the Ribbon.
- Use web resources to enable the storage of shared blocks of code or resources for reuse across the Microsoft Dynamics CRM web application.
Workflow and Dialog Processes in Microsoft Dynamics CRM 2011 Course Number 80444
A customer source license is required to access this material.
Reporting in Microsoft Dynamics CRM 2011 Course Number 80445
A customer source license is required to access this material.
since I blogged about passing the 2011 Presales Assessment, I have had a few emails and comments asking about where people can find information regarding this exam.
The reason quite a few people are interested in the exam is because Microsoft have started to insist a certain number of people pass the certification to have silver or gold partner status.
Microsoft are also a bit cheeky because the best sources of information are class led lessons which you have to pay, so not only are people wanting to learn how to sell Microsoft products but Microsoft want people to pay them to learn how to do so, Clever but cheeky.
All of the source material is on partner source but the test might not be
The test can be found here
you can take this test as many times as you like. It’s 50 questions long and it probably has 100 different questions (at a guess). One tip I used was to screen shot a correct answer (it shows the correct answer straight away) and then you can check the answer on the next test run.
You won’t be able to guess all the answers, you will have to watch, read some of the study material for the exam.
here is the preperation guide
On Demand Presentation: Microsoft Dynamics Presales Exam Preparation Web Seminar | Downloads PDF – 2.50 MB
2011 Sales Assessments:
This page is fantastic, probably the most useful link on this blog page. You can see below it basically shows you all the links to the free online videos. My personal recommendations is you will definitely need to know about sure step and how it’s used in presales, the video 65 minutes long but very interesting and a good introduction to Sure Step 2010 for those who need it.
Good luck and keep practising that test.
Assessment Preparatory Course*
|How to sell Microsoft Dynamics CRM 2011
ILT (8 hrs)
|How to Upgrade Existing Customers to Microsoft Dynamics CRM 2011 (available in April)
|Selling the Business Value of Microsoft Dynamics CRM 2011
|Application: What’s New in Microsoft Dynamics CRM 2011
On-demand (5 hrs)
|Click-through demos for Microsoft Dynamics CRM 2011
|Compete to Win: Microsoft Dynamics CRM against Salesforce.com
|Managing Microsoft Dynamics CRM Online 2011 Trials from “Click to Close”
|Microsoft Dynamics CRM Online 2011: Pricing and Licensing
|Microsoft Dynamics CRM 2011: On-premise Pricing and Licensing
|Microsoft Dynamics CRM 2011 Data Management New Features
|Microsoft Dynamics CRM 2011 E-mail New Features
|Microsoft Dynamics CRM 2011 Mobile New Features
|Microsoft Dynamics CRM 2011 Outlook Client New Features
|Microsoft Dynamics CRM 2011 Reporting New Features
|Partner Sales Opportunity with Microsoft Dynamics CRM Online