Rework cosmicworks section

Author: seesharprun

articles/cosmos-db/nosql/media/tutorial-dotnet-web-app/dialog-new-container.png

@@ -9,7 +9,7 @@ ms.reviewer: esarroyo
 ms.service: cosmos-db
 ms.subservice: nosql
 ms.topic: tutorial
-ms.date: 12/02/2022
+ms.date: 04/09/2024
 ms.devlang: csharp
 ms.custom: devx-track-dotnet, cosmos-dev-refresh, cosmos-dev-dotnet-path
 ---
@@ -50,7 +50,7 @@ First, you'll create a database and container in the existing API for NoSQL acco
 
     :::image type="content" source="media/tutorial-dotnet-web-app/resource-menu-keys.png" lightbox="media/tutorial-dotnet-web-app/resource-menu-keys.png" alt-text="Screenshot of an API for NoSQL account page. The Keys option is highlighted in the resource menu.":::
 
-1. On the **Keys** page, observe and record the value of the **URI**, **PRIMARY KEY**, and **PRIMARY CONNECTION STRING*** fields. These values will be used throughout the tutorial.
+1. On the **Keys** page, observe and record the value of the **PRIMARY CONNECTION STRING*** field. This value will be used throughout the tutorial.
 
     :::image type="content" source="media/tutorial-dotnet-web-app/page-keys.png" alt-text="Screenshot of the Keys page with the URI, Primary Key, and Primary Connection String fields highlighted.":::
 
@@ -70,12 +70,12 @@ First, you'll create a database and container in the existing API for NoSQL acco
     | **Database throughput type** | **Manual** |
     | **Database throughput amount** | `1000` |
     | **Container id** | `products` |
-    | **Partition key** | `/categoryId` |
+    | **Partition key** | `/category/name` |
 
     :::image type="content" source="media/tutorial-dotnet-web-app/dialog-new-container.png" alt-text="Screenshot of the New Container dialog in the Data Explorer with various values in each field.":::
 
     > [!IMPORTANT]
-    > In this tutorial, we will first scale the database up to 4,000 RU/s in shared throughput to maximize performance for the data migration. Once the data migration is complete, we will scale down to 400 RU/s of provisioned throughput.
+    > In this tutorial, we will first scale the database up to 1,000 RU/s in shared throughput to maximize performance for the data migration. Once the data migration is complete, we will scale down to 400 RU/s of provisioned throughput.
 
 1. Select **OK** to create the database and container.
 
@@ -84,36 +84,41 @@ First, you'll create a database and container in the existing API for NoSQL acco
     > [!TIP]
     > You can optionally use the Azure Cloud Shell here.
 
-1. Install a **pre-release**version of the `cosmicworks` dotnet tool from NuGet.
+1. Install **v2** of the `cosmicworks` dotnet tool from NuGet.
 
     ```bash
-    dotnet tool install --global cosmicworks  --prerelease
+    dotnet tool install --global cosmicworks  --version 2.*
     ```
 
 1. Use the `cosmicworks` tool to populate your API for NoSQL account with sample product data using the **URI** and **PRIMARY KEY** values you recorded earlier in this lab. Those recorded values will be used for the `endpoint` and `key` parameters respectively.
 
     ```bash
     cosmicworks \
-        --datasets product \
-        --endpoint <uri> \
-        --key <primary-key>
+        --number-of-products 1759 \
+        --number-of-employees 0 \
+        --disable-hierarchical-partition-keys \
+        --connection-string <nosql-connection-string>
     ```
 
-1. Observe the output from the command line tool. It should add more than 200 items to the container. The example output included is truncated for brevity.
+1. Observe the output from the command line tool. It should add 1759 items to the container. The example output included is truncated for brevity.
 
     ```output
+    ── Parsing connection string ────────────────────────────────────────────────────────────────
+    ╭─Connection string──────────────────────────────────────────────────────────────────────────╮
+    │ AccountEndpoint=https://<account-name>.documents.azure.com:443/;AccountKey=<account-key>;  │
+    ╰────────────────────────────────────────────────────────────────────────────────────────────╯
+    ── Populating data ──────────────────────────────────────────────────────────────────────────
+    ╭─Products configuration─────────────────────────────────────────────────────────────────────╮
+    │ Database   cosmicworks                                                                     │
+    │ Container  products                                                                        │
+    │ Count      1,759                                                                           │
+    ╰────────────────────────────────────────────────────────────────────────────────────────────╯
     ...
-    Revision:       v4
-    Datasets:
-            product
-    
-    Database:       [cosmicworks]   Status: Created
-    Container:      [products]      Status: Ready
-    
-    product Items Count:    295
-    Entity: [9363838B-2D13-48E8-986D-C9625BE5AB26]  Container:products      Status: RanToCompletion
-    ...
-    Container:      [product]       Status: Populated
+    [SEED]  00000000-0000-0000-0000-000000005951 | Road-650 Black, 60 - Bikes
+    [SEED]  00000000-0000-0000-0000-000000005950 | Mountain-100 Silver, 42 - Bikes
+    [SEED]  00000000-0000-0000-0000-000000005949 | Men's Bib-Shorts, L - Clothing
+    [SEED]  00000000-0000-0000-0000-000000005948 | ML Mountain Front Wheel - Components
+    [SEED]  00000000-0000-0000-0000-000000005947 | Mountain-500 Silver, 42 - Bikes
     ```
 
 1. Return to the **Data Explorer** page for your account.
@@ -173,29 +178,33 @@ First, you'll create a database and container in the existing API for NoSQL acco
 
     ```sql
     SELECT
-      p.name,
-      p.categoryName,
-      p.tags
+        p.name,
+        p.category.name AS category,
+        p.category.subCategory.name AS subcategory,
+        p.tags
     FROM products p
-    JOIN t IN p.tags
-    WHERE t.name = "Tag-32"
+    JOIN tag IN p.tags
+    WHERE STRINGEQUALS(tag, "yellow", true)
     ```
 
 1. The results should be a smaller array of items filtered to only contain items that include at least one tag with a **name** value of `Tag-32`. Again, a subset of the output is included here for brevity.
 
     ```output
-    ...
-    {
-    "name": "ML Mountain Frame - Black, 44",
-    "categoryName": "Components, Mountain Frames",
-    "tags": [
-        {
-        "id": "18AC309F-F81C-4234-A752-5DDD2BEAEE83",
-        "name": "Tag-32"
-        }
+    [
+      ...
+      {
+        "name": "HL Touring Frame - Yellow, 60",
+        "category": "Components",
+        "subcategory": "Touring Frames",
+        "tags": [
+          "Components",
+          "Touring Frames",
+          "Yellow",
+          "60"
+        ]
+      },
+      ...
     ]
-    },
-    ...
     ```
 
 ## Create ASP.NET web application