Question
You plan to create a dataflow to import data into Microsoft Dataverse by using Power Query.
The dataflow has the following requirements:
• A table of aggregated data must be created in dataflow storage.
• A unique identifier must be created for the table.
You need to configure the dataflow.
Which solutions should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Explanation
Table of aggregated data: Computed entity — In a dataflow, a computed entity is a table whose data is produced by running additional Power Query transformations (such as group-by aggregations, joins, or summarizations) over data already loaded into dataflow storage, and the result is materialized and stored there rather than re-pulled from the source. A linked entity only references a table from another dataflow without performing or storing the aggregation, and a merge query is just a single transformation step, not a stored table.
Unique identifier: Alternate key — When a dataflow loads data into Dataverse, an alternate key defines the column (or combination of columns) that uniquely identifies each row, so the dataflow can match incoming records to existing rows and perform upserts instead of creating duplicates. A plain key column in Power Query does not create the uniqueness constraint that Dataverse uses for record matching during import.
