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
+20-12Lines changed: 20 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,13 +54,13 @@ For this example, add the Common Data Service trigger that fires when a new reco
54
54
55
55
1. In the search box, enter `common data service`. For this example, under the triggers list, select this trigger: **When a record is created**
56
56
57
-

57
+

58
58
59
59
1. If prompted, sign in to the Common Data Service.
60
60
61
61
1. In the trigger, provide information about the environment where you want to monitor for new "Leads" records, for example:
62
62
63
-

63
+

64
64
65
65
| Property | Required | Description |
66
66
|----------|----------|-------------|
@@ -77,11 +77,11 @@ Now add a Common Data Service action that creates a task record for a new "Leads
77
77
78
78
1. In the search box, enter `common data service`. From the actions list, select this action: **Create a new record**
79
79
80
-

80
+

81
81
82
82
1. In the action, provide the information about the environment where you want to create the new task record. If available, other properties also appear based on the entity that you selected for this action, for example:
83
83
84
-

84
+

85
85
86
86
| Property | Required | Description |
87
87
|----------|----------|-------------|
@@ -98,7 +98,7 @@ Now add a Common Data Service action that creates a task record for a new "Leads
98
98
99
99
1. In the list, from the **When a record is created** section, select the trigger outputs that you want to include in the task record, for example:
100
100
101
-

101
+

102
102
103
103
| Trigger output | Description |
104
104
|----------------|-------------|
@@ -109,19 +109,27 @@ Now add a Common Data Service action that creates a task record for a new "Leads
109
109
110
110
When you're done, the action might look like this example:
111
111
112
-

112
+

113
113
114
114
1. Save your logic app. On the designer toolbar, select **Save**.
115
115
116
116
1. To manually start the logic app, on the designer toolbar, select **Run**. To test your logic app, create a new "Leads" record.
117
117
118
-
## Add filter or query
118
+
## Trigger only on updated attributes
119
119
120
-
To specify how to filter data in a Dynamics 365 action, choose **Show advanced options** in that action.
121
-
You can then add a filter or order by query.
122
-
For example, you can use a filter query to get only the
123
-
active accounts and order those records by account name.
124
-
For this task, follow these steps:
120
+
For triggers that run when a record is updated, you can use filter attributes so that your logic app runs only when the specified attributes are updated. This capability helps you prevent unnecessary logic app runs.
121
+
122
+
1. In the trigger, from the **Add new parameter** list, select **Attribute Filters**.
For actions that list records, you can add a query that returns records based on a filter or in a specific order. For example, you can use a filter query to get only the active accounts and order those records by account name. For this task, follow these steps:
125
133
126
134
1. Under **Filter query**, enter this OData filter query: `statuscode eq 1`
0 commit comments