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: powerapps-docs/maker/data-platform/data-platform-create-business-rule.md
+31-3Lines changed: 31 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -3,10 +3,9 @@ title: Create a business rule in Microsoft Dataverse | Microsoft Docs
3
3
description: Step-by-step instructions for how to create a business rule in Microsoft Dataverse.
4
4
author: lancedMicrosoft
5
5
manager: kvivek
6
-
7
6
ms.component: cds
8
7
ms.topic: how-to
9
-
ms.date: 03/21/2018
8
+
ms.date: 04/05/2022
10
9
ms.subservice: dataverse-maker
11
10
ms.author: lanced
12
11
ms.reviewer: matp
@@ -128,7 +127,36 @@ Business rules work with most column types including text, number, choice, date,
128
127
> - To take a snapshot of everything in the **Business Rule** window, select **Snapshot** on the action bar. This is useful, for example, if you want to share and get comments on the business rule from a team member.
129
128
> - Use the mini-map to navigate quickly to different parts of the process. This is useful when you have a complicated process that scrolls off the screen.
130
129
> - As you add conditions, Actions, and business recommendations to your business rule, Dataverse builds the code for the business rule at the bottom of the designer window. This code is read only.
131
-
130
+
131
+
## Example: Create a business rule for tasks older than 30 days
132
+
133
+
This business rule example creates a condition that triggers a message in the task description field when a task is more than 30 days old.
134
+
135
+
1. Sign in to [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), on the left navigation pane expand **Data**.
136
+
1. In the list that appears, select **Tables**.
137
+
1. Open the **Task** table, and then select the **Business rules** tab.
138
+
1. Select New.
139
+
1. Select **New Condition** on the business process flow canvas, and enter or select the following properties.
140
+
-**Display name**: *Task is more than 30 days old*
141
+
-**Entity**: **Task**
142
+
-**Rule 1**
143
+
-**Source**: **Entity**
144
+
-**Field**: **Created On**
145
+
-**Operator**: **+**
146
+
-**Type**: **Value**
147
+
-**Days**: *30*
148
+
-**Condition Expression** (automatically created): **(Created On Is greater than [Created On + 30])**
149
+
1. Select **Apply**.
150
+
1. Select **Add** > **Add Show Error Message**.
151
+
1. In the **Show Error Message Properties** tab, enter the following properties:
152
+
-**Display Name**: *Task is more than 30 days old*
153
+
-**Entity**: **Task**
154
+
- Error Message:
155
+
-**Field**: **Description**
156
+
-**Message**: *This task is more than 30 days old!*
157
+
1. Select **Apply**.
158
+
1. Select **Save**.
159
+
132
160
## Localize error messages used in business rules
133
161
134
162
If you have more than one language provisioned for your organization, you will want to localize any error messages that you have set. Each time you set a message, a label is generated by the system. If you export the translations in your organization, you can add localized versions of your messages and then import those labels back into the Dataverse, so that people using languages other than your base language can view the translated messages.
0 commit comments