Hide “Sign in with an external account” from Dynamics 365 Portal


To hide the Sign in with an external account section from the Sign In and Register page of the portal.

Set the following site settings value to false à

Followed by Restart of the portal.

To add any additional JavaScript or HTML, for e.g. we wanted to disable the Email text box on the Register page,

Go to Portals à Content Snippets and create a new code snippet record

The output:-

code

The helpful post –

http://benitezhere.blogspot.ae/2018/01/hiding-sign-in-with-external-account.html

http://arpitmscrmhunt.blogspot.ae/2017/12/customise-registration-page-in-crm.html

Hope it helps..

Unknown Error or Resource not found for the segment ‘msdyn_FpsAction’ in Schedule Board in Field Service in Dynamics 365.


Hi,

Recently we configured the portal trial instance and installed Partner Field Service portal in it .

However, while trying to access Field Service à Schedule Board, we were getting the below errors

Eventually it turned out that the issue was caused because of the certain processes being in draft state.

The post which helped in fixing this issue

https://glinks.co.uk/2017/01/06/field-services-schedule-board-unknown-error/

Hope it helps..

Partner Field Service Portal in Dynamics 365.


Dynamics 365 comes with Partner Field Service portal which helps Partners manage work order, service request, assets, invoices, opportunities etc. from within the portal.

Go to Administrator Center, select Portal and click on Manage.

Select Manage Dynamics 365 Instance

Click on Update Dynamics 365 Instance

Select Partner as Audience and Partner Field Service as the portal to be deployed

Once installed this is how Partner Portal looks like

Below are the different menu options that comes OOB.

Partner Program

Opportunities

Customers

Field Service

Below are the Entity Forms associated to the Partner Portal Web site created in CRM.

Below are the Entity Lists associated to the Partner Portal Web site created in CRM.

Around 121 Entity Permission records are added by the Partner Portal

Web Roles specific to Partner Portal.

Below are some of the permission for the Partner Admin web role.

Once the portal is setup next step would be to Become a Partner. Click on Begin Here.

Update the profile and click on submit.

Within CRM, the admin user needs to run the Approve Partner Application workflow on the corresponding portal contact user record.

After workflow succeeds we can assign appropriate web roles to the portal contact user.

The portal user can create customer contacts record

The portal user can raise Service Requests from within the portal.

Can manage Work Orders.

Can manage Opportunities.

The portal has the Dashboard that shows the details around the opportunity and the cases.

Hope it helps..

Edit Primary Navigation in Portal in Dynamics 365


For updating the Navigation, login to the portal with the user having Administrator web role.

Hover over the Navigation and select Edit

This opens up the dialog box, here we can edit or insert a new navigation link. To add new navigation link click on “+”

We can either specify any existing page within portal or can point to any external URL and can also show up image + text or image only.

This adds the new navigation link

Similarly, we can add new child links or move a link as child link which then appears as drop down. Here we have moved the new Search Home link inside Support by dragging.

The updated navigation looks like below

Hope it helps..

Manage Dynamics 365 Portal Instance


Suppose we have Community Portal configured in our Dynamics 365 Instance.

Now we would like to have Custom Portal instead of Community Portal associated to our instance.

To configure this, we need go to Admin Centre à Select Portal and Click on Manage

Then select Manage Dynamic 365 CRM Instance and then Update Dynamics 365 Instance

From there we can select the Portal Audience and corresponding Portal to be deployed.

This will install the corresponding portal solution to our CRM Instance.

Now our portal URL will show up the Custom Portal instead of Community Portal.

To switch back to community portal, we can select Portal Details and Update Portal Binding to point it to website we want it to bind to.

Suppose we have Employee self-service portal deployed to our instance and we would like to update binding to it.

Below we select Employee self-service as the web site record and click on Update.

Once update is done, opening the Base Portal URL will open up Employee self-service portal instead of Custom Portal now.

Hope it helps..

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

Applying Theme in Portal in Dynamics 365


Suppose we have the below portal configured whose theme we would like to change.

As Portal is based on Bootstrap framework, we can apply any of free bootstrap themes to it.

Go to the below site which offers few free themes.

https://bootswatch.com/

Here we have download the Cerulean theme’s bootstrap.min.css file.

Now inside the portal home page, create a new child file

Name the file as bootstap.min.css

Basically, this creates a web file in CRM that has the bootstrap.min.css file associated as notes attachment to it. (with Home page as the parent page)

Refresh the portal to see the changes

Another way of doing the same is create a new web file or update the bootstrap file attached as attachment to notes in the existing web file.

Download a new theme file.

Delete the existing attachment and upload this newly downloaded theme file.

Refresh the portal.

The theme here gets applied to all the child pages of Home. If we want a different theme for any of the child pages, we can repeat the same step.

For e.g. we want a different theme to be applied to Blog and its child pages. For this we will create a new child file, upload the theme file.

On clicking on any of the child pages of the Blog we can see the new theme applied only to its child 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..

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