This document describes the dataflow used to import external Minecraft items into the application and map them to the Recipe table, enhancing the value of existing data that we have in the model driven app. The recipes are then used by our customer/user. 

1. Dataflow Creation 

A new dataflow is created using a blank query. The query connects to a public Minecraft API to retrieve item data in JSON format. 

2. Minecraft API Query 

The blank query is named “Get Items” and contains logic that calls the Minecraft API, converts the response into a table, and selects the required item columns. 

3. Dataflow Connection 

The connection is configured to allow the dataflow to access the Minecraft Items API. 

4. Execute the query 

Once the connection is established, the query is executed automatically to retrieve data from the Minecraft API. 

5. Table Mapping 

The output of the query is mapped to the desired Dataverse table (la_recipe). Each column from the API response is mapped to its corresponding column in the Recipe table. 

6. Dataflow Publish 

After mapping, the dataflow is published so it can be used for importing data. 

7. Running the Dataflow 

The dataflow can be scheduled or run manually. The first execution occurs automatically if it is set up as manual. The progress and status can be monitored. 

8. Check Results 

After the dataflow has run, the imported data can be verified in the model-driven app to confirm that Minecraft items are available in the Recipe table.