In part one of this post I wrote about the installation of Resco Mobile CRM for MS Dynamics CRM for a client using the latest version of the Woodford solution (at the time of writing 7.4). For details on that post you can use the following link: http://wp.me/p3wxxT-13
Step 1 – Launch MobileCRM Woodford: Once you have installed Woodford as per the previous steps you will need to create a new “Mobile Project”. To launch the console app’ navigate to; Settings > MobileCRM > Woodford in your CRM instance, the Silverlight app’ may launch automatically depending on your browser – if not click the “MobileCRM Woodford” icon in the CRM UX.
Within the app window you will see a number of different options in the left hand navigation pane by default, from here you can manage different app’ settings and features (as per Fig. 2 below), these include:
- Mobile Projects (this is where we create and manage of projects)
- Security (displays the devices currently accessing Woodford and the attached user IDs)
- Mobile Users (add, enable, disable users access)
- Localisations (languages)
- Geocoding (used for translating addresses to GPS data)
- About (find the build number and download updates)
To explore the administration in more detail you can download the Woodford Guide here: http://www.resco.net/MobileCRM/customizations.aspx
Step 2 – Create a Mobile Project: To start configuring Woodford, in the administration menu select; Mobile Projects > New, in the “Add Mobile Project” dialog as in the previous post you will need to select the “Type” of project you are going to be working with, you can choose between the following:
- Standard User
- External (Portal) User
- Anonymous External User
Note: we will be using “Standard User” as we will authenticate our users using their CRM credentials and security roles.
Once you have chosen a “Type” give your project a name so it can be identified from others that you may create, in this example I have used “MobileCRM Project”, you will then need to set the “Priority” used for the project, the higher the number set the higher the priority (as I understand the documentation), so ‘1’ would supersede ‘0’ etc. and finally choose the roles that will be able to access the content for the project once published. You can select one or multiple roles and you may have different projects created for different role sets so that different content is displayed, such as a Sales project and a Service project. Click “OK” so you can start to edit the project.
Note: the roles you can select should reflect those you have in CRM, including custom roles.
Now when you open the main menu for Woodford you can select the “Activate” or “Deactivate” commands or choose “Edit” to work with the project.
Step 3 – Working with CRM Entities: Once you have created and opened your Mobile Project you can begin to configure the entities from you MS Dynamics CRM instance that you will use as part of the project. You should now have a list of all available entities from your Dynamics CRM server in the left hand navigation area.
The type of entities you will want to service through the app’ will vary depending on your organisation, for example if the project has a sales focus then you typically will be looking to add; Leads, Opportunities, Accounts, Contacts and Competitors, for those with a focus on customer service you may want to work with Accounts, Contacts, Cases etc.
Note: It is worth mentioning that unless you have purchased the licensed version of Resco MobileCRM you will not be able include custom entities in your mobile project, the free version only allows configuration using out of the box entities and fields.
To select an entity to add to the project you will need to navigate to; Entities > Select Your Entity > Click Enable (in the toolbar). Once you have done this don’t forget to click “Save” to save the change. The entity will now be visible as a bold item rather than with a ‘fade’ in the left hand navigation pane, the example below is for the Lead entity. Now that we have added the entity to the project we have the option to expand it, and should be able to see the five items that will roll down: Forms, Views, Charts, Fields and Indexes.
As well as the entities display name, schema and description from CRM, there are a number of parameters visible for the entity:
Mode – If set to Online only, the data for the entity will only be available in the app’s Online Mode. If set to Online & Offline – the data of course will be available for both modes
Conflict Strategy – this is for cases when there the server and the mobile app want to modify data at the same time. Either you can set it to that the Server always wins this conflict or Device wins or it let’s the user decide (User Action).
Permissions – you can set the Read, Write, Create and Delete permission for the whole entity.
Advanced Properties – when the Include Lookup Labels is checked, the app will no longer show related data to that entity as “Unknown” in the offline mode. This often happened with Owner ID’s of records as the data with User names is stored in the User entity (by default the Owner entity is not enabled in Woodford).
Step 4 – Adding Fields: Once you have enabled your entity you can start to add fields that you want to add to your forms in Woodford, this interface is very easy to use, you can navigate through the fields associated with your entity and simply use the check box to add fields. Once you select and highlight a field you will be able to view the field “properties” on the right hand side of the app’ window.
Some of the properties displayed are ‘read only’ in this area, the field properties available include:
- Requirement Level
- Formatting (depending on field type)
- Constraints (depending on field type)
- Lookup Targets
You can amend the formatting of certain fields from your chosen entity, the formatting is changed for the fields display in Woodford only, the types of formatting include:
Single line – field is formatted to have the appearance of a single line field in the mobile app
Multiline – field will have the appearance of a multiline field
Email – the field in the mobile app will have an action button that after activating will give the user an opportunity to immediately create an email
Phone number – the field will have an action button that will activate the phone call function on the device (the device will dial the number contained in the field)
URL – an action button to open the URL in the native browser of the device will be available
Barcode – action button activates a camera so user can scan Barcodes and QR codes. Function will only work on devices that have a camera with Autofocus.
HTML – will format the text field into a HTML type (bodies of email, signatures and etc.).
Once you are done make sure to save your changes. When you are ready you can also click “Publish” to roll-out your changes, this however will largely depend on you having updated your forms, which I will try and walk through next time.
Until then, happy CRM’ing!