Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I’ve published version 1.0.9 of spkl to NuGet - this adds the following new features:
This was a tricky one due to the CrmSvcUtil not making it easy to prevent multiple enums being output where a global optionset is used, but you can now add the following to your spkl.json early bound section to generate global optionset enums.
In a future update, I’ll add the ability to filter out the enums to only those used.
The solution packager allows you to manage your Dynamics metadata inside a Visual Studio project by extracting the solution into separate xml files. When you need to combine multiple updates from code comments, you can then use the packager to re-combine and import into Dynamics. To configure the solution packager task you can add the following to your spkl.json
The solutions section defines a solution that can be extracted to individual xml files to make
versioning of Dynamics metadata (entities, attributes etc) easier
The unique name of the solution to extract, unpack, pack and import
The relative folder path to store the extracted solution metadata xml files
Set to 'true' to increment the minor version number before importing from the xml files
There are two .bat files provided that will call:
This will extract the solution specifed in the spkl.json into the packagepath as multiple xml files
This will re-pack the xml files and import into Dynamics - optionally increasing the version number of the solution to account for the new build.
Business Applications communities