Configuration

You can use Woodford to set up some of the default settings of the Resco Mobile CRM app remotely. You can also prohibit users from modifying the settings. Edit an app project and select Configuration from the Project menu.

The list of parameters is divided into several groups. You can expand and collapse each group by clicking its header row.

• User Experience
• Data
• Synchronization
• Security
• Online Mode
• PIM/Email
• Accounts

Each row represents a configuration parameter.

• It is identified by a name, a description, and the default value - you cannot change these.
• Use the Value column to modify configuration. All changed options are displayed bold.
• Optionally, use the Lock checkbox to allow or disallow app users to override the setting in the app. If you lock a setting, the option actually disappears from the Setup section of the mobile app.

You can also configure Sync Config and Blob Filter from this screen.

Configuration examples

Client Customize

This setting does not use the Lock checkbox. If you leave the Value checkbox ticked, users will be able to use the Data part of the Setup and enable/disable entities. If you clear the Value checkbox, users will not see the Data part anymore and will not be able to enable/disable entities.

Multi Thread Sync

This setting does not use the Lock checkbox, as this setting is not available in the Mobile CRM Setup. This option is enabled by default, but if users experience synchronization problems, it can be turned off.

Use Database Encryption

This setting does not use the Lock checkbox, as this setting is not available on the Mobile CRM Setup. Local database is encrypted by default on the mobile devices. It can be disabled though.

Save Signature As PNG

If this option is enabled and value set to true, the signature files will be saved as .PNG files instead of .SVG that is used when the value is set to false.

Use Entity & Attribute Map

If you have an automatic field mapping set up on the CRM server, this parameter will enable the same functionality in the Mobile CRM application.

Background synchronization

You need to set Require Sync Login option to False and Save Password to True.

Automatic synchronization – Please check our BLOG POST. Blog

Detecting duplicates (Microsoft Dynamics)

The parameter Duplicate Detection controls whether to use duplicate detection when creating a new record. The purpose of Duplicate detection is to discover duplicate records, such as:

• Accounts using the same name
• Contacts using the same e-mail address

Duplicate detection rules are to be set on the CRM server (for more info, go to LINK). Mobile CRM application does not create any rules on its own; it may be directed to make use of the CRM server rules.

If you do so, then whenever an entity record is saved, this record is compared against the existing records to find the possible duplicates. If there are any, MobileCRM application displays a warning and users get a chance to edit the data.

Disabled

Duplicates are not detected.

Enabled

If MobileCRM is in offline mode: The local database is checked for duplicates by using the local rules. (Duplicate detection is stored in system entities duplicaterule and duplicaterulecondition. These entities physically contain the duplicate detection rules. They are originally stored on the server (server rules), but once enabled, the synchronization will copy the rules to the local database thus creating the local rules.)

If MobileCRM is in the online mode: The server database is checked for duplicates by using the server rules.

AlwaysOnline

Even if the Mobile CRM app is set to offline mode, the server database is used when looking for duplicates.

Note	Make sure that the Sync Filter does not exclude rules that are needed for the duplicate detection. Also, do not disable these entities in Woodford.