Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Last year, I built out a simple approach for script management in Dynamics Portals, including a model for managing shared script modules and building common reusable validators across Portal components. I posted about some of this work in prior posts: Dynamics Portals Field Validation and Dynamics Portals Script Management.
That project began as an Adxstudio v7 project that we later upgraded to the Dynamics Portals online solution. The model for handling scripts and the helper methods around validation held up very well during the upgrade. We required only minor updates for very specific cases, such as how a tool tip rendered from Adxstudios v7 to the Dynamics Portals.
Since I wrote these posts, I took some time to rework these ideas into a shared solution and examples with the intention of sharing as an open source project.
I recently started a new Dynamics Portals project and we began implementing client side scripting, such as adding custom validators and hiding/showing items based on field values. This was a nice chance to test out the solution and it’s worked well so far. My teammate and I have even added some updates in the short time we’ve been testing and we’ve been able to add some complex validations in a very short amount of time.
As mentioned, I had plans to post this solution to GitHub and add some examples. I had hoped to post working samples on a shared Dynamics Portal, but that’s been delayed for a bit. Luckily, preparing for that deployment forced me to clean up the code, include comments for TypeScript Intellisense, and work up some quick samples.
So instead of waiting for an environment, I’ve decided to post the solution to GitHub with instructions for setup and use in your project and environment. Once I get a sample environment up that will stick around for more than a few months, I’ll update the repository with that information.
The current project posted on GitHub is a standard Visual Studio solution that includes the shared scripts in TypeScript format. The Wiki page includes some details on the solution setup and how to deploy to Portals. That’s a work in progress, so keep an eye out for updates!
As a brief overview, the core of the solution resides in three TypeScript modules:
You can check out the repository here: DynamicsPortalScripts.
I’ll be updating this this repository documentation with more detail on the individual modules and usage examples. As my current project continues, I am sure we will uncover some issues, make revisions, and include some additions based on new scenarios. As we make these revisions and additions, I will be sure to sync them up with the GitHub repository.
Any comments, suggestions, and/or issues can be posted to the repository Issues section, or just drop me a line here!
Business Applications communities