Follow the steps in this article to install North52 for Dynamics 365 Portals.




  • It is assumed that you have already installed North52 with a valid licence key in your Dynamics 365 environment
  • It is assumed that you configured and installed the Portal add-on for Dynamics 365. See the Dynamics Portal provisioning guide. We suggest you use the Customer Self-Service or Community Portal.

When you deploy North52 for Portals several records will be deployed in your Dynamics 365 environment. The record naming convention for each record will generally follow this template:

North52 Formula Calculation - <Portal Site name> - <Portal Language>


Using a portal site called Customer Self-Service and the language is English then the naming convention will be:

North52 Formula Calculation - Customer Self-Service - English

What Gets Installed

When you deploy North52 for Dynamics Portals the following records will be installed:

  • Web Template
  • Page Template
  • Web Page
  • Web Page Access Control Rule
  • Web File
  • Annotation (note) on the Web File
  • Entity Permission

To deploy North52 you need to know the name of the following records:

  1. Website name - (adx_website)
  2. Language - (adx_language
  3. Root web page name - (adx_webpage)
  4. Publish state - (adx_publishingstate)
  5. Webrole name - (adx_webrole)

This information will be used in the deployment process.

In this example we will deploy North52 to a portal that is already set up with the name Customer Self-Service.

Pre-Deployment Step

During deployment North52 for Dynamics Portals will install a JavaScript file connected to a Web File, therefore we need to temporarily allow JS file extensions during the deployment. To do this we need to remove js from the list of blocked file extensions (you will re-add it at the end of the deployment process):

  • Go to and select your environment
  • Select Settings > Product > Privacy + Security 
  • Find and delete js; from the list of Blocked Attachments
  • Click OK

Find Information Required for Deployment

The deployment process requires 5 parameters which can all be found via the Portal Management App on your Dynamics instance


Find the Web Site name

Open up Websites and it will be listed there:

Note down the Name of the website that you want to install North52 for Dynamics Portals on; in this example it is Community Portal

Find the Website Language

Open the website and you will see the default language listed on the first page:

In this example, we are using English

Find the Root Web Page

You can find the Root web page listed in the Website record, you will need to note this down as well:

In this example the name is Home

Find the Publishing State

Note down the name of the record that is Published - or the local language equivalent

Find the Web Role Name

Note down the name of the record that identifies Authenticated Users:

 In this example the name is Authenticated Users


Use the information found the previous section to build the Command String needed for deployment. Each information parameter is separated by the pipe symbol | like in the following template:


In our example the command string will be composed of the following records:

  • Website Name: Community Portal
  • Language: English
  • Parent Page: Home
  • Publishing State: Published
  • Web Role: Authenticated Users

Command String

Community Portal|English|Home|Published|Authenticated Users
  1. Open the North52 App and select Administration Operations 
  2. Select Portal Install from the listed options 
    • This will populate the Comments box with sample data
    • Paste your command string into the Parameters box
    • Click Execute

This will install all the necessary components for North52 to operate in Powers Apps Portals.

The installation process can take around 60 seconds to complete.

Post Deployment Step

When the save completes, re-open Settings > System > Administration > System Settings and add js; to the list of Set blocked file extensions for attachments again.