Announcing Single View Builder 2.1

Wednesday, February 26, 2020

What is new ?

Single View Builder version 2.1 innovations:

  • We now can fully leverage the capabilities of the Microsoft Power Platform and offer all our custom components as PCF controls Important to note: we still offer all Web Resource variants of our SVB control within the SVB V2.1 solution.
  • A new 2D-visualization option for the Tile View component, i.e. Carousel
  • A Clone-option facilitating the SVB architect to realize SVB implementations more efficient and less prone to errors. It is an option made available on each component (e.g. Tile View component) as well as on the child level of each component (e.g. Tile Group, Tile Indicator for that Tile View component)
  • License count check
 

What is deprecated and deemphasized With Single View Builder version 2.1 we’ve deprecated and deemphasized the following:

  • “Navigate To”: In prior versions of Dynamics 365 CRM we offered through configuration of “Navigate To” as standard way to provide convenient navigation through TABs. This functionality has meanwhile been added as default functionality within Microsoft Dynamics 365. If you still want to use “Navigate To”-configuration option, please refer to SVB manual of versions prior to version 2.1
  • Web Resources-versions of our SVB controls are still supported, but deemphasized: Microsoft Dynamics CRM web resources are “web” files that are stored within CRM that contain content that is useful for integrating web page functionality into the Microsoft Dynamics CRM interface. Because these web resources are stored within the Microsoft Dynamics CRM database, they can be reused throughout the system in different forms or entities and can be deployed using Solutions. Microsoft has been increasingly vocal and directive about customers and ISVs starting to move to use the Power Apps Platform, away from using Web Resources. Early September 2019, Microsoft announced they will deprecate the legacy web client and as such customers and ISV solution will have to transition to the Unified Interface before October 1, 2020 (cf. https://cloudblogs.microsoft.com/dynamics365/it/2019/09/10/announcingthe-timeline-to-move-to-unified-interface/). Once having installed the Single View Builder V2.1 solution package, we therefore strongly advice to migrate your existing SVB configuration to start using the Power Apps Component Framework (PCF) Controls. To facilitate a quick migration of the existing configuration to PCF, we provide you within our SVB V2.1 solution he necessary script to automate that migration process.