Navigation

• Main Page

• What's New
• All Pages
• Categories

• Login/Logout
• Language Selection
• Your Profile
• Create Account

Quick Search Advanced Search »

Table of Contents [Hide/Show] 1 - This Document 2 - Resources 3 - Mobile Configurator 4 - Entities    Add an Entity    Delete an Entity    Publish an Entity 5 - Profiles    Add a Profile    Delete a Profile    Copy a Profile    Import/Export a Profile 6 - Users    Add a User    Edit a User    Delete a User 7 - Views    Add/Edit a View        Change View Properties        Edit Filter Criteria        Configure Sorting        Add Columns        Change (Column) Properties        Remove (a Column)    Delete a View    Import/Export a View 8 - Forms    Add/Edit a Form        Change Form Properties        Add Fields        Add Tab/Label        Add Custom Control        Change Properties        Change Field Properties        Related        Remove    Delete a Form    Import/Export a Form 9 - Filters    Add/Edit a Filter    Delete a Filter    Import/Export a Filter 10 - Troubleshooting    Log files    I see a red status bar at the bottom of the main menu.       Registered Name doesn't match.    I get an error message when I try to delete an entity from the entity list.    I get an error message when I try to delete a profile.

Edit

1 - This Document

This document describes how to configure your Mobile CRM 4.0 application (for Dynamics CRM 4.0). It gives you all the information you need to implement your own customized Mobile CRM solution using the Mobile Configurator tool.

Edit

2 - Resources

Here are some resources that might be useful if you require further information.

First of all, if you find any errors in this document, have comments and/or suggestions, we highly appreciate your feedback! Please send your feedback to support at cwrmobility dot com or leave them on the discussion page and we’ll use that to improve our documentation.

CWR Mobility website : http://www.cwrmobility.com

Microsoft Dynamics CRM 4.0 SDK : http://msdn.microsoft.com/nl-nl/library/cc160840(en-us).aspx

Optimizing and Maintaining Microsoft Dynamics CRM 4.0 : http://www.microsoft.com/downloads/details.aspx?FamilyID=ba826cee-eddf-4d6e-842d-27fd654ed893&displaylang=en

Edit

3 - Mobile Configurator

With the Mobile Configurator an administrator can manage virtually every aspect of the CWR Mobile CRM application from within the Microsoft Dynamics CRM web interface. The Mobile Configurator can be accessed via the Settings - CWR Mobile CRM menu.

In the main menu the administrator can choose to manage the following aspects: Users, Entities, Profiles, Views, Forms and Filters.



Edit

4 - Entities

The first step in configuring CWR Mobile CRM is selecting the entities that can be made available on the mobile client. When you click on the Entities menu item you go the mobile Entities overview. From this overview you can Add, Delete and Publish entities.



Edit

Add an Entity

When you click on the Add button in the menu bar a popup window appears. Here you can select an entity from a list of available entities in CRM. This includes custom entities that you’ve created yourself. After selecting an entity and clicking OK the entity is added to the list of mobile entities. The entity is now ready to be used in Profiles.



Edit

Delete an Entity

When you don’t want to make an entity available anymore for mobile clients, you can delete it from the list. When you select an entity from the list and click the Delete button a confirmation popup appears. After you confirm the delete, the entity is removed from the list of mobile entities.

You cannot delete an entity if it is used in a profile. Before deleting an entity you must first remove it from any profile it is used in.

Edit

Publish an Entity

When a mobile client synchronizes with the server for the first time, the metadata of every entity is transferred to the mobile client. When the metadata of an entity changes, e.g. an attribute is added or deleted, that change should be communicated to the mobile client so that the mobile client can refresh the metadata for that entity.

When you select an entity from the list and click the Publish button a confirmation popup appears. After you confirm publishing the entity, the Modified On date is updated and mobile clients will refresh the metadata for that entity when they synchronize next. Edit

5 - Profiles

A Profile contains a selection of Entities with their own Filters, Views and Forms. This is a very powerful feature. E.g. it enables you to have a Sales and a Service profile, each with their own mobile entities. Each profile has its own synchronization filters so the Sales profile could synchronize "my active accounts" while the Service profile could sync "all accounts with active cases". Also forms and views are defined per profile. You could make the Account form read-only for the Service profile (they don't need to edit account info) and editable for the Sales profile (they manage account info). You can even define field level security using profiles!

When you click on the Profiles menu item in the main menu you go the Profiles overview. From this overview you can Add, Edit, Delete and Copy profiles. You can also Import and Export profiles.



Edit

Add a Profile

When you click on the Add button in the menu bar a popup window appears. Here you can enter a name for the new profile. Then on the first tab you can create the sitemap. The Sitemap for CWR Mobile CRM has basically the same function as the CRM Sitemap. The Sitemap defines the main menu on the mobile client.



The Sitemap consists of Area’s, which are the Menu Groups on the mobile client (e.g. Workplace or Sales) and Menu Items (e.g. Calendar or Tasks).

When you right-click the Site Map you can Add and Area. A popup window appears and you can give the Area a name and select from a list of predefined icons.



When you right-click an Area you get three options:



You can add a menu item to the area, or hide or delete the area. When you hide an area it shows as strike through:

When you add a new menu item, the following popup appears:

You have to fill in a title for the menu item and a type. There are three types: Entity, Url and Calendar. Depending on the type you choose you have to select either an existing entity from a list (when you choose type Entity) or enter a URL (when you choose type Url). Entity is the most used type; it opens a list of the specified entity type. The Url type opens the specified url in the web browser. Finally, the Calendar type opens a Calendar that shows Appointments and Service Activities (if available in the profile).

Right-clicking a menu item gives you the option to delete the menu item.

On the second tab, entities can be added to the profile. You can choose from the list of entities that have been selected in the Entities overview.

When you’re done you can click OK and the profile is saved. If you want to Edit an existing profile, double click the profile in the list and the popup window appears again.



Edit

Delete a Profile

When you select a profile from the list and click the Delete button a confirmation popup appears. After you confirm the delete, the profile is removed. You cannot delete a profile as long as there are users in the profile, so you must first move users to another profile or delete users before you can delete the profile.

Edit

Copy a Profile

You can quickly create a new profile by copying an existing profile. This comes in handy when you want to use an existing profile as the starting point for a new profile.

To copy a profile, first select an existing profile from the list. Then click the Copy button. A popup window appears where you can enter a name for your new profile.



When you click OK a new profile is created based on the one you selected, complete with Forms, Views and Filters.

Edit

Import/Export a Profile

You can also quickly create a profile by importing a profile from an xml file. You can use this feature e.g. to export a profile from another environment and import it into your environment.

When you click the Import button a popup window appears. Here you can enter a name for the profile that you import, or you can leave the field empty. In that case the profile name from the import file is used. Furthermore, you can browse for the import xml file.



You cannot overwrite an existing profile, so you need to choose a new name for the profile.

Two default profiles are included in the installation; a Sales and a Service profile.

You can also export an existing profile and save it as an xml file so you can import it into another system.

When you select a profile from the list and click the Export button a File Download dialog appears and you can save the export file to your hard disk.

Edit

6 - Users

Once you’ve added Profiles you can manage your mobile Users. When you click on the Users menu item you go the mobile Users overview. From this overview you can Add, Edit and Delete users.



Edit

Add a User

When you click the Add button a popup window appears. Here you can select from a list of CRM users and select a profile where you want to put the user in.



There are also two options Wipe User and Disable. These options are not of much use when adding a user. They are more useful in a later stage.

Edit

Edit a User

When you double click a user in the list the same popup window as shown in the above figure appears and you can Edit the user.

Here you can move the user to another profile. It’s important to note that when a user has already synchronized with a profile and is moved to another profile, the user needs to initialize the mobile client again!

You can also temporarily Disable a user. When a user is disabled, he can no longer synchronize with the mobile client. When trying to synchronize the message “This user is disabled” appears.

Finally you can Wipe the user. When you wipe a user, the data on the mobile client is wiped when the user synchronizes. This is useful for when a mobile device is lost or stolen. Note that this option only works when the mobile device synchronizes after the Wipe option has been set. If the mobile device doesn’t have a network connection and doesn’t synchronize, the data is not wiped!

If the user has background synchronization enabled on the mobile client and the network connection is active, the data will automatically be wiped during the next background synchronization.

While trying a normal sync the message “This user will be wiped” appears and the application will exit.

Edit

Delete a User

When you select a user from the list and click the Delete button a confirmation popup appears. After you confirm the delete, the user is removed.

When you delete a specific user (or don’t add the user at all), that user gets an error message saying “This user is not a Mobile User”.

Edit

7 - Views

Mobile Views have the same function as views in CRM. A mobile view represents a view on the local data on the mobile device. As mentioned in the Profiles section, views can be defined per entity per profile. So, an Account entity in the Sales profile can have different views than the Account entity in the Service profile.

When you click on the Views menu item you go the Views overview. From here you can Add/Edit, Delete, Export and Import Views.



Edit

Add/Edit a View

When you click the Add button a popup window appears. Here you can choose a profile from the list of profiles and an entity from the list of entities that are associated with the profile and that have no view defined yet.



The Create Default View option is a powerful feature. If you check this option when creating a new view, it tries to generate views for you based on the CRM views that are associated with the entity you chose.

Note that not all CRM views are compatible with mobile views. Incompatible views are skipped and an entry is added to the Mobile Configuration log file on the server. Look e.g. at the Email views:



The All E-mails and My Draft E-mails views are generated. Two incompatible views My Sent E-mails and My Received E-mails were skipped. These views use a filter that is incompatible with the mobile views. Also you see that there are no Related Views. This is because the Email entity doesn’t have any related views (Associated Views in CRM).

You can also leave the Create Default View option unchecked. In that case you have to create all your views from scratch. So most of the time you would leave this option checked to give you a head start. Edit

Change View Properties

Once you generated a view you can change a number of properties. In the right pane you’ll find a number of tasks you can perform. When you click the View Properties button a popup window appears where you can edit the properties of the selected view.



You can define whether you can add new records using the view with the Show new option. With the Show find option you define if there’s a find button on the view so you can enter a search string. With the Show delete option you can define whether users can delete records from the view. This is regardless whether the user has the privilege to delete certain records. The Show delete option is a general setting. If the user doesn’t have the privilege to delete a record, the user cannot delete the record.

In the previous figure you see that the Default view option is disabled. There should always be one default view. That’s the view that shows up first when opening a view. You cannot uncheck this option. You can only check the option on another view. In that case the new view will be the default view and the old default view is no longer the default.

Finally you can change the name of the view.

Edit

Edit Filter Criteria

As said, a mobile view represents a view on the local data on the mobile device. Most of the time this view will be filtered. You use filter criteria to define what is shown in the view. Take e.g. the view “All Appointments for Today”. The filter looks like this:



You see here one filter group with two conditions combined with an AND. This filter shows all appointments where scheduledstart is Today AND statecode is not Complete (1).

We can extend this filter to get an “All My Appointments for Today” view. To do this we add a new condition “Owner equals current User” to the filter group.

When you right click on the “Filter (And)” filter group a context menu appears:

When you click Add Condition a new popup window appears where you can define your condition.

Here you can select a Field that you want to filter on (in this case Owner) and the Operator (in this case Equals Current User). The Value field is not used in this case, because the value is already included in the operator.



When you click OK the end result looks like this:

The list of available operators depends on the type of field that you filter on. E.g. if you double click the first condition (scheduledstart) and open the list of operators you’ll find other values than the ones shown in the above figure.



When you double click on a filter group (or when you add a new filter group) a popup window appears where you select the grouping type. You can group conditions within a filter with an AND or an OR.



With the ability to add multiple filter groups, each with their own grouping type (and/or), and the ability to add multiple conditions to each filter group, you can create complex filters to match your needs.

Edit

Configure Sorting

When you click on the Configure Sorting button a popup window appears where you can set the sorting column and the sorting order.



Edit

Add Columns

When you click the Add Columns button a popup window appears where you can select columns that you can add to the view. You can check the columns that you want to add and after clicking OK, the columns will be added to the end of the view columns.



Edit

Change (Column) Properties

You can double click a column or select a column and click the Change Properties button to open a popup window where you can edit column properties.



Here you can change the width of the column and the Column title. Depending on the data type of the column you can also set the Display field. E.g. for a DateTime field you can set the Display field to Date/Time, Date or Time. For other types such as Nvarchar, there is no Display field or the Display field is fixed to a certain value.

When you leave the Column title to its default value, the value will be omitted from the generated view xml and the mobile client will use the value from the metadata. The implications of this functionality will be described in detail in the section Change Field Properties.

Edit

Remove (a Column)

When you select a column and click the Remove button a confirmation popup appears. After you confirm the delete, the column is removed from the view.

Edit

Delete a View

When you select a view from the list and click the Delete button a confirmation popup appears. After you confirm the delete, the view is removed.

Edit

Import/Export a View

Just as you can import and export complete profiles; you can also import or export a single view. When you click the Import button a popup window appears. Here you can select a Profile and an Entity. Finally, you can browse for the import xml file.



You cannot overwrite an existing view. You can only select an entity that has no view yet. If you want to import an already existing view, you first need to delete the existing view and then import the new one.

You can also export an existing view and save it as an xml file so you can import it into another system.

When you select a view from the list and click the Export button a File Download dialog appears and you can save the export file to your hard disk.

Edit

8 - Forms

Mobile Forms have the same function as forms in CRM. A mobile form enables you to view, create and update data on the mobile device. As mentioned in the Profiles section, forms can be defined per entity per profile. So, an Account entity in the Sales profile can have a different form than the Account entity in the Service profile.

When you click on the Forms menu item you go the Forms overview. From here you can Add/Edit, Delete, Export and Import Forms.



Edit

Add/Edit a Form

When you click the Add button a popup window appears. Here you can choose a profile and an entity from the list of entities that are associated with the profile and that have no form defined yet.



Just as with views, you have the option to let the system generate the form for you using the Create Default Form option.

Not for all entities forms can be generated. Some CRM entities have hardcoded forms that cannot be retrieved from the CRM metadata. This does not mean that you cannot create a form for such entities; it only means that the system cannot generate it. Let’s try to generate a form for the businessunit entity.



You see it generates an empty form with one tab named “???”. When we look at the CRM entity properties for businessunit in the next figure we’ll see that there’s no form that can be configured, only entities.

Note that there’s often a reason that a form cannot be customized in CRM. These entities usually have very specific functionality that is important for the correct functioning of CRM. So be very careful when creating a form for such an entity. As a precaution, when generation of the form fails, it Read only property is automatically set to True. This way the data can only be viewed on the mobile client, not edited.





When generating a form succeeds you are presented with a preconfigured form based on the CRM form. Let’s look at a form generated for the letter entity.



Edit

Change Form Properties

Once you’ve generated the form you can change a number of properties. In the right pane you’ll find a number of tasks you can perform. When you click the Form Properties button a popup window appears where you can edit the properties of the form. The popup window is shown in Figure 31.

Here you can change the title for the form. You can also set the Read only and Show save properties. Checking the Show save option will show a Save button on the mobile form.

Edit

Add Fields

When you click the Add fields button a popup window appears. Here you can select one or more fields to be added to the form and you can choose the tab to add them to.



Once the fields are added to the form you can move them up and down using the up and down arrow buttons. You cannot move a field to another tab using the arrow buttons; you have to use the Change Properties form to do that.

Edit

Add Tab/Label

When you click the Add a tab button a popup window appears where you can enter the name of the tab. When you confirm the tab is added to the right of the existing tabs. With the left and right arrow buttons you can then move the tab.

When you click the Add a label button a popup window appears where you can enter the name of the label. A label is much like a Section in CRM. However, a label doesn’t contain fields so you cannot move a label together with the containing fields like you can with sections in CRM.

Edit

Add Custom Control

You can also add custom controls to your form. These are .NET controls that you can create using our Custom Control SDK. When you add a custom control you need to enter the .NET fully qualified name of the control. You can also add name-value pairs that are used as input parameters for the control. An example of adding a custom control could look like this:



Note that these are arbitrary name-value pairs and are defined by the custom control developer.

Furthermore, you can decide if the control should be visible on the form and on which tab it is located. You could e.g. hide a custom control if it’s only performing validation functions.

A custom control looks like this on a form:



Edit

Change Properties

With the Change Properties button you can change the properties of the selected item. This can be any of the top four items in the right pane: tab, label, fields or custom control. Double clicking an item has the same effect.

Changing the properties of a tab or label opens a popup in which you can edit the name of the tab or label. Edit

Change Field Properties

Double clicking a field or selecting a field and clicking the Change Properties button opens a popup window where you can change the properties of the field. Let’s take a look at the properties of the subject field.



You see the form is divided in three sections: General, Additional and Location. The sections General and Location are the same for every Control type (Nvarchar in this case). Depending on the Control type there can be zero or more properties in the Additional section. The following Control types exist:

Type	Additional properties	Description
Attachment		Special type only used for the filename field on the annotation entity.
Bit	Display format, True value, False value, Default value
Custom		Used for custom controls.
Customer
DateTime	Display format
Decimal	Minimum value, Maximum value, Precision, Default value
Float	Minimum value, Maximum value, Precision, Default value
Int	Minimum value, Maximum value, Default value
Lookup	LookupEntities
Money	Minimum value, Maximum value, Precision, Default value, Currency symbol
MultiLookup	LookupEntities	Lookup that can reference multiple records.
Nvarchar	Display format
Owner
Picklist	Default value
State	Default value
Status	Default value

Most of these control types match directly with their corresponding CRM type.

When we go back to the Field Properties form we see that the Field name and Control type properties are read-only.

The Label property has specific functionality. When you add a field to a form, by default the Label is filled with the label from CRM. When you leave it like this, the actual Label attribute is omitted from the generated form xml (that will be sent to the mobile client). When this attribute is omitted, the mobile client will use the Label value from the metadata.

This is a great localization feature! Because what this means is, that you can create forms (and views) with default label/column values, export the profile and use it in any language CRM system, and the mobile client will use the labels from the localized metadata, i.e. in the language of the CRM system you connect to!

When you empty the Label property, the Label attribute is included in the generated form xml, but its value is blank. In that case, the label on the form will be blank also. When you change the Label property, you override the default value and the new value will be used.

Furthermore, you can set the Mandatory and Read only properties. You can also toggle visibility of the field. This may not make much sense, but it can be useful when overriding default fields with custom controls. In that case you might want to hide the default control. When you double click on an Additional property a popup window appears where you can edit the property. E.g. you can change the Display format for an Nvarchar control:



When you change the Display format to Text Area, an extra property named Rows will appear in the Additional section with a default value of 5.



Let’s take a look at another example. When you double click the field Priority you see the Field Properties form. The field is of type Picklist and has one additional property named Default value. When you double click that property the following popup window appears:



The available default values for the field Priority are taken from the CRM metadata and shown in the list.

Finally, the Lookup Entities property is worth mentioning. The best example is the Regarding field of an Activity. This field can point to several different entity types. Using the Lookup Entities property you can decide which entities you want to have available and in which order.



Edit

Related

When you click the Related button a popup window appears where you can add or remove related entities. On the mobile client, related entities are shown in the Related menu when you open a form. When you click on a related entity, a list opens with all records of that entity that are related to the entity on the form. Let’s take a look at the order entity. The related entities popup looks like this:



The list shows all one-to-many relations for the order entity. E.g. one order with (zero or) many invoices. These relations are all retrieved from the metadata. So when you’ve created custom entities with relations to system entities, these relations also show up in this list. From this list you can add or remove related entities.

Some entities, like account or contact, have a lot of relations. By default a relation gets the name of the related entity. This can create duplicates. Let’s look at some relations for the account entity.



We see four relations with Contracts. The mobile client uses the name as the display name in the Related menu so the names have to be unique. When you double click on a relation a popup window appears where you can change the name for the relation.

Note that when you have duplicate relation names, the mobile client will only show the first occurrence of that name and skip the other ones!

Edit

Remove

With the Remove button you can remove the selected item from the form. When you select an item and click Remove a confirmation popup appears. After you confirm the delete, the selected item is removed from the form.

Edit

Delete a Form

When you select a form from the list and click the Delete button a confirmation popup appears. After you confirm the delete, the form is removed.

Edit

Import/Export a Form

Just as with profiles and views, you can also import and export forms. When you click the Import button a popup window appears. Here you can select a Profile and an Entity. Finally, you can browse for the import xml file.



You cannot overwrite an existing form. You can only select an entity that has no form yet. If you want to import an already existing form, you first need to delete the existing form and then import the new one.

You can also export an existing form and save it as an xml file so you can import it into another system.

When you select a form from the list and click the Export button a File Download dialog appears and you can save the export file to your hard disk.

Edit

9 - Filters

Filters determine how much data gets synchronized to the mobile devices. As mentioned in the Profiles section, filters can be defined per entity per profile. Note, if no filters are applied for a particular entity, all information the user is allowed to see is being synchronized.

You can combine filters to get a more precise dataset. Filters can get pretty sophisticated, combining AND/OR clauses and linked entities. However, sometimes it’s not possible to get the data you want using just one filter and that’s where you combine filters to get the desired result set. The data retrieved from each individual filter is combined, duplicates are removed and the result is transferred to the client.

It is recommended to keep your filters as simple as possible and to keep the number of filters (per entity) low. However, it’s more important to keep the filters simple than to keep the number of filters low. So in general, using two simple filters is better than one large, complex filter.

Keep in mind; filters are converted to SQL queries on the CRM database. The more complex the filter, the more complex the SQL query which puts more load on the server and can affect performance adversely. Contact your CRM/SQL administrator for more information on the performance of filters/queries. He/she can profile the SQL database and fine-tune performance if needed. For further reference see “Optimizing and Maintaining Microsoft Dynamics CRM 4.0”.

When you click on the Filters menu item you go the Filters overview. From here you can Add/Edit, Delete, Export and Import Filters.



Edit

Add/Edit a Filter

When you click the Add button a popup window appears. Here you can choose a profile and an entity to add the filter to. You can also enter a descriptive name for the filter.

Then, on the Filter tab you can start creating or editing the filter. The Xml tab shows a read only textual xml view of the filter. Let’s create a filter for Accounts named My Active Accounts with Activities in the last 6 months. This will filter all active accounts where I am the owner and that have relatedactivities that have been modified in the last 6 months.

When you choose a profile and the Account entity from the list and fill in the name, you see this screen:



Now we need to add a Filter with 2 Conditions:

1. Statecode = Active
2. OwnerId = Current User

Right-click on the Account node and select Add Filter from the popup menu:



Then, in the popup screen select And for the type of filter because both conditions need to be met:



This will result in Statecode=Active AND OwnerId=CurrentUser.

Clicking on OK returns you to the Filter tab. Right-click on the Filter (And) node and select Add Condition:



Here we can define the first condition:



The Operator and Value fields change based on the type of Field that is chosen. E.g. not all operators apply to all types of fields. DateTime operators like Today or Last X Months obviously only apply to DateTime fields and will only show in the list of operators when a field of type DateTime is selected.

The same applies to the Value field. When available values are known, as the case is for Statecode (and picklist fields), the Value field displays those values to choose from.

Clicking on OK returns you to the Filter tab. Here you can add the second condition. This time we select the field OwnerId. You see how the list of operators now shows Equals Current User:



You don’t need (and you can’t) fill in anything in the Value field, because the value is already included the operator in this case. When you click OK the Filter tab should now look like this:



Now, for the second part of the filter we need to create a link with Activities and filter on the ModifiedOn field. Right-click on the Account node and select Add Link-Entity:



A popup window appears where you can select the Link Entity:



Most of the time you will use the 1 to Many relations to select a Link Entity. We want to link to Activities using the Regarding (regardingobjectid) field. So this will get Activities where the Account is in the regarding field. We could also choose to link via activityparty.partyid. That way we would select Activities where the Account is a Party (resource, optional attendee, requiredattendee, etc.).

After clicking OK we return to the Filter tab and we finally need to add the filter on the ModifiedOn field of the linked Activity. Right-click the linked entity node and choose Add Filter. Select the And type. Then right-click the Filter (And) node and select Add Condition.



Here you see that the list of operators shows DateTime related operators. Select Last X Months and enter 6 in the Value field. Click OK and your filter is finished!



When you click OK the filter is validated and, if no validation errors are found, saved.

This is just one example of a filter that showed the basic principles of Filters, Conditions and Linked Entities. You can add multiple filters and combine AND and OR filters. And you can add as many conditions to a filter as you like. You can also add multiple levels of linked entities. In theory there’s no limit to the amount of filters, conditions and linked entities you can add. However, the sync filters are translated into SQL and executed by SQL Server. The more filters, conditions and linked entities you add, the more complex the SQL query becomes and this affects performance. So, keep it as simple as possible!

Edit

Delete a Filter

When you select a filter from the list and click the Delete button a confirmation popup appears. After you confirm the delete, the filter is removed.

Edit

Import/Export a Filter

Just as with profiles, views and form, you can also import and export filters. When you click the Import button a popup window appears. Here you can select a Profile and an Entity. You also need to enter a Filter name. Finally, you can browse for the Filter xml file:



You can also export an existing filter and save it as an xml file so you can import it into another system.

When you select a filter from the list and click the Export button a File Download dialog appears and you can save the export file to your hard disk.

Edit

10 - Troubleshooting

Edit

Log files

The Mobile CRM Server has two kinds of log files. The Configuration-error<date>.log file for errors in the Mobile Configurator and the WebServices-error<date>.log file for the errors that occur during communication with the Mobile WebServices.

These log files are located in the Logs sub folder of your Mobile CRM installation folder.

Edit

I see a red status bar at the bottom of the main menu.

A red status bar means that something is wrong with the license. It can be that the license file is missing or the registered name doesn’t match the CRM organization name. In the next figure the license file is missing.



When you hover over the red status bar it shows a tooltip with the error message. The detailed license error can be found in the log file.

Edit

Registered Name doesn't match.

This error message indicates that the registered name you provided when requesting the license doesn’t match with the organization name you used to install CRM. You can check this by looking at the primary business unit name in CRM. The primary business unit is the business unit that doesn’t have a parent business unit. Note that the registered name is case sensitive!

Another reason for this error message is that the license file cannot be read due to insufficient privileges. You have to make sure that the Network Service account has sufficient privileges to read the file.

As an example, these insufficient privileges can be caused by first copying the license.lic file to your Desktop (it then get the security properties from the Desktop, which are insufficient) and then after installation, move the license file to the WebServices folder. When you do this, the Security properties for the license file look like this:



When you click the Advanced button you see that the checkbox “Allow inheritable permission from the parent….” is unchecked.



Check this option and click Apply and you see new permissions appear. You could now delete the top three permissions as they’re not needed anymore.

The Network Service account is part of the Authenticated Users, so now the Authenticated Users has Read permissions, the problem should disappear.



Edit

I get an error message when I try to delete an entity from the entity list.

When trying to delete an entity the following error message can appear:



The most common cause for this error is that the entity is still in use in a profile. To fix this error, first delete the entity from all profiles and then delete it from the entity list.

Edit

I get an error message when I try to delete a profile.

When trying to delete a profile the following error message can appear:



The most common cause for this error is that the profile still contains users. To fix this error, remove all users from the profile, either by moving them to another profile or by deleting them.