Site Settings records specific to Registration in Portal (Dynamics 365)

In Portal, we have few Site Setting records that defines the registration behavior.

By default, if user clicks on Sign In page, we see the below options i.e. Sign In, Register and Redeem Invitation as well as Sign in with an external account.

If we want to disable Local Login then we can set the below Authentication/Registration/LocalLoginEnabled value as false.

This hides the Sign in with Local Account option.

For disabling the Registration option we can set the below site setting record as false.

This hides the Registration tabs from the sign in page

Setting both the above site settings as false, presents the user with the only option of using Azure AD for signing in to the portal.

Hope it helps..

A simple Web Template example in Portal (Dynamics 365)

Let us create a very simple web template that displays logged in user’s name and displays whether the user is in administrator role or not.

The template uses Liquid language

The Web template can be used to define Page Template.

Page template can be of type Web Template or Redirect. Redirect types would be pointing to actual physical aspx page inside the portal.

Now as we have our custom page template defined we can create a new child page in our portal using this new page template.

As we have Use Website Header and Footer checked the page takes it from the web site.

This is how the page renders with our new template

If we uncheck Use Website Header and Footer checkbox, the page renders with only the content (source) defined within the web template.

Apart from being used to define page template, web template can be inserted into the page through editing the copy of the page.

  • Click on Edit

  • Select Insert Template

  • Select the Hello World Template (it also displays the preview) and click Ok.

  • Click on Save

  • This adds our custom web template in the page.

This was a very basic example, please check the below link that contains all the details and real world examples.

https://community.adxstudio.com/products/adxstudio-portals/documentation/configuration-guide/liquid-templates/basics/web-template/

Hope it helps..

Using bootstrap classes and components in Portal (Dynamics 365)

As Portals are based on Bootstrap framework we can make use of classes, components etc. specified as part of the framework in our Portal.

Below we have created a new blank page to which we will add content.

Click on Edit in the content editor.

Click on Edit Source icon.

For reference go to the getbootstrap web site

Below are some of the classes that we will add

Lead Class –

Table table-striped class –

Badges Component

Breadcrumbs

Below is our sample source code

This is how it renders in the page.

Hope it helps..

Portal Blog Post List

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..