Jukka Niiranen’s Post

View profile for Jukka Niiranen, graphic

The Original Power Platform Advisor. 11x Microsoft MVP. Low-code 4 life.

Is it a "preview" if it's enabled by default? Well, that's just how #PowerApps canvas app feature roll-out stages work.🚥 It is a concept that is quite different from the Power Platform level preview/GA features. There you enable the switch on an environment level and everything in preview is under the disclaimer "not supported by Microsoft for production use". Canvas previews are app level switches. Whenever you create a new canvas app, though, most of the preview feature switches are on by default. Today the list is 12/13 features. What's the idea behind such widespread use of previews? I recommend reading through Docs page for "understand experimental, preview, and retired features in canvas apps": https://lnkd.in/dfziuJeV Here the guidance from MS is to start migrating existing apps to use a feature once it reaches the preview stage. More precisely: "These features are ready for wide circulation, have been documented, and are FULLY SUPPORTED. One day, the option to turn off these features will be removed, and they'll become a permanent part of the product." It is quite a different approach indeed to what the #Dynamics365 side of the business applications platform has been accustomed to. In the canvas world of apps, such feature flags may remain in the product for a very long time. Also, often existing apps are not automatically migrated to use the new features, unless the app maker explicitly performs this update. I've often said that "in the cloud, GA is the new beta". Things change all the time, and they aren't always that robust upon first release. Canvas apps are taking things even further, causing confusion among customers and partners on whether the preview tag is something that actually means it's not production ready nor supported. What's your policy on this? Do you always disable these preview features when shipping canvas apps to production? Or do you trust that they are stable enought, and supported by Microsoft if issues arise?

  • No alternative text description for this image
Jukka Niiranen

The Original Power Platform Advisor. 11x Microsoft MVP. Low-code 4 life.

1y

The latest announcement of Power Fx error hanlding preview is a great practical example of this policy: https://powerapps.microsoft.com/en-us/blog/power-fx-error-handling-graduates-to-preview/ "We are rolling this out slowly as it is such a big change. All of you will soon see that the Formula-level error handling switch has moved from experimental to preview in the settings (as of version 3.22082). It will still be default to off for most tenants. Over the coming weeks we will slowly change the default for new apps only to on across the tenants. Makers can still disable this feature and will be able to do so for a long time." "I say again: we are changing the default for new apps only. Existing apps will continue running as they always have. We have no plans at this time to turn this on for existing apps, and as this is such a big change, we may never do this and make this a permanently available switch. Your feedback will guide us."

Like
Reply
Sharon Smith

Solution Architect & Strategist | Microsoft Dynamics 365 | Power Platform | ERP | 14x Microsoft Certified | Microsoft Catalyst Accredited | IBM Design Thinking Co-Creator | HeuristicDev Blogger

1y

Thank you Jukka Niiranen. As ever you're reading my mind (or my comments & questions elsewhere 😉). So with a Power App that gets a regular monthly update, like the CoE Starter Kit, are we safe to assume that unless stated otherwise, all the functionality will be in the 'Shipped' stage? Probably a better example is the newly released Power Platform Build Tools v2.0 where the new MS Docs page at https://lnkd.in/enUmFfPQ  only mentions "preview" against the 'pac solution sync'. Or would you always be wiser to read all the Release Notes for the new version at the Marketplace (e.g. https://lnkd.in/eCCFa4zc in our above example) to be sure (if you can ever be sure of anything...)?

Like
Reply
Hamish Sheild

Enabling teams to create user centric apps that drive business success.

1y

Thanks for sharing Jukka Niiranen, I did not realise there was a difference between what 'preview' means for Canvas apps compared to the rest of the platform. When it comes to preview features and shipping to production, I usually assess the risk of the preview component breaking or being pulled vs the benefits that the feature provides to the end users. Often the benefits outweigh the risk. Now that I know more about the Canvas app 'preview' features I would say leave them all on!

Sharon Smith

Solution Architect & Strategist | Microsoft Dynamics 365 | Power Platform | ERP | 14x Microsoft Certified | Microsoft Catalyst Accredited | IBM Design Thinking Co-Creator | HeuristicDev Blogger

1y

Carl Campbell this one's really useful for understanding how MS' releases work.

Like
Reply
See more comments

To view or add a comment, sign in

Explore topics