Download the plugin and locate the jquery.mask.min.js file under the “dist” folder
Create a Web File in your CDS environment
Note that by default you can’t upload a .JS file, I am going to rename the file to .ES to bypass this validation (you can also change your environment settings but this is not recommended) – but keep the Partial URL as .JS
I am going to set the parent page as Home
I am going to set it to be hidden from site map and excluded from search
Adding JS library reference
We need to reference the JS, open your Web Page (content page) and add the following to your HTML “copy” field:
You can also add the above line to the “Tracking Code” Content Snippet, and this would be loaded in every page, in my example this JS would only be loaded in the Profile Web Page.
Still in your content page, navigate to the Advanced tab and add the following code:
Power Apps Portals provides us with very quick and simple ways to expose data from the D365 system into an external portal. Often, we have requirements to export or print the data using current Word Templates present in D365, but unfortunately there is no OOB feature (currently) for performing this task.
In this post, I will describe what is available using the OOB configuration from the portal, and how to extend it in order to export the data in the application. The idea of this post is not explain the Portal objects (Web Template, Entity List etc), you can find content on the Power Apps Portals on the following link: https://docs.microsoft.com/en-us/dynamics365/portals/configure-portal
For this demo, we will be using the following setup:
Power Apps Portals Starter (Version 22.214.171.124)
Before going to the step-by-step, below you can see what we will be achieving by going through the end of the post:
As a starting point, we will create an Entity List and Web Page record to present a list of the Active Contacts:
This is how the list will be rendered by default in your Portal page:
For Entity List records, we have the option (OOB) to add an Export to Excel button, this can be achieved by:
Open your Entity List record
Navigate to tab Options
In the Grid Configuration add a “Download” action and add a label
This is how the button is shown on the Portal, and once clicked, you will download an Excel file with the list content:
Unfortunately, this excel file is rendered just like our Advanced Find Export to Excel feature, which is not bad, but usually when we have a Website, we (and our customers) want this information to be presented in a friendlier way.
Now create a new Page Template and Web Template and make sure to associate the new Page Template to your existing Web Page:
For the Web Template record, I basically copied the content from the OOB Web Template “Full Page” and removed a few lines, leaving only the condition that will render the Entity List.
At this moment, nothing has changed and our Web Page is behaving exactly the same way as before.
Now, we are going back to our recently created Web Template, and add the following:
Give a name for the Div that is holding your Entity List
Add the Button for printing (outside the div)
Add DIV with logo inside your print DIV
Show the Logo before setting the HTML content, also hide the Command Bar which will contain your Search Box / View Selector / Create or Download button (in case you setup any of those)
After setting the HTML Content, Hide the Logo and show again the Command Bar
In the top of the HTML, before the <head>, add:
Now we have our Logo being shown only for the printed window, and we have the same layout as the Portal webpage.
The following is the final code for the Web Template:
You can also use the same implementation to any other Web Page in your Portal, this way you can, for example, create a custom Web Template for your entity, displaying the information the way you need and add the Print button, showing and hiding anything on the Web Page if required, like logos, sensitive information, etc.
Maybe in the future Microsoft provides us a way to export using Word or Excel templates, which would be a very nice feature.
I hope this post has been helpful to you and your Power Apps Portals implementation.