Upload your Electronic Reporting objects to Dataverse solution automatically – How the new ALM in ER will look like.

In a previous post, I explained how I did to migrate all the existing ERs of a project to Dataverse. But what about the new ER reports or versions created after that? After months of not knowing what the new development/deployment cycle will look like due to the deprecation of RCS and the move to Dataverse, we finally have an answer! There is a new functionality to streamline the process of uploading to the Dataverse repository your Electronic Reporting objects right after you have developed and tested them in your development environment! That way you will be able to easily distribute them to all the different environments and also keep all your reports in one place, making easier to avoid ending up having divergent versions of the same report.

This functionality is included into the Upload into repository (that it normally worked so-so), but that now is a live safer/changer for all the ER developers that want to do the things correctly and use a Repository. … More Upload your Electronic Reporting objects to Dataverse solution automatically – How the new ALM in ER will look like.

Migrate RCS Electronic Reportings (ER) to Dataverse: Step-by-Step Guide

As you all may know, RCS (Regulatory Configuration Service) is being deprecated as the Electronic Reporting objects repository. No new provisioning of RCS environments from 10.0.39, and Microsoft will fully shut down it by the 1st of August of 2024. The new repository is nothing more and nothing less than the good Dataverse, so how do we migrate our ERs? keep reading to have the full picture of the process. … More Migrate RCS Electronic Reportings (ER) to Dataverse: Step-by-Step Guide