Merge branch 'master' into michu-pachecker-4599547-api-docs

Author: phecke

powerapps-docs/developer/common-data-service/developer-tools.md

@@ -26,7 +26,7 @@ The following tools are distributed in NuGet packages. The [Developer Guide: Dow
 
 |Tool  |Description  |
 |---------|---------|
-|Code generation tool `CrmSvcUtil.exe`|A command-line code generation tool that generates early-bound .NET Framework classes that represent the entity data model used by the organization service. <br />More information: <br />[Organization Service](work-with-data-cds.md#organization-service)<br />[Create early bound entity classes with the code generation tool ](/dynamics365/customer-engagement/developer/org-service/create-early-bound-entity-classes-code-generation-tool)|
+|Code generation tool `CrmSvcUtil.exe`|A command-line code generation tool that generates early-bound .NET Framework classes that represent the entity data model used by the organization service. <br />More information: <br />[Organization Service](work-with-data-cds.md#organization-service)<br />[Create early bound entity classes with the code generation tool](/dynamics365/customer-engagement/developer/org-service/create-early-bound-entity-classes-code-generation-tool)|
 |Configuration Migration tool `DataMigrationUtility.exe`|Used to move configuration data across environments. Configuration data is used to define custom functionality  and is typically stored in custom entities. This tool is not designed to move business data. <br /> More information: [Common Data Service Administrator Guide: Move configuration data across instances and organizations with the Configuration Migration tool](/dynamics365/customer-engagement/admin/manage-configuration-data)|
 |Package Deployer `PackageDeployer.exe`|Used to deploy packages on Common Data Service instances. A package is an installable unit that includes solutions. <br /> More information: <br />[Deploy Solution Packages](introduction-solutions.md#deploy-solution-packages)<br />[Create packages for the Common Data Service Package Deployer](/dynamics365/customer-engagement/developer/create-packages-package-deployer)|
 |Plug-in Registration Tool `PluginRegistration.exe`|A tool used to subscribe .NET assembly plug-in classes to server events. <br />More information: <br />[Create a plug-in](apply-business-logic-with-code.md#create-a-plug-in)<br />[Register a plug-in](register-plug-in.md)|

powerapps-docs/developer/common-data-service/entity-attribute-metadata.md

@@ -82,8 +82,8 @@ In the following table:
 |Collection|`CalendarRulesType`|No|Contains a collection of `CalendarRules` entity records.<br />There are no attributes that use this type. When generating a proxy, the code generation tool will create two simulated attributes that are not present in the metadata. These attributes represent a view of the calendar rules records associated in a one-to-many relationship to the entity record.|
 |Collection|`PartyListType`|No|Contains a collection of `ActivityParty` entity records.<br />More information: [ActivityParty entity](reference/entities/activityparty.md)|
 |Date and Time|`DateTimeType`<br />[DateTimeAttributeMetadata](/dotnet/api/microsoft.xrm.sdk.metadata.datetimeattributemetadata)|Yes<br />**Date and Time**|Contains a date and time value.<br />All date and time attributes support values as early as 1/1/1753 12:00 AM.|
-|Image|`ImageType`<br />[ImageAttributeMetadata]()|Yes<br />**Image**|Contains data to support retrieving image data for an entity record.<br />More information: [Entity Images](entity-metadata.md#entity-images)|
-|Managed Property|`ManagedPropertyType`<br />[ManagedPropertyAttributeMetadata](/dotnet/api/microsoft.xrm.sdk.metadata.imageattributemetadata)|No|Contains data that describe whether the solution component stored in the entity record can be customized when included in a managed solution.<br />More information: [Managed Properties](introduction-solutions.md#managed-properties)|
+|Image|`ImageType`<br />[ImageAttributeMetadata](/dotnet/api/microsoft.xrm.sdk.metadata.imageattributemetadata)|Yes<br />**Image**|Contains data to support retrieving image data for an entity record.<br />More information: [Entity Images](entity-metadata.md#entity-images)|
+|Managed Property|`ManagedPropertyType`<br />[ManagedPropertyAttributeMetadata](/dotnet/api/microsoft.xrm.sdk.metadata.managedpropertyattributemetadata)|No|Contains data that describe whether the solution component stored in the entity record can be customized when included in a managed solution.<br />More information: [Managed Properties](introduction-solutions.md#managed-properties)|
 |Quantity|`BigIntType`<br />[BigIntAttributeMetadata](/dotnet/api/microsoft.xrm.sdk.metadata.bigintattributemetadata)|No|Contains a `BigInt` value. For internal use only.|
 |Quantity|`DecimalType`<br />[DecimalAttributeMetadata](/dotnet/api/microsoft.xrm.sdk.metadata.decimalattributemetadata)|Yes<br />**Decimal Number**|Contains a `Decimal` value. The `Precision` property sets the level of precision.|
 |Quantity|`DoubleType`<br />[DoubleAttributeMetadata](/dotnet/api/microsoft.xrm.sdk.metadata.doubleattributemetadata)|Yes<br />**Floating Point Number**|Contains a `Double` value. The `Precision` property sets the level of precision.|

powerapps-docs/developer/common-data-service/event-framework.md

@@ -2,7 +2,7 @@
 title: " Event Framework (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Describes the event framework and information developers should know when working with it." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 05/25/2019
+ms.date: 06/18/2019
 ms.reviewer: ""
 ms.service: powerapps
 ms.topic: "article"
@@ -45,7 +45,27 @@ Generally, you can expect to find a message for most of the **Request* classes i
 
 Data about messages is stored in the [SdkMessage](reference/entities/sdkmessage.md) and [SdkMessageFilter](reference/entities/sdkmessagefilter.md) entities. The Plug-in registration tool will filter this information to only show valid messages.
 
-To verify if a message and entity combination supports execution of plug-ins using a database query, use Advanced Find or a community tool (e.g., [FetchXML Builder](http://fxb.xrmtoolbox.com)) to execute the following fetchXML query. When using Advanced Find, you must create the query interactively.
+To verify if a message and entity combination supports execution of plug-ins using a database query, you can use the following Web API query:
+
+```
+{{webapiurl}}sdkmessages?$select=name
+&$filter=isprivate eq false 
+and (name ne 'SetStateDynamicEntity' 
+and name ne 'RemoveRelated' 
+and name ne 'SetRelated' and 
+name ne 'Execute') 
+and sdkmessageid_sdkmessagefilter/any(s:s/iscustomprocessingstepallowed eq true 
+and s/isvisible eq true)
+&$expand=sdkmessageid_sdkmessagefilter($select=primaryobjecttypecode;
+$filter=iscustomprocessingstepallowed eq true and isvisible eq true)
+&$orderby=name
+```
+
+> [!TIP]
+> You can export this data to an Excel worksheet using this query and the instructions provided in this blog post: [Find Messages and entities eligible for plug-ins using the Common Data Service](https://powerapps.microsoft.com/en-us/blog/find-messages-and-entities-eligible-for-plug-ins-using-the-common-data-service/)
+
+
+You can also use the following FetchXML to retrieve this information. The [FetchXML Builder](http://fxb.xrmtoolbox.com) is a useful tool to execute this kind of query.
 
 ```xml
 <fetch>

powerapps-docs/developer/common-data-service/org-service/generate-early-bound-classes.md

@@ -37,7 +37,7 @@ The classes created by the code generation tool are designed to be built into a
 The following lists assemblies that must be referenced in your project when you use the generated code file.  
 
 - `Microsoft.Crm.Sdk.Proxy.dll`  
-- `Microsoft.Xrm.Sdk.dll ` 
+- `Microsoft.Xrm.Sdk.dll` 
 
 These assemblies are part of the [Microsoft.CrmSdk.CoreAssemblies](https://www.nuget.org/packages/Microsoft.CrmSdk.CoreAssemblies/) NuGet package. Use this Nuget packages to add these assemblies to your Visual Studio project.
 

powerapps-docs/developer/common-data-service/org-service/handle-exceptions-code.md

@@ -73,11 +73,11 @@ catch (System.Exception ex)
   
 In addition to these exceptions and faults, your code must handle the following exceptions:  
 
-- [SecurityTokenValidationException](https://msdn.microsoft.com/library/system.identitymodel.tokens.securitytokenvalidationexception.aspx)  
-- [ExpiredSecurityTokenException](https://msdn.microsoft.com/library/system.servicemodel.security.expiredsecuritytokenexception.aspx)  
-- [SecurityAccessDeniedException](https://msdn.microsoft.com/library/system.servicemodel.security.securityaccessdeniedexception.aspx)  
-- [MessageSecurityException](https://msdn.microsoft.com/library/system.servicemodel.security.messagesecurityexception.aspx)  
-- [SecurityNegotiationException](https://msdn.microsoft.com/library/system.servicemodel.security.securitynegotiationexception.aspx)  
+- [SecurityTokenValidationException](/dotnet/api/system.identitymodel.tokens.securitytokenvalidationexception)  
+- [ExpiredSecurityTokenException](/dotnet/api/system.servicemodel.security.expiredsecuritytokenexception)  
+- [SecurityAccessDeniedException](/dotnet/api/system.servicemodel.security.securityaccessdeniedexception)  
+- [MessageSecurityException](/dotnet/api/system.servicemodel.security.messagesecurityexception)  
+- [SecurityNegotiationException](/dotnet/api/system.servicemodel.security.securitynegotiationexception)  
 
 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.  
 
@@ -119,7 +119,7 @@ Sync workflow 'Name of Entity Scope Business Rule returning Error' terminated wi
 </OrganizationServiceFault>  
 ```  
 
-More information: [Create and edit Business Rules](https://technet.microsoft.com/library/dn531086.aspx).  
+More information: [Create a business rule for an entity](../../../maker/common-data-service/data-platform-create-business-rule.md)  
 
 <a name="BKMK_AdditionalInfo"></a>
 

powerapps-docs/developer/common-data-service/security-model.md

@@ -2,7 +2,7 @@
 title: "Security Model (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "PowerApps provides a security model that protects data integrity and privacy, and supports efficient data access and collaboration" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 06/18/2019
 ms.reviewer: ""
 ms.service: powerapps
 ms.topic: "article"
@@ -33,8 +33,5 @@ Combine role-based security, record-level security, and field-level security to
 As a developer, you should know that your queries run in the context of a user, and will only return records that the user is entitled to read.
 Further, you will only be able to perform operations based on the privileges assigned to your user account through the security roles.
 
-For detailed information about the security concepts, see [Security concepts](/dynamics365/customer-engagement/admin/security-concepts)
+For detailed information, see [Security in Common Data Service](/power-platform/admin/wp-security)
 
-### See also
-
-[BusinessUnit entity](businessunit-entity.md)

powerapps-docs/developer/common-data-service/troubleshoot-plug-in.md

@@ -73,7 +73,7 @@ TODO: Add content that shows how to do this -->
 
 ## Error: Message size exceeded when sending context to Sandbox
 
-<!-- This is the error code for an unexpected error we should be providing a specific error code -->
+<!-- This is the error code for an unexpected error we should be providing a specific error code. Bug 1470173 is tracking this. -->
 Error Code: `-2147220970`<br />
 Error Message: `Message size exceeded when sending context to Sandbox. Message size: ### Mb`
 
@@ -87,3 +87,57 @@ If you encounter this error you can:
 
 1.	Remove the plug-in for the message. If there are no plug-ins registered for the message, the operation will complete without an error.
 2.	If the error is occurring in a custom client, you can modify your code so that it doesn't attempt to perform the work in a single operation. Instead, write code to retrieve the data in smaller parts.
+
+## Error: The given key was not present in the dictionary
+
+Common Data Service frequently uses classes derived from the abstract <xref:Microsoft.Xrm.Sdk.DataCollection`2> class that represents a collection of keys and values. For example, with plug-ins the  <xref:Microsoft.Xrm.Sdk.IExecutionContext>.<xref:Microsoft.Xrm.Sdk.IExecutionContext.InputParameters> property is a <xref:Microsoft.Xrm.Sdk.ParameterCollection> derived from the <xref:Microsoft.Xrm.Sdk.DataCollection`2> class. These classes are essentially dictionary objects where you access a specific value using the key name.
+
+### Error codes
+
+This error occurs when the key value in code doesn't exist in the collection. This is a run-time error rather a platform error. When this error occurs within a plug-in, the error code will depend on whether the error was caught.
+
+If the developer caught the exception and returned an <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionException> as described in [Handle exceptions in plug-ins](handle-exceptions.md), the following error will be returned:
+
+Error Code: `-2147220891`<br />
+Error Message: `ISV code aborted the operation.`
+
+However, with this error it is common that the developer doesn't catch it properly and the following error will be returned:
+
+Error Code: `-2147220956`<br />
+Error Message: `An unexpected error occurred from ISV code.`
+
+> [!NOTE]
+> "ISV" stands for *Independent Software Vendor*.
+
+### Causes
+
+This error frequently occurs at design time and can be due to a misspelling or using the incorrect casing. The key values are case sensitive.
+
+At run-time the error is frequently due to the developer assuming that the value will be present when it isn't. For example, in a plug-in that is registered for the update of an entity, only those values which are changed will be included in the <xref:Microsoft.Xrm.Sdk.Entity>.<xref:Microsoft.Xrm.Sdk.Entity.Attributes> collection.
+
+### Prevention
+
+To prevent this error you must check that the key exists before attempting to use it to access a value. 
+
+For example, when accessing an entity attribute, you can use the <xref:Microsoft.Xrm.Sdk.Entity>.<xref:Microsoft.Xrm.Sdk.Entity.Contains(System.String)> method to check whether an attribute exists in an entity as shown in the following code.
+
+```csharp
+// Obtain the execution context from the service provider.  
+IPluginExecutionContext context = (IPluginExecutionContext)
+    serviceProvider.GetService(typeof(IPluginExecutionContext));
+
+// The InputParameters collection contains all the data passed in the message request.  
+if (context.InputParameters.Contains("Target") &&
+    context.InputParameters["Target"] is Entity)
+    {
+    // Obtain the target entity from the input parameters.  
+    Entity entity = (Entity)context.InputParameters["Target"];
+
+    //Check whether the name attribute exists.
+    if(entity.Contains("name"))
+    {
+        string name = entity["name"];
+    }
+```
+
+Some developers use the <xref:Microsoft.Xrm.Sdk.Entity>.<xref:Microsoft.Xrm.Sdk.Entity.GetAttributeValue``1(System.String)> method to avoid this error when accessing entity attributes, but be aware that this method will return the default value of the type if the attribute doesn't exist. If the default value is null, this works as expected. But if the default value doesn't return null, such as with a `DateTime`, the value returned will be `1/1/0001 00:00` rather than null.

powerapps-docs/developer/common-data-service/tutorial-write-plug-in.md

@@ -209,7 +209,7 @@ In Visual Studio, press **F6** to build the assembly. Verify that it compiles wi
 1. Click **OK** to close the **Create Strong Name Key** dialog.
 1. In the project properties **Build** tab, verify that the **Configuration** is set to **Debug**.
 1. Press **F6** to build the plug-in again.
-1. Using windows explorer, find the built plug-in at:` \bin\Debug\BasicPlugin.dll`.
+1. Using windows explorer, find the built plug-in at: `\bin\Debug\BasicPlugin.dll`.
 
 > [!NOTE]
 > Build the assembly using **Debug** configuration because you will use the Plug-in profiler to debug it in a later tutorial.   Before you include a plug-in with your solution, you should build it using the release configuration.

powerapps-docs/developer/common-data-service/understand-the-data-context.md

@@ -2,7 +2,7 @@
 title: "Understand the execution context (Common Data Service) | Microsoft Docs" 
 description: "Learn about the data that is passed to your plug-ins when it is executed." 
 ms.custom: ""
-ms.date: 05/25/2019
+ms.date: 06/20/2019
 ms.reviewer: pehecke
 ms.service: powerapps
 ms.topic: "article"
@@ -168,11 +168,12 @@ When you define an entity image, you specify an entity alias value you can use t
 var oldAccountName = (string)context.PreEntityImages["a"]["name"];
 ```
 
-More information: [Define entity images](register-plug-in.md#define-entity-images)
+More information:
+
+- [Define entity images](register-plug-in.md#define-entity-images)
+- [Entity Images for workflow extensions](workflow/workflow-extensions.md#entity-images-for-workflow-extensions)
 
-### Entity Images for custom workflow activites
 
-There is no way to configure entity images for custom workflow activities since you only register the assembly and the workflow activity runs in the context of the workflow. For custom workflow activities entity images are available using the key values `PreBusinessEntity` and `PostBusinessEntity` respectively for the pre and post entity images.
 
 ### See also
 

powerapps-docs/developer/common-data-service/use-change-tracking-synchronize-data-external-systems.md

@@ -22,7 +22,7 @@ The change tracking feature in Common Data Service provides a way to keep the da
 <a name="BKMK_enable"></a>   
 ## Enable change tracking for an entity  
 
- Before retrieving the changes for an entity, make sure that the change tracking feature is enabled for that entity. This feature can be enabled by using the customization user interface (UI) or programmatically by setting the <xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.ChangeTrackingEnabled> property to `True`. Annotation `Org.OData.Capabilities.V1.ChangeTracking ` gets added to entity sets that have change tracking enabled. To see annotations in entity metadata, do 
+ Before retrieving the changes for an entity, make sure that the change tracking feature is enabled for that entity. This feature can be enabled by using the customization user interface (UI) or programmatically by setting the <xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.ChangeTrackingEnabled> property to `True`. Annotation `Org.OData.Capabilities.V1.ChangeTracking` gets added to entity sets that have change tracking enabled. To see annotations in entity metadata, do 
 
  ```http 
  GET [Organization URI]/api/data/v9.0/$metadata?annotations=true