A validation error occurred. The value of ‘membercount’ on record of type ‘list’ is outside the valid range exception in Dynamics 365 (CRM)


We were getting the below error while trying to delete one of the marketing list members from a static marketing list.

This occurs if the Members Count field has value 0 in it, even if there are members associated to it. (due to some exception)

Updating that field to correct value fixes this issue (customize the form to add the field on form). and we can then delete the members from it.

Hope it helps..

Using tpc.identity to get the logged in user details in JavaScript in The Portal Connector (TPC)


Recently while working in TPC, we had a requirement to get the details of the logged in user (which is basically a contact record in CRM).

To do so we can make use tpc.identity object in Client Side.

For e.g. contactId

Hope it helps..

Create a simple logic app with Dynamics 365 connector


Let us create a simple logic app that on create of a contact record in CRM creates the same contact in Gmail.

Log in to the azure portal.

https://portal.azure.com/#create/hub

Select New Logic App

Specify Name, Resource Group and Location for the logic app.

Select Blank Logic App

Select “When a record is created” as Trigger.

Sign in to Dynamics 365 Instance.

Select the Organization name and Entity as Contact.

Select Add an action and the New Step

Choose Google Contacts as the Service

Sign in to your Gmail account to be connected

Allow permission to Logic App to access Gmail

Configure Full Name and Primary Email (Dynamic content) as the values for the contact record to be created in Gmail.

Save and Run the app.

Create the new contact record in CRM that triggers the logic app.

On Successful run à

We can see the contact record created in Gmail.

Find all the details here

https://docs.microsoft.com/en-us/azure/connectors/connectors-create-api-crmonline

Hope it helps..

Using Multiple Choice Matrix and Likert Scape Option Sets in Web Form in Dynamics 365.


Let us continue with our previous example wherein we have already setup a sample Survey Web Form and added a Multi choice Field

https://nishantrana.me/2017/03/06/configuring-multiple-choice-field-for-web-form-in-portal-dynamics-365/

Here we would be making use of Multiple Choice Matrix.

For this first let us create 2 option sets in our Survey Entity. We’d put those field in Step 3 Tab.

  • Here we will use the existing global option set for Likert Scale which is added by the Portal in CRM.

Our first field – FacilityLikert Scale Satisfaction.

Our second field

Below are the different Likert Scale Global Option Set available within CRM added by Portal.

Now in the Survey form we have added a section named “Please Rate” and with the newly created fields inside it.

In the Web Form Step corresponding to the Step 3 tab and we added Web Form Metadata records one for each of the fields.

Style Multiple Choice Matrix
Group Name MCM

Refreshing the page in the Portal shows the option sets as Multi Choice Matrix

Hope it helps..

Configuring Multiple Choice field for Web Form in Portal (Dynamics 365)


Let us continue with our previous example and add a Multiple-Choice field for Step 3 Web Form Step as shown below.

https://nishantrana.me/2017/03/06/using-conditional-branching-in-web-form-in-portal-dynamics-365/

To configure this, add a section named “Please select all that applies” to Step 3 Tab and 3 two options (Boolean) fields in the Survey Form.

Now go to Step 3 Web Form Step and add Web Form Metadata for each of these bool fields.

For the poor management field,

  • Style – Multiple Choice
  • Group Name – MyGroup

For the poor salary field, specify the same value for style and group name field

  • Style – Multiple Choice
  • Group Name – MyGroup

Do same for the third two options field.

The main point to remember here is that the Group Name should be same.

Now open the portal page and go to the web form step.

The page shows the newly added Boolean Fields in the Web Form Step as checkboxes.

Hope it helps..

Using Conditional Branching in Web Form in Portal (Dynamics 365)


Let us continue with our previous example of Employee Exit Survey and add conditional branching step to it.

https://nishantrana.me/2017/03/05/using-web-form-to-create-a-simple-survey-in-portal-dynamics-365/

Here we’d add a conditional web form step which will check the response of the user for Work Life Balance question and in case if it false, it shows one more step to the user and asks for the comments.

So, let us first create a web form of type Condition with below details

Type Condition
Target Entity Logical Name Our custom survey entity
Next Step Web Form Step when condition is true
Condition If new_thirdquestion is true

Now let us see the details of web form step – third step which we have defined as Next Step for the condition Web Step above.

We have also created associated Web Form Metadata record of the type attribute for defining the label and other properties for the new field named fourth question in our survey form.

Adding label –

Adding Description –

Making field required –

Finally update the Second Web Form Step to point to the Condition Step

We are done with our configuration, now going back to our web page shows the Web Form with all the 3 steps.

Clicking on next with No as the answer for the Work Life balance Question shows the third web form step. Note here we can see the label defined, description defined and also the field is mandatory which we did using Webform Metadata.

Clicking on submit without specifying comments shows the required field message

All the details here

https://community.adxstudio.com/products/adxstudio-portals/documentation/configuration-guide/web-forms/web-form-steps/conditional-step/

Hope it helps..

Using Web Form to create a simple survey in Portal (Dynamics 365)


Web Form are an extension of Entity Form, which can be used for Surveys, Registration or any wizard sort of interfaces etc. which could involve conditions and span across multiple entities.

To understand Web Form, let us create a simple Employee Exit Survey having 3 questions and 2 web form steps.

Basically, we have one Web Form which can have one or more than one Web Form Steps. Here we will use tabs within a single form for web form step (we can also use multiple forms as steps)

Let us first create a custom entity named Survey which we will use in Web Form having 2 Tabs Step 1 and Step 2, which we will use to define our Web Form Steps respectively.

Here each field/ attribute defined is one question in our Survey.

Using Web Form Metadata we can specify the label for the fields above and can do some formatting as well.

Below is our Web Form record –

Start Step is where we define the Web Form Step, which are similar to Entity Form.

Below is our First Step Web Form Step.

Type Load Tab – as we are loading the tab here
Target Entity Logical Name new_survery
Next Step Second Step – the next web form step.
Mode Insert – as we are creating the record
Form Name Name of the form
Tab Name Tab inside it

Also here we will create a related Web Form Step Metadata of type attribute to define the label for the field named new_firstquestion.

Let see the definition of the next Web Form Step i.e. Second Step

Mode Edit – Here the mode is edit as the record will already be created in the first step and will be updated in this next step.
Move Previous Permitted Allowing user to move back to the first step.
Next Step Blank – so this will be the last step.
Source Type Result From Previous Step
Entity Source Step First Step – the previous step.

Below is the Web Form Metadata for the below 2 fields of the Step 2 Tab. One of the fields is Option Set and the other is Boolean.

Metadata for second question field –

Metadata for third question field –

Finally, the web page that displays the Web Form

This is how the Web Form renders in the portal

On Submitting the Survey

This creates the Survey record in CRM

Hope it helps..

Clear Cache in Portal in Dynamics 365


Update – Append “/_services/about” to the portal URL ==> OCache

 

Or

Restart the portal from Portal Admin Page

Cache1

Recently while working on web form configuration we made few changes to the form that was being used in web form step. However, the changes we made were not getting reflected back in the portal.

We had added the 2 controls in Step 2 tab in the form, however the change was not getting reflected back in the portal.

In the portal,

To refresh the website with the latest CRM changes, we can go to the Dynamics 365 Administration Center

And change the portal state to off – update and back on – update.

This updates the portal page with the latest changes

Also refer this document

https://community.adxstudio.com/products/adxstudio-portals/documentation/developers-guide/cache/cache-invalidation-utility/

Hope it helps..

1000 posts on my blog


Hope they have been helpful 🙂

1000

Understanding Parental Scope in Entity Permission in Portal (Dynamics 365)


Let us create 2 entities Parent Entity and Child
Entity having 1 – n relationship.

Here we will be creating Entity List for Child Entity that displays all the child entity records associated to Parent Entity to which user has access to.

This we can achieve using Child Entity Permission record for the Child Entity.

First let us define an Entity List for Parent Entity to which we will enable Entity Permission with Global Scope.

Next let us create Entity Permission for Parent Entity and assign it to one of the web role associated to the current Portal Contact user.

For simplicity, we are keeping the Scope as Global. We can also use Contact and Account scope here for filtering the access to the records if that Entity is associated with the Contact Entity. Based on which the Child entity records will further get filtered.

https://nishantrana.me/2017/02/28/understanding-scope-global-contact-and-account-in-entity-permission-in-portal-dynamics-365/

The above Entity Permission gives access to all the records (Global – Read) of Parent Entity to the portal user.

Now let us create an Entity List for Child Entity and enable Entity Permissions.

Configure the below Actions Create, Details, Edit and Delete.

To configure the above Actions we would need an Entity Form, so before we do that we need to create an Entity Form for Child Entity.

Next configure a web page to display the Child Entity Entity List.

Now comes the important part i.e. creating child entity permission for Child Entity.

Create an Entity Permission Record with the below details :

Scope – Parent

Parent Entity Permission – Entity Permission created for Parent Entity i.e. Entity Permission Parent Entity.

Parent Relationship – the 1 – n relationship we created between Parent Entity and Child Entity.

Now opening the page which has the Entity List defined for Child Entity, we can see the below 3 records associated to the parent records to which user has the Read access.

We do not see the all the records as not all the child entity records are associated to the parent entity’s record.

Hope it helps..

Understanding Scope (Global, Contact and Account) in Entity Permission in Portal (Dynamics 365)


Let us take an example of the below Entity List configured for Case entity configured for Active Cases view.

For Entity Permission to work we need to check Enable Entity Permissions.

Let us first create an Entity Permission record with Global Scope and Read Privileges and assign it to a custom web role to which in turn is assigned to the Portal User.

Below we have Case Entity Permission record associated to our My Custom Web Role.

My Custom Web Role is then associated with the portal contact record.

Scope – Global with Read Privelges à

This shows all the Active Case records in the portal.

Now let us change the Scope to Contact, and specify Conact_As_Primary_Contact as the relationship to be considered i.e. Contact Lookup in Case entity form.

Scope – Contact

This shows all the case records that has current portal user as Contact as well as those records which has Customer specified as the account which is the Parent Account of the current contact portal user.

i.e.

The portal view is filtered based on the Contact Scope Entity Permission.

Now let us change the Scope to Account, and specify Incident_customer_accounts as the relationship to be considered i.e. Customer Lookup in Case form.

Scope – Account

This shows only those case records that has Customer specified as the Parent Customer of the current logged in Portal Contact User.

Hope it helps..

Configuring View and Item Actions for Entity List in Portal in Dynamics 365


Similar to configuring Actions for Entity Form we can specify Actions for Entity List.

https://nishantrana.me/2017/02/27/adding-actions-qualify-workflow-delete-etc-for-entity-form-in-portal-in-dynamics-365/

Let us take example of Case List that comes configured with Community Portal for incident\cases entity.

Inside portal this is how the list shows up as grid à

To define Actions we need to go to Options tab à
Grid Configuration

View Actions lets us define actions for the View which are Create and Download.

For Create we need to define an entity form, web page or an URL configured for Insert for incident record.

Below we have selected Target Type as Entity Form and Create Case as the Entity Form.

This adds the Create button in the portal

Clicking on Create opens the Entity Form for Insert.

Download Action lets user to export the records to Excel

This adds the Download button in the page.

Clicking on Download opens the save as dialog

For Details and Edit Item Actions we need to specify either Web Page, Entity Form or URL to a page having Entity Form defined for Incident\Case entity.

Below we have specified the Edit Case Entity Form.

Inside Portal

Clicking on them opens the Entity Form

Similarly, we can add rest of the Item Actions like Delete, Close, Resolve, Cancel etc.

This add the corresponding options to the grid in the portal.

As we are showing all the Active Records it automatically hides the Reopen Case button.

Here clicking on Cancel Case, cancels the Case record in CRM and shows the below message in the portal.

For Workflow Action, we can define an On Demand Workflow created for the Case Entity.

Suppose we have following workflow defined for Case.

Configuring the same inside Entity List

In the portal we get the option to Run Workflow

Clicking on it gives the below message

Hope it helps..

Configuring Note for Entity Form in Portal in Dynamics 365


Suppose we have below form for Contact to be displayed as Entity Form in Portal having notes control in it.

The Entity Form configured for the above form à

The portal page that displays the Entity Form à

Few points we need to remember here is that

  • The Portal User (contact record) needs to have Entity Permission assigned on Notes (Annotation) through one of the web roles assigned. For simplicity I have given the Global scope permission.

  • The Notes body should start with *WEB* prefix for Notes to be published on the Portal. For e.g. we have 3 notes attached for the contact record but only one shows up in the Portal.

Only 1 note being displayed in the portal.

The Portal displays the Notes as read only OOB.

We can use Entity Form Metadata of type Notes associated to Entity Form to further customize it.

Below are the different options that we have.

Refreshing the Portal page adds the

Add Note button

Edit and Delete Option

https://community.adxstudio.com/products/adxstudio-portals/documentation/configuration-guide/customization-tools/managed-forms/notes-for-managed-forms/

Hope it helps..

Using Entity Form Metadata for Sub Grid configuration in Entity Form in Portal in Dynamics 365


Suppose we have following Entity Form configured for Lead Entity in Edit Mode which is having Contact Sub Grid in it.

Contact Us Lead Form with Contact Sub Grid:

Entity Form Configuration:

The Sub Grid renders as read only

We can further customize Sub Grid creating related Entity Form Metadata of type Sub Grid.

Suppose we have added all the below View and Item Actions to our Sub Grid type metadata.

On refreshing the page, we can see all the actions available as buttons in the page.

For Create to work we need to define the Insert Entity Form for Lead.

Download lets the records to be downloaded in Excel

Associate lets the current lead record to be associated to the contact record selected.

Similarly

View Details opens up the Entity Form defined in the Read Only mode. Edit opens the Entity Form to edit the record. The Entity Form must be configured and defined in the Item Actions for it to work.

Run workflow can be used to run On Demand Workflow(s) configured.

Delete, Disassociate and Deactivate does what it means and doesn’t need any specific configuration.

Hope it helps..

Adding Actions (Qualify, Workflow, Delete etc.) for Entity Form in Portal in Dynamics 365


Hi,

Apart from the Submit button we can additional Actions to the Entity Form like Delete, Workflow, Qualify (in case of lead) etc.

To understand this, we will use the Contact Us Entity Form that comes with Community Portal.

Let us add Delete, Workflow and Qualify action to it. However before doing that we first need to check Enable Entity Permissions on the Entity Form for actions to work.

And as we have enabled the Entity Permission we need to make sure that the portal user has the appropriate permissions through the web role assigned to him.

Below we have created a global entity permission for Lead record and added it to the Web Role which is assigned to the portal user.

Else we would get the below error

One more thing we need to do here is to change the Mode of the Entity Form to Edit as the delete and workflow action will only work for an existing record.

So here basically we are showing the lead record to which current Portal User (i.e. contact) is associated as Parent Contact.

For the workflow, we need to remember that only On Demand Workflow(s) would be available for the actions inside the Entity Form, which does make sense, as it would be something which the user is triggering instead of conditions on which it is running automatically.

Now open the Entity Form, go to Additional Settings tab and add the actions to it.

Below we have added Delete, Workflow and Qualify action. The Qualify action is specific to Lead only.

Refresh the web page in the portal, we will see the buttons added for the Actions.

For Qualify button to appear, we need to make sure the portal user has appropriate rights on Account, Opportunity and Contact entity along with Lead. For simplicity, we have added Global Entity Permission for those entities to the web role assigned to the portal user.

Entity Permission Associated View for the Web Role record: –

On refreshing the page again, we can see the Qualify Button.

On clicking Qualify button à

The confirmation message à

Hope it helps..

Using Entity Form Metadata to configure the Entity Form in Portal in Dynamics 365


Sharing a simple example wherein we are configuring the First Name field of the Contact Us Entity Form for the lead entity using Entity Form Metadata.

Suppose we have the below Entity Form configured for Lead entity.

Now go to Entity Form Metadata tab and create a new record.

The record allows us to configure Attribute, Notes, Section etc.

Let us configure the First Name field.

Change the label to “Please Enter First Name”.

First select Type as attribute and specify “firstname” as the attribute to be configured. And then provide the Label.

Prepopulate the field from the First Name of the Current Portal User.

Make the field required

Add instructions to the field

Refreshing the page in the portal updates the first name field in the portal accordingly –

Hope it helps..

Configuring OData feed for Entity List in Portal in Dynamics 365


Suppose we have Entity List configured for a custom entity name Locations.

To configure OData feed go to OData feed tab and check the Enabled checkbox.

Specify the Entity Type Name and Set Name, if none is specified the entity’s schema name is used.

Select the View to be exposed for feed.

URL for the feed

http://<<domain>>/_odata

Get the data for the LocationSet à

Filter option à

OrderBy option à

Supported options: –

Hope it helps..

Configuring Map View for Entity List in Portal in Dynamics 365


Let us create a custom entity having latitude and longitude fields (floating point data type) in it. These fields are required for configuring Map View for the entity list.

For e.g. Location is our custom entity.

We have 2 record created and have the entity list configured for the Active Location view.

Entity List for the Location custom entity on the portal :-

Open the Entity List record, go to Map View tab and check Map Enabled check box.

Configure Latitude, Longitude field.

The InfoBox title and description field will be used for the info box that pops up when hovered over the pushpin.

For Credentials, get the Bing Map key

https://www.bingmapsportal.com/

Default Center Latitude and Longitude would define the center point for the map.On refreshing the portal page, it shows the Map with the 2 records as push pin along with the records detail and Get Directions button

Info Box

Hope it helps..

Using Details View to update the Entity List records in Portal in Dynamics 365


Suppose we have configured the Entity List view for showing Contact records

https://nishantrana.me/2017/02/02/using-entity-list-to-show-crm-data-in-portal-in-dynamics-365/

Next we want to update the record in the list, for this  we need to configure Web Page for Details View field of the Entity List record.

Here we have specified Contact Details Page web page, this web page has Update Entity Form for Contact in it.

This adds the link for opening the edit page.

Edit Page: –

On Submitting the update, the record gets updated.

Similarly, we can associate a create page having Insert Entity Form in it.

Hope it helps..

Using Custom JavaScript field on Entity List to add JavaScript in Portal in Dynamics 365


Suppose we have added an Entity List on Portal to display Contact information to the portal.

https://nishantrana.me/2017/02/02/using-entity-list-to-show-crm-data-in-portal-in-dynamics-365/

Now we want to add some JavaScript to it. For this we can use the Custom JavaScript field in Options tab of Entity List.


$(document).ready(function () {

$("#EntityListControl").on("loaded", function () {

$('#EntityListControl td').filter(function () {
return this.textContent === "SYSTEM"
}).css("color", "red");

});
});

We can make use of jQuery for this. The above code selects the TD with text System and highlights it with red font colour.

Hope it helps..

Add Attach File additional settings in Entity Form in Portal in Dynamics 365


For attaching files along with an entity form through the portal, we can make use of the Add Attach File section in the Additional Settings tab of Entity Form.

For e.g. in the below Contact Us form, we have checked Attach File check box which basically add the File Control to the web page in the portal.

Allow Multiple Files lets the user attach multiple files. Label would be the label for the control.

Attach File Required option makes attaching a file mandatory and the Required Error message shows the associated error message.

Attach File Save Option– Notes i.e. files are stored as attachment to notes.

Let us see how the settings effects the display and functionality in the Portal.

Attach File label with required symbol à

Clicking on Submit without attaching a file à

Attaching multiple filesà

Clicking on Submit after entering all the required fields à

Opening the lead record inside CRM shows the attachments added to the notes à

Hope it helps..

Using Custom JavaScript field on Entity Form to add JavaScript in Portal in Dynamics 365


Suppose we have added an Entity Form on Portal to display Lead information to the portal.

https://nishantrana.me/2017/02/03/using-entity-form-to-show-crm-form-inside-portal-in-dynamics-365/

Now we want to add some JavaScript to it. For this we can use the Custom JavaScript field in Additional Settings tab of Entity Form.

We can make use of jQuery for this. The above code shows alert and also accesses the Topic field of Lead record using the schema name subject.

Alert Message –

Setting field value –

More details below

https://www.microsoft.com/en-us/dynamics/crm-setup-and-administration/custom-javascript.aspx

https://rajeevpentyala.com/2016/09/12/useful-jscript-syntaxes-adx-portal/

Hope it helps..

Using Entity Form to show CRM Form inside Portal in Dynamics 365


To show CRM Form inside Portal, go to CRM – Portal – Entity Form and let us create a new Entity Form record to show Lead form in Portal.

Here we have selected entity as lead and we are showing Summary Tab in the Lead form in insert mode in the Community Portal.

Now login to the portal with admin rights and create a new child page to display this lead form.

This adds the tab in the Portal page

Clicking on Submit shows the message

Opening CRM – Leads, we can see our lead record created.

Hope it helps.

REVIEW: Microsoft Dynamics CRM 2013 Marketing Automation


Hi,

I was very happy to receive the eBook of Microsoft Dynamic CRM 2013 Marketing Automation (Packt Publishing by Alok Singh and Sandeep Chanda) for review few days back.

7227EN_cov

It a mini guide focusing on the Marketing Module of CRM 2013, with around 100 pages divided into 6 chapters. It starts by explaining the challenges faced in marketing and how CRM 2013 can address those challenges. It then explains in detail various feature available in Microsoft Dynamics CRM 2013 that can be leveraged to successful implement the marketing module.It also talks about two of the most popular third party marketplace solution available for marketing module of CRM i.e. ClickDimensions and CoreMotives.

The book is very informative and clearly explains everything that there is in Marketing Module of CRM 2013. The authors are expert and we can clearly see their authority in the subject.

It a must read guide for all the CRM professionals.

Grab your copy here

http://goo.gl/2Ze97E

Bye.