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/connect-common-data-service.md
+14-55Lines changed: 14 additions & 55 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,73 +155,32 @@ For actions that return records, such as the **List records** action, you can us
155
155
156
156
For more information about `$orderby` system query options, see [Common Data Service - Order results](https://docs.microsoft.com/powerapps/developer/common-data-service/webapi/query-data-web-api#order-results).
157
157
158
-
### Best practices for advanced options
158
+
##Field data types
159
159
160
-
When you specify a value for a field in an action or trigger,
161
-
the value's data type must match the field type whether you
162
-
manually enter the value or select the value from the dynamic content list.
160
+
Regardless whether you manually enter a value or select a value from the dynamic content list for a field in a trigger or action, the value's data type must match the field's required data type.
163
161
164
-
This table describes some of field types and
165
-
the required data types for their values.
162
+
This table describes some field types and the data types that those fields require for their values.
166
163
167
-
| Field type | Required data type | Description |
168
-
|------------|--------------------|-------------|
169
-
| Text fields| Single line of text |These fields require a single line of text or dynamic content that has the text type. <p><p>*Example fields*: **Description**and**Category**|
170
-
| Integer fields| Whole number |Some fields require integer or dynamic content that has the integer type. <p><p>*Example fields*: **Percent Complete**and**Duration**|
171
-
| Date fields| Date and Time |Some fields require a date with mm/dd/yyyy format or dynamic content that has the date type. <p><p>*Example fields*: **Created On**, **Start Date**, **Actual Start**, **Actual End**, and**Due Date**|
172
-
|Fields requiring both a record IDand lookup type| Primary key | Some fields that reference another entity record require both a record ID and a lookup type. |
164
+
| Field | Data type | Description |
165
+
|-------|-----------|-------------|
166
+
| Text field| Single line of text |Requires either a single line of text or dynamic content that has the text data type, for example: <p><p>- **Description**<br>-**Category**|
167
+
| Integer field| Whole number |Requires either an integer or dynamic content that has the integer data type, for example: <p><p>- **Percent Complete**<br>-**Duration**|
168
+
| Date field| Date and Time |Requires either a date in MM/DD/YYY format or dynamic content that has the date data type, for example: <p><p>- **Created On** <br>- **Start Date** <br>- **Actual Start** <br>- **Actual End** <br>-**Due Date**|
169
+
|Field that references another entity record | Primary key | Requires both a record ID, such as a GUID, and a lookup type, which means that values from the dynamic content list won't work, for example: <p><p>- **Owner**: Must be a valid user ID or a team record ID. <br>- **Owner Type**: Must be a lookup type such as `systemusers` or `teams`, respectively. <p><p>- **Regarding**: Must be a valid record ID such as an account ID or a contact record ID. <br>- **Regarding Type**: Must be a lookup type such as `accounts` or `contacts`, respectively. <p><p>- **Customer**: Must be a valid record ID such as an account ID or contact record ID. <br>- **Customer Type**: Must be the lookup type, such as `accounts` or `contacts`, respectively. |
173
170
||||
174
171
175
-
Expanding on these field types, here are example fields in
176
-
Dynamics 365 triggers and actions that require both a
177
-
record ID and the lookup type. This requirement means
178
-
values that you select from the dynamic list won't work.
172
+
For example, this **Create a new record** action creates a new "Tasks" record and shows how some of these field types require values that match the required data types.
179
173
180
-
| Field | Description |
181
-
|-------|-------------|
182
-
|**Owner**| Must be either a valid user ID or team record ID. |
183
-
|**Owner Type**| Must be either `systemusers` or `teams`. |
184
-
|**Regarding**| Must be a valid record ID, such as an account ID or contact record ID. |
185
-
|**Regarding Type**| Must be a lookup type, such as `accounts` or `contacts`. |
186
-
|**Customer**| Must be a valid record ID, such as an account ID or contact record ID. |
187
-
|**Customer Type**| Must be the lookup type, such as `accounts` or `contacts`. |
188
-
|||
174
+
* The action assigns the new task record to a specific user ID, based on the record ID in the **Owner** field and the lookup type in the **Owner Type** field.
189
175
190
-
In this example, the action named **Create a new record** creates a new task record:
176
+
* The action adds an account record that's associated with the record ID in the **Regarding** field and the lookup type in the **Regarding Type** field.
191
177
192
-

193
-
194
-
This action assigns the task record to a specific user ID or team record ID,
195
-
based on the record ID in the **Owner** field and the lookup type in the **Owner Type** field:
196
-
197
-

198
-
199
-
This action also adds an account record that's associated with the record ID
200
-
added in the **Regarding** field and the lookup type in the **Regarding Type** field:
201
-
202
-

203
-
204
-
## Find record ID
205
-
206
-
To find a record ID, follow these steps:
207
-
208
-
1. In Dynamics 365, open a record, such as an account record.
209
-
210
-
2. On the actions toolbar, choose one of these steps:
* Choose **EMAIL A LINK** so you can copy the full URL into your default email program.
214
-
215
-
The record ID appears in the URL between the `%7b` and `%7d` encoding characters:
216
-
217
-

178
+

218
179
219
180
## Connector reference
220
181
221
182
For technical information based on the connector's Swagger description, such as triggers, actions, limits, and other details, see the the [connector's reference page](https://docs.microsoft.com/connectors/commondataservice/).
222
183
223
184
## Next steps
224
185
225
-
* Learn about other [connectors for Azure Logic Apps](../connectors/apis-list.md)
226
-
227
-
* Learn about other [Logic Apps connectors](../connectors/apis-list.md)
186
+
* Learn about other [connectors for Azure Logic Apps](../connectors/apis-list.md)
0 commit comments