Microsoft Dynamics CRM - Working offline with Dynamics CRM mobile apps

Microsoft Dynamics CRM 2016 provides you with full offline experience with mobile Dynamics CRM apps.
You can find some more information here.
In order to Configure your mobile offline synchronization for CRM for phones and tablets, please click here.
The following video will provide you a quick tour for Dynamics CRM mobile offline.

 

 

Fredy Opaets
Soft-Pro
Fredy@soft-pro.co.il

Moving Form Labels Above the Field Instead of on Side of Field in Microsoft Dynamics CRM 2011

I know that I have had trouble in the past when I make a new four column section, getting everything to fit on the form, and by default you need to re-size the form on open to even get everything to fit unless you can find a way to shrink your fields down. I know there are settings to change the amount of space given to the label, but I have found another way to tackle this.

Here is how it works:

1. The setting is at the section level. So, double-click on a section to bring up the section properties
   
   
   
2. Now, click on the formatting tab and scroll to the bottom to find the "Field Label Position" setting:
   
   
   
3. Now you just have to change the setting to "Top" and save and publish the form. You can repeat this for all sections on the form if you want to

It's as easy as that. Here's what it looks like when you are done and have published the form.

Hope it will help you out :).

Two default views in CRM

Two default views? How to get back to one

You might come across a scenario where you see that Microsoft CRM lists two different views as the "default" for an entity (as shown in the screenshot below):

Obviously this is not the intended behavior as only one view should be listed the default. Changing the default view and re-publishing the entity with the web interface does not appear to correct this issue. While we're not 100% what causes this scenario, we have figured out a method to fix it.

First you need to export the customizations.xml file for the entity. Then open the customizations file and search for the duplicated defaulted view and change the
 
"isdefault name="Yes" "1 "isdefault "
To
"isdefault name="No" "0 "isdefault"

Note that when you find the view "name" in the customizations.xml file, it is actually at the bottom of the node. This means you will need to scroll up in the file to find the "isdefault" node.

Save, import, publish and you should be all set again.

Enabling and Editing ISV.CONFIG

To edit the isv.config, do the following:

1.Export the isv.config using the Export Customizations tool. 

2.Create a backup copy of the exported XML file. Use this file to recover from errors.

3.Make your changes to the exported XML file.

4.Import the updated XML file using the Import Customization tool.

This file contains examples of the various customizations you can perform. You should rename this file and then create your own configuration file. By doing this you will not confuse the sample UI changes with the UI changes you need for your customization.

Enabling your customizations
To enable your customizations, modify the ISVIntegration setting in the web.config file, which is located at:

\wwwroot\web.config

This setting appears as follows:

The ISVIntegration setting is used as a performance optimization. When there are no customizations to be rendered, the value for this setting should be None. Multiple values can be used as long as they are separated by a comma and do not contain spaces, as shown in the following examples: 

The following table shows the possible values for the ISVIntegration setting.

Value Description 
All - Integration is turned on for both Outlook and Web clients 
None - Integration is not turned on 
Outlook - Integration is turned on for only the Outlook client 
OutlookWorkstationClient - Integration is turned on for only the full Outlook client 
OutlookLaptopClient - Integration is turned on for only the light Outlook client 
Web - Integration is turned on for only the Web client 

ISV Extensions Privileges
After you have enabled your customizations, you need to set the ISV Extensions privilege for security roles that need to use the customizations. By default, the security roles that do not represent a management position do not have ISV Extensions Privilege.

Disabling your customizations
To disable your customizations for either client you must use the appropriate setting in the web.config file. 

Security Issues

Any integration into the application or the Outlook client must participate in security. That is, any server or client application calling into the Microsoft CRM 3.0 application programming interface (API) must have user context in the same domain.

How to change Field Requirement Level

This script allows you to change the requirement level for one or more fields.

The number in the script means the following :
0 - No Constraint
1 - Business Recommended
2 - Business Required

crmForm.SetFieldReqLevel("AttributeSchemaName", 1);

Form Assistant for Dynamics CRM 4.0 / 3.0

Purpose :
1) Some clients don't like using Form Assistant
2) On low resolution screens, I don't recommend using Form assistant. It takes up too much space

There are several steps we need to follow in order to hide the form assistant.

Dynamics CRM 3.0 – How to hide?
1. Export related Entity (where you want to disable Form Assistant)
2. Find the following: relatedInformationCollapsed="true";
3. Change "true" to "false"
4. Import

Dynamics CRM 4.0 – How to hide?
1. Go to customizations à Enter the relevant entity
2. Go to forms and views à Enter “Form”
3. Click on “Form Properties” and go to “Display” tab
4. Turn On/Off the features according to your needs

5. Click “Ok”
6. Save and close the form
7. Publish the entity and that’s it :)