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/data-platform/org-service/samples/work-with-option-sets.md
+11-12Lines changed: 11 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -20,27 +20,26 @@ contributors:
20
20
# Work with choices
21
21
22
22
23
-
24
23
This sample shows how to work with choices. Typically, you use choices to set columns so that different columns can share the same set of options, which are maintained in one ___location. Unlike local options sets which are defined only for a specific column, you can reuse choices. You will also see them used in request parameters in a manner similar to an enumeration.
25
24
26
25
When you define a choices column by using [CreateOptionSetRequest](/dotnet/api/microsoft.xrm.sdk.messages.createoptionsetrequest?view=dynamics-general-ce-9), we recommend that you let the system assign a value. You do this by passing a null value when you create the new `OptionMetadata` instance. When you define an option, it will contain an option value prefix specific to the context of the publisher set for the solution that the choices column is created in. This prefix helps reduce the chance of creating duplicate choices for a managed solution, and in any choices column that are defined in organizations where your managed solution is installed. For more information, see [Merge choices values](/power-platform/alm/how-managed-solutions-merged#merge-option-set-options).
27
26
28
27
Use the following message request classes to work with choices:
Copy file name to clipboardExpand all lines: powerapps-docs/developer/data-platform/webapi/web-api-samples-csharp.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ The following is required to build and run the Dataverse Web API C# samples :
38
38
- In order to run samples against Dataverse, you must register your application with Azure Active Directory to obtain a client ID and redirect URL. For more information, see [Walkthrough: Register a Dataverse app with Azure Active Directory](../walkthrough-register-app-azure-active-directory.md).
39
39
40
40
> [!NOTE]
41
-
> These samples require version 2.x of assembly [Microsoft.IdentityModel.Client.ActiveDirectory](/dotnet/api/microsoft.identitymodel.clients.activedirectory?view=azure-dotnet) for OAuth based authentication.
41
+
> These samples require version 2.x of assembly [Microsoft.IdentityModel.Client.ActiveDirectory](/dotnet/api/microsoft.identitymodel.clients.activedirectory) for OAuth based authentication.
Copy file name to clipboardExpand all lines: powerapps-docs/developer/data-platform/webapi/web-api-types-operations.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -258,7 +258,7 @@ OData supports a wide range of data types but Dataverse doesn’t use all of the
258
258
259
259
### Lookup properties
260
260
261
-
For most single-valued navigation properties you will find a computed, read-only property that uses the following naming convention: `_<name>_value` where the `<name>` matches the name of the single-valued navigation property. The exception to this pattern is when a lookup attribute of the entity can accept multiple types of entity references. A common example is how the `incident` entity `customerid` attribute may be set to a reference that is either a `contact` or `account` entity. In the <xref:Microsoft.Dynamics.CRM.incident?text=incident EntityType/> [Single-valued navigation properties](/dynamics365/customer-engagement/web-api/incident?view=dynamics-ce-odata-9#Single-valued_navigation_properties) you will find `customerid_account` and `customerid_contact` as separate single-valued navigation properties to reflect the customer associated with an opportunity. If you set one of these single-valued navigation properties, the other will be set to null because they are both bound to the `customerid` attribute. In the <xref:Microsoft.Dynamics.CRM.incident?text=incident EntityType/> [Properties](/dynamics365/customer-engagement/web-api/incident?view=dynamics-ce-odata-9#Properties) you’ll find a `_customerid_value` lookup property that contains the same value that is set for whichever of the single-valued navigation properties contain a value.
261
+
For most single-valued navigation properties you will find a computed, read-only property that uses the following naming convention: `_<name>_value` where the `<name>` matches the name of the single-valued navigation property. The exception to this pattern is when a lookup attribute of the entity can accept multiple types of entity references. A common example is how the `incident` entity `customerid` attribute may be set to a reference that is either a `contact` or `account` entity. In the <xref:Microsoft.Dynamics.CRM.incident?text=incident EntityType/> [Single-valued navigation properties](/dynamics365/customer-engagement/web-api/incident#Single-valued_navigation_properties) you will find `customerid_account` and `customerid_contact` as separate single-valued navigation properties to reflect the customer associated with an opportunity. If you set one of these single-valued navigation properties, the other will be set to null because they are both bound to the `customerid` attribute. In the <xref:Microsoft.Dynamics.CRM.incident?text=incident EntityType/> [Properties](/dynamics365/customer-engagement/web-api/incident#Properties) you’ll find a `_customerid_value` lookup property that contains the same value that is set for whichever of the single-valued navigation properties contain a value.
262
262
263
263
Generally, you should avoid using lookup properties and use the corresponding single-valued navigation properties instead. These properties have been included because they may be useful for certain integration scenarios. These properties are read-only and computed because they will simply reflect the changes applied using the corresponding single-valued navigation property.
0 commit comments