You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/connectors/connectors-create-api-cosmos-db.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,10 @@ To add an Azure Cosmos DB built-in trigger to a Standard workflow, follow these
72
72
> The trigger creates a workflow run for each item created or modified in Azure Cosmos DB,
73
73
> so the dynamic content output of this trigger is always a single item.
74
74
75
+
The following example shows the **When an item is created or modified** trigger:
76
+
77
+
:::image type="content" source="media/connectors-create-api-cosmos-db/trigger-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard workflow, and trigger named When an item is created or modified.":::
78
+
75
79
1. To add any other available parameters, open the **Advanced parameters** list.
76
80
77
81
1. Configure any other parameters or settings as needed.
@@ -148,7 +152,11 @@ To add an Azure Cosmos DB built-in action to a Standard workflow, follow these s
148
152
|-----------|----------|-------|-------------|
149
153
|**Database Id**| Yes | <*database-ID*> | The database to connect. |
150
154
|**Container Id**| Yes | <*container-ID*> | The container to query. |
151
-
|**Item**| Yes | <*JSON-document*> | The JSON document to create. This example uses the request body from the trigger output. <br><br>**Tip**: If the HTTP trigger's **Body** token doesn't appear in the dynamic content list for you to add, next to the trigger name, select **See more**. <br><br>**Note**: Make sure that the body is well-formed JSON, and at a minimum, contains the **`id`** property and the partition key property for your document. If a document with the specified **`id`** and partition key exists, the document is updated. Otherwise, a new document is created. |
155
+
|**Item**| Yes | <*JSON-document*> | The JSON document to create. This example uses the **id** output from the Request trigger. <br><br>**Note**: If you use the **body** trigger output, make sure that the body content is well-formed JSON, and at a minimum, contains the **`id`** attribute and the **`partitionKey`** attribute for your document. If a document with these attributes exist, the document is updated. Otherwise, a new document is created. |
156
+
157
+
The following example shows the action named **Create or update item**, which includes the **Item** and **Partition Key** parameter values from the output for the trigger named **When a HTTP request is received**:
158
+
159
+
:::image type="content" source="media/connectors-create-api-cosmos-db/create-action-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard workflow, and action named Create or update item.":::
152
160
153
161
1. Configure any other parameters or settings as needed.
0 commit comments