Box 1: 1.0.0.0

When identifying versions of the app solution, all dependencies, entities, and user interfaces components must be identified to avoid any unintentional issues caused by reverting individual components to a previous version.

A solution’s version has the following format: major.minor.build.revision. An update must have a higher major, minor, build or revision number than the parent solution. For example, for a base solution version 3.1.5.7, a small update could be a version 3.1.5.8 or a slightly more signficant update could have version 3.1.7.0. A substantially more significant update could be version 3.2.0.0.

Box 2: 20.11.1.1

Scenario:

You must use the following version control numbering scheme:

- Major: The last two digits of the year the app is packaged

- Minor: Two digits that represent the month when the app is packaged

- Build: A number that is incremented to represent significant changes to the app

- Revision: The incremented revision for a package

New versions of the application must completely replace previous versions of the app.

C: You can create a table in Dataverse and fill that table with data from an OData feed by using Power Query. You can use the same techniques to integrate data from these online and on-premises sources, among others:

SQL Server

Salesforce

IBM DB2

Access

Excel

Web APIs

OData feeds

Text files

D: You can create a new Dataverse table that stores all the metadata from the dataflow run. For every refresh of a dataflow, a record is added to this table. You can also store metadata for multiple dataflow runs in the same table.