Validating & comparing features across channels and releases

Validating & comparing features across channels and releases

he previous article about the Comparison of the Monthly Channel and Semi-Annual Channel for your model-driven app: https://www.dhirubhai.net/pulse/comparison-monthly-channel-semi-annual-your-app-jakub-homola-kl3se/

The previous article about the Configuring release channel for your model-driven app: https://www.dhirubhai.net/pulse/configuring-release-channel-your-model-driven-app-jakub-homola-f0gwe/

Validating the next monthly release

If you want to check and test how your Model-driven application will behave in the next release, simply add '&channelrelease=next' to the end of the URL. This way, you can verify the future compatibility of your customizations with Microsoft's new features.

.
.

Comparing features across channels and releases

If you have set the 'monthly channel' mode for end users and an error occurs in the standard Model-driven application, Microsoft recommends the following procedure:

  • Check if the unexpected behavior exists in the semi-annual channel by using the URL parameter?&channel=semiannual. If the behavior also exists in the semi-annual channel, it's unrelated to the monthly channel and should follow normal support processes.
  • Check if the unexpected behavior exists in the previous monthly release by using the URL parameter?&channelrelease=?with the prior release short name like?2308. If the two monthly releases behave the same, then it's likely unrelated to a specific monthly channel release and should follow normal support processes.
  • When a change is noticed between monthly releases, review the changed features in?Unified Interface monthly channel releases?to learn more.

.
.



要查看或添加评论,请登录

社区洞察

其他会员也浏览了