Jukka Niiranen

Tag: Business Application Platform

  • Winter in July: Release Notes for Next Dynamics 365 Version

    Winter in July: Release Notes for Next Dynamics 365 Version

    While I’m over in Finland enjoying the biggest and longest heatwave ever, some of my fellow MVPs and Dynamics 365 community members were attending the first ever Microsoft Business Applications Summit this week on the other side of the globe in Seattle. As much as I would have enjoyed sitting in cold & dark conference rooms instead of trying to hide from the burning sunlight, this time I had to rely on the others to share the latest news from #MSBizAppsSummit while I attempt to enjoy the summer vacation.

    A large share of the conference’s announcements are covered in the October ’18 Release Notes, which you can download in PDF format right here. This is a massive “drop” that follows the format of what we already saw with the previous April ’18 release. Even though it’s been made available during the summer heat, it’s actually a list of features that Microsoft intends to (mostly) make available between October 2018 and March 2019. So, winter came early this year, which is a positive thing, since now we have several months of advance notice of what’s in the product team’s pipeline. These release notes essentially replace the earlier roadmap.dynamics.com website, which in itself was kinda cool (running on top of Dynamics 365 Portals and all) but didn’t communicate the actual road ahead all that well. So, these twice a year PDF releases with ongoing updates to their detailed content is the thing you need to pay attention to now.

    One small but notable difference is that Microsoft is no longer calling it “Dynamics 365 Release Notes” but “Business Applications Release Notes”, which together with the Summit’s name reflects the new context in which we all should approach whatever parts of the toolkit we use in our end user solutions. Recently also the Microsoft Most Valuable Professional program updated its terminology, and now the previous Business Solutions MVPs are in the Business Applications MVP category.

    The previous April 2018 release was the first time when we saw the new organizational structure of Microsoft Business Applications Group (“BAG”) bringing previously separate product offerings under one roof, with CRM & ERP products being represented in the same release notes list as PowerApps, Flow, Power BI. That also was the time when things like the Common Data Service for Apps were announced as replacements for what XRM previously stood for. However, from a raw functionality level there appeared to be a greater urgency in reaching GDPR compliance before the May 25th deadline than to actually push out new integrated features for the CDS for Apps platform.

    Reading through the October 2018 release notes, this time it’s very different. There are huge steps being take to bring together the “ex-XRM” technologies with the newer products and make it truly one Power Platform. Here are selected highlights:

    • PowerApps Canvas Apps and Flows can now been included inside CDS for Apps solutions, giving them the ALM story for enterprise grade deployment across different dev/test/UAT/prod instances. This clearly makes them no longer a “power user” focus tool but a building block for credible business applications.
    • PowerApps Canvas Apps can be embedded inside the model-driven app entity forms. The traditional UI of XRM apps that was generated from metadata will get a touch of pixel-perfect design options that the Canvas Apps have always been about. This ability coincides with the new options to freely set the app size instead of earlier phone/tablet format limitations.
    • Flow is promised to reach parity with async workflows. Even though the transactional capabilities of real-time workflows (similar to plug-ins) is not yet within October 2018 scope, that’s one bold step to make the XRM workflows history and move their logic into Flows.
    • Power BI reports & tiles can be embedded onto CDS for Apps entity forms and the record context as well as any record attribute can be passed to them for data query and visualization filtering. Surely pretty much anyone has at one time wished “gee, wouldn’t it be sweet if instead of working with this limited ASP.NET chart XML from Dynamics CRM 2011 we could leverage those modern Power BI charts instead”. Well, that day is getting closer!
    • PowerApps Canvas Apps will FINALLY offer native support for lookups, option sets and datetime fields. For anyone who’s tried to replicate pretty much any CRM functionality with PowerApps, this will have been a very early stumbling block. Not so easy to solve with separate product teams inside MSFT apparently, but within the new Business Applications Group these gaps for real life solutions can now be filled.
    • There will be a single mobile “player” for both Model-driven Apps and Canvas Apps. When previously the Dynamics 365 Customer Engagement mobile app for Unified Interface and the PowerApps apps lived behind separate app icons on your phone, soon the users may no longer see any difference when switching between different business applications.

    These are only a few items in the long list of upcoming features that the 239 pages of October 2018 release notes contain. A lot of important unification is also taking place in the author and admin experience of how Dynamics 365 Customer Engagement apps, CDS for Apps platform, PowerApps Canvas Apps and Flow can be used together for your solution design needs. Similarly, a lot of advances are being made on the UCI front, with the legacy web client being more and more replace with Unified Interface. Then there’s the whole CDS for Analytics side of things coming up, with promises for new AI apps and capabilities. You’re going to need to read through a wealth of blog posts to grasp the full spectrum of what Microsoft is planning to launch, so a good place to start is the Scott Durow Top 10 favourite features in this release.

    The April 2018 release for Dynamics 365 CE was a bit of a surprise due to the fact that it wasn’t officially a major release like v10 or even v9.1, instead it was only a v9.0.2 update. Deployed automatically to your v9 instances, with no CDU process to schedule the update from the available time slots. Now in July we got a confirmation from Microsoft that this reflects the way all future updates will be rolled out, in the blog post Modernizing the way we update Dynamics 365. Looking at how the Power Platform will increasingly be consisting of functionality that isn’t found in the “XRM server”, the automatic updates make a whole lot of sense. It remains to be seen how the remaining on-premises customers will be serviced with the updates and to what extent there will be feature parity. At least we now got a confirmation at the Business Applications Summit 2018 that there will be a new on-prem release this fall, so there appears to be a plan to bring things like UCI available for those who still prefer to run their own business application servers.

  • Exploring CDS for Apps Platform Licensing (PowerApps)

    Exploring CDS for Apps Platform Licensing (PowerApps)

    When Microsoft originally made the Spring 2018 release announcement for Business Applications products and essentially promoted XRM to be the Common Data Service for Apps, they didn’t yet disclose the finer details about how the CDS for Apps license model would work outside the Dynamics 365 Apps and Plans that we’re familiar with. On May 1st the details were revealed alongside the blog post “Which PowerApps plan do I need for model-driven apps and CDS for Apps”.

    In his earlier blog post, Frank Weigel announced that PowerApps Plan 2 officially became the platform SKU for CDS for Apps. In the updated PowerApps pricing page we can see that actually the license types and prices have effectively remained the same as they were before Spring 2018 release:

    The changes are mostly on the new Model-driven App side (formerly XRM), but since there’s now also a wealth of server-side functionality made available for PowerApps via the new CDS for Apps concept, it also affects the Canvas Apps designers. Let’s dive into the details and explore the license model from a few different angles.

    PowerApps for the Productivity Folks

    A customer who’s got Office 365 will already have the specific PowerApps license type included in that subscription. As stated by the Licensing overview page over on docs.microsoft.com, this allows them to create and run applications within the context of this service (O365), as well as connect to “common cloud services including Box.com, Facebook, and many more”. Not D365 and not CDS, but that still covers a lot of interesting scenarios for building an app to replace a manual process that used to run on email or Excel.

    Since it never was a “pure business app” like Dynamics 365 CRM and ERP products, PowerApps has grown into a highly versatile tool that connects with the more mainstream Microsoft services. You can embed them into a wide variety of places within your MS Cloud environment, like on Power BI dashboards or modern SharePoint pages. For your data collection forms, they are InfoPath on steroids. An Office 365 customer might therefore get pretty far with just mashing up the UI’s of different apps and storing data into less structured places like SharePoint lists or OneDrive files.

    If they’d like to introduce more solid capabilities for relational data modeling, process automation and granular security management, the PowerApps Plan 1 would unlock this scenario for €5.90 per user. With this the data could be managed in CDS for Apps database, a much more robust back end for a business application than simple lists in the Office tools. The users still couldn’t access any Dynamics 365 style UI, since Plan 1 doesn’t grant the access to Model-driven Apps. You would need to construct the required lists, forms, navigation and client side logic with the traditional PowerApps “maker” experience and publish it through the same channels as what the Office 365 users already have access to.

    This Plan 1 approach could be viewed as the first step up from the starting point where a knowledgeable power user or “citizen developer” had built a PowerApp with the license they already had via Office 365 and now the app needs to be adopted more widely within the organization. The new admins and designers of the app would need a Plan 2 license for €33.70 but the users could be assigned the cheaper Plan 1 license for €5.90 a piece. It shouldn’t be too difficult a business case to build if there’s real demand for the app and it either saves time or money in some business process that used to be a painful manual operation before Microsoft Cloud came along. If things work out well, these same P1 licensed users can then go and use any number of apps that the P2 power users design for them, since each P2 gets 2 databases with it and no limits on how many PowerApps you have on top of those.

    PowerApps for the Dynamics Crowd

    Dynamics 365 has a powerful, growing set of first party Apps from Microsoft, but sometimes there isn’t an app for that particular business process you’re looking to digitally transform with the help of MS Cloud. This is where the power of the platform comes to rescue and saves you from custom software development and maintenance efforts. Earlier this platform was called “eXtended Relationship Management” (XRM) but now we refer to it as the Common Data Service for Apps. We don’t even need to buy a Dynamics 365 license for it anymore, since we could just use PowerApps Plan 2 instead.

    What sets Plan 2 apart from Plan 1 is that you can work with the application data via the Model-driven App UI that is automatically generated for you when you design your data model. Sure, you’ll need to configure the details of it to deliver a pleasant UX, but you’re not forced into pixel-perfect design work of the Canvas App. Navigation is provided for you, there’s the full search capability, you can quickly configure dashboards, Business Rules can make your entity forms adapt to field data values, and so on. With the new Unified Interface your Model-driven App will adapt to any screen size, and the solution framework ensures you can easily transport your customizations across environments. The Model-driven sample apps will give you a quick idea of what a non-Dynamics 365 app on CDS might look like.

    There are limitations, though, and you’ll find them listed on the “license requirements for entities” page on CDS for Apps documentation. As mentioned, P1 users can’t access the Model-driven App UI, but they also aren’t authorized to access a Canvas App that runs on a CDS for Apps instance and uses entities that have real-time workflows or plug-ins associated with them. These require a P2 license, which unlocks the full XRM style functionality of the platform.

    Now, just because the Dynamics 365 first party Apps from Microsoft are built on the same platform as your custom Model-driven Apps, that doesn’t mean a PowerApps P2 license would fully cover their usage. There’s a list of restricted entities that are used in MS apps like Sales, Customer Service, Field Service, that you aren’t allowed to touch without the proper Dynamics 365 license. For example, you’re free to work with leads and opportunities, but you can’t use cases or knowledge articles in your custom PowerApps – because Microsoft said so.

    For an overview of the different license types and privileges, be sure to check out the great blog posts and ever so slick videos that MVP Scott Durow has created for explaning the topic of PowerApps to those of us who’ve got a Dynamics background.

    PowerApps vs. Dynamics 365 License Model

    Just because we now have something declared as Platform SKU on a Microsoft blog post doesn’t mean we get to skip the finer details laid out in the Dynamics 365 Licensing Guide. Anyone working on the partner side must have experienced the amount of documentation that goes into performing changes to the licensing practices of Dynamics products. (Remember that deck about transition from Dynamics CRM to Dynamics 365? Of course you do, how could you ever forget…) I’ve got a feeling that we’re going to see more licensing related information emerge about the new PowerApps Model-driven Apps offering in the near future, as this initial announcement raises many questions that need to be answered before customers and partners can fully embrace the new platform opportunities. (more…)