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/developer/common-data-service/define-alternate-keys-entity.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ You should be aware of the following constraints when creating alternate keys:
54
54
55
55
-**Unicode characters in key value**
56
56
57
-
If the data within a field that is used in an alternate key will contain one of the following characters `<`,`>`,`*`,`%`,`&`,`:`,`\\` then patch or upsert actions will not work. If you only need uniqueness then this approach will work, but if you need to use these keys as part of data integration then it is best to create the key on fields that won't have data with those characters.
57
+
If the data within a field that is used in an alternate key will contain one of the following characters `<`,`>`,`*`,`%`,`&`,`:`,`\\` then get or patch actions will not work. If you only need uniqueness then this approach will work, but if you need to use these keys as part of data integration then it is best to create the key on fields that won't have data with those characters.
Copy file name to clipboardExpand all lines: powerapps-docs/developer/common-data-service/org-service/handle-exceptions-code.md
+18-21Lines changed: 18 additions & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Handle exceptions in your code (Common Data Service) | Microsoft Docs"
3
3
description: "This article discusses the exceptions that are returned from a Dynamics 365 Customer Engagement web service method call. The sample in this article highlights the common faults and exceptions that your application design should handle."
4
4
ms.custom: ""
5
-
ms.date: 10/31/2018
5
+
ms.date: 06/17/2019
6
6
ms.reviewer: ""
7
7
ms.service: powerapps
8
8
ms.topic: "article"
@@ -23,7 +23,7 @@ There are a number of exceptions that can be returned from a Common Data Service
23
23
24
24
## Common exceptions and faults
25
25
26
-
The following code is used in most Common Data Service Web Services samples. It highlights the common faults and exceptions that your application design should handle.
26
+
The following code is used in most Common Data Service Web Services samples. It highlights the common faults and exceptions that your application design should handle.
> If you’re accessing the Discovery web service, your code should catch <xref:Microsoft.Xrm.Sdk.DiscoveryServiceFault> instead of the <xref:Microsoft.Xrm.Sdk.OrganizationServiceFault> fault shown previously.
73
73
74
-
In addition to these exceptions and faults, your code must handle the following exceptions:
74
+
In addition to these exceptions and faults, your code must handle the following exceptions:
When connecting to Common Data Service, a `SecurityAccessDeniedException` exception can be thrown if you use a valid Microsoft account and your account is not associated with any Common Data Service organization. A `MessageSecurityException` can be thrown if your Microsoft account isn’t valid or there was an authentication failure.
82
+
When connecting to Common Data Service, a `SecurityAccessDeniedException` exception can be thrown if you use a valid Microsoft account and your account is not associated with any Common Data Service organization. A `MessageSecurityException` can be thrown if your Microsoft account isn’t valid or there was an authentication failure.
87
83
88
84
<aname="BKMK_BusinessRuleErrors"></a>
89
85
90
86
## Custom errors from business rules
91
87
92
-
With Common Data Service, customizers can create business rules that are evaluated on the server. Customizers can throw error messages based on conditions set in the business rule. Developers should be sure to include robust error handling in their code to catch and handle these exceptions.
88
+
With Common Data Service, customizers can create business rules that are evaluated on the server. Customizers can throw error messages based on conditions set in the business rule. Developers should be sure to include robust error handling in their code to catch and handle these exceptions.
93
89
94
-
The following is an example of the trace log produced when one of these errors is returned from a business rule named **Name of Entity Scope Business Rule returning Error** and the error message is **custom error message**.
90
+
The following is an example of the trace log produced when one of these errors is returned from a business rule named **Name of Entity Scope Business Rule returning Error** and the error message is **custom error message**.
@@ -123,15 +119,16 @@ Sync workflow 'Name of Entity Scope Business Rule returning Error' terminated wi
123
119
</OrganizationServiceFault>
124
120
```
125
121
126
-
More information: [Create and edit Business Rules](https://technet.microsoft.com/library/dn531086.aspx).
122
+
More information: [Create and edit Business Rules](https://technet.microsoft.com/library/dn531086.aspx).
127
123
128
-
<aname="BKMK_AdditionalInfo"></a>
129
-
## Additional information about exceptions
130
-
When an uncaught exception is thrown that contains sensitive information that the user doesn’t have permission to see, the sensitive information in the exception is hidden from the user and a reference number is provided. This reference number refers to the related server event log entry and server trace entry. A system administrator can look up those entries and find more information about the exception.
124
+
<aname="BKMK_AdditionalInfo"></a>
125
+
126
+
## Additional information about exceptions
127
+
128
+
When an uncaught exception is thrown that contains sensitive information that the user doesn’t have permission to see, the sensitive information in the exception is hidden from the user and a reference number is provided. This reference number refers to the related server event log entry and server trace entry. A system administrator can look up those entries and find more information about the exception.
131
129
132
130
### See also
133
-
[Troubleshooting and error handling](/dynamics365/customer-engagement/developer/troubleshooting-error-handling)
0 commit comments