Merge branch 'live' into live

Author: jlattimer

.openpublishing.publish.config.json

@@ -104,11 +104,7 @@
     "master": [
       "Publish",
       "PDF"
-    ],
-    "mints-Aug": [
-      "Publish",
-      "PDF"
-      ]
+    ]
   },
   "need_generate_pdf_url_template": true,
   "Targets": {

powerapps-docs/developer/common-data-service/TOC.yml

@@ -89,6 +89,8 @@
       href: logging-tracing.md
     - name: Analyze performance
       href: analyze-performance.md
+    - name: Troubleshoot plug-ins
+      href: troubleshoot-plug-in.md
     - name: Access external web resources
       href: access-web-services.md
     - name: Tutorials

powerapps-docs/developer/common-data-service/api-limits.md

@@ -21,6 +21,8 @@ We limit the number of API requests made by each user, per organization instance
 
 The limit will help ensure that users running applications cannot interfere with each other based on resource constraints. The limits will not affect normal users of the platform. Only applications that perform a large number of API requests may be affected. The limit will help provide a level of protection from random and unexpected surges in request volumes that threaten the availability and performance characteristics of the Common Data Service platform.
 
+Since plug-ins and custom workflow activities execute on the server independent of a logged on user, API calls made from plug-in code will not count against this external API request limit.
+
 If your application has the potential to exceed the limit, please consider the guidance given in the [What should I do if my application exceeds the limit?](#what-should-i-do-if-my-application-exceeds-the-limit) section below.
 
 ## What happens when the limit is exceeded?

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

@@ -80,7 +80,7 @@ In the following table:
 |Categorization|`StateType`<br />[StateAttributeMetadata](/dotnet/api/microsoft.xrm.sdk.metadata.stateattributemetadata)|No|Contains the option value that describes the status of an entity record.<br />More information: [Option Sets](#option-sets)|
 |Categorization|`StatusType`<br />[StatusAttributeMetadata](/dotnet/api/microsoft.xrm.sdk.metadata.statusattributemetadata)|No|Contains the option value that describes the reason for the status of an entity record.<br />More information: [Option Sets](#option-sets)|
 |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](#activityparty-entity)|
+|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)|

powerapps-docs/developer/common-data-service/media/Azure-add-api-access.png

@@ -104,6 +104,8 @@
     href: metadata-retrieve-detect-changes.md
   - name: Retrieve, update, and delete entities
     href: metadata-retrieve-update-delete-entities.md 
+  - name: Create an entity to send email activities
+    href: create-update-entity-emailed.md
 - name: Import data
   href: ../import-data.md #Topic is for both Web API and Organization service
 - name: Sample data

powerapps-docs/developer/common-data-service/media/azure-add-permission.PNG

@@ -0,0 +1,113 @@
+---
+title: "Create and update an entity to send email activities to records (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+description: "Learn about creating an entity that contains an email address you can use to send email activities to records for that entity." # 115-145 characters including spaces. This abstract displays in the search result.
+ms.custom: ""
+ms.date: 04/05/2019
+ms.reviewer: ""
+ms.service: powerapps
+ms.topic: "article"
+author: "brandonsimons" # GitHub ID
+ms.author: "jdaly" # MSFT alias of Microsoft employees only
+manager: "ryjones" # MSFT alias of manager or PM counterpart
+search.audienceType: 
+  - developer
+search.app: 
+  - PowerApps
+  - D365CE
+---
+# Create and update an entity to send email activities to records
+
+You can create an entity that contains an email address you can use to send email activities to records for that entity.  
+  
+ The following sample code creates a custom entity and sets the <xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.IsActivityParty> property to `true`. It also creates a <xref:Microsoft.Xrm.Sdk.Metadata.StringAttributeMetadata> attribute using <xref:Microsoft.Xrm.Sdk.Metadata.StringFormatName>.`Email` to provide an email address to use.  
+  
+ Even if you add other <xref:Microsoft.Xrm.Sdk.Metadata.StringAttributeMetadata> attributes formatted as an email address, only the first one specified is used.  
+
+```csharp
+// Create the custom entity.
+CreateEntityRequest createrequest = new CreateEntityRequest
+{
+    // Define an entity to enable for emailing. In order to do so,
+    // IsActivityParty must be set.
+    Entity = new EntityMetadata
+    {
+        SchemaName = _customEntityName,
+        DisplayName = new Label("Agent", 1033),
+        DisplayCollectionName = new Label("Agents", 1033),
+        Description = new Label("Insurance Agents", 1033),
+        OwnershipType = OwnershipTypes.UserOwned,
+        IsActivity = false,
+
+        // Unless this flag is set, this entity cannot be party to an
+        // activity.
+        IsActivityParty = true
+    },
+
+    // As with built-in emailable entities, the Primary Attribute will
+    // be used in the activity party screens. Be sure to choose descriptive
+    // attributes.
+    PrimaryAttribute = new StringAttributeMetadata
+    {
+        SchemaName = "new_fullname",
+        RequiredLevel = new AttributeRequiredLevelManagedProperty(AttributeRequiredLevel.None),
+        MaxLength = 100,
+        FormatName = StringFormatName.Text,
+        DisplayName = new Label("Agent Name", 1033),
+        Description = new Label("Agent Name", 1033)
+    }
+};
+
+_serviceProxy.Execute(createrequest);
+Console.WriteLine("The emailable entity has been created.");
+
+// The entity will not be selectable as an activity party until its customizations
+// have been published. Otherwise, the e-mail activity dialog cannot find
+// a correct default view.
+PublishAllXmlRequest publishRequest = new PublishAllXmlRequest();
+_serviceProxy.Execute(publishRequest);
+
+// Before any emails can be created for this entity, an Email attribute
+// must be defined.
+CreateAttributeRequest createFirstEmailAttributeRequest = new CreateAttributeRequest
+{
+    EntityName = _customEntityName,
+    Attribute = new StringAttributeMetadata
+    {
+        SchemaName = "new_emailaddress",
+        RequiredLevel = new AttributeRequiredLevelManagedProperty(AttributeRequiredLevel.None),
+        MaxLength = 100,
+        FormatName = StringFormatName.Email,
+        DisplayName = new Label("Email Address", 1033),
+        Description = new Label("Email Address", 1033)
+    }
+};
+
+_serviceProxy.Execute(createFirstEmailAttributeRequest);
+Console.WriteLine("An email attribute has been added to the emailable entity.");
+
+// Create a second, alternate email address. Since there is already one 
+// email attribute on the entity, this will never be used for emailing
+// even if the first one is not populated.
+CreateAttributeRequest createSecondEmailAttributeRequest = new CreateAttributeRequest
+{
+    EntityName = _customEntityName,
+    Attribute = new StringAttributeMetadata
+    {
+        SchemaName = "new_secondaryaddress",
+        RequiredLevel = new AttributeRequiredLevelManagedProperty(AttributeRequiredLevel.None),
+        MaxLength = 100,
+        FormatName = StringFormatName.Email,
+        DisplayName = new Label("Secondary Email Address", 1033),
+        Description = new Label("Secondary Email Address", 1033)
+    }
+};
+
+_serviceProxy.Execute(createSecondEmailAttributeRequest);
+
+Console.WriteLine("A second email attribute has been added to the emailable entity.");
+```
+
+### See Also
+
+[Create entities using the Organization Service](entity-operations-create.md)  
+[Update and Delete entities using the Organization Service](entity-operations-update-delete.md)

powerapps-docs/developer/common-data-service/media/tutorial-write-plug-in-create-visual-studio-project.png

@@ -2,7 +2,7 @@
 title: "Update and Delete entities using the Organization Service (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn how to update and delete entities using the organization service." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 04/21/2019
 ms.reviewer: ""
 ms.service: powerapps
 ms.topic: "article"
@@ -17,16 +17,6 @@ search.app:
 ---
 # Update and Delete entities using the Organization Service
 
-<!-- 
-Adding parity with Web API topics
-
-include information from https://docs.microsoft.com/dynamics365/customer-engagement/developer/org-service/perform-specialized-operations-using-update 
-
-https://docs.microsoft.com/dynamics365/customer-engagement/developer/org-service/use-early-bound-entity-classes-create-update-delete
-https://docs.microsoft.com/dynamics365/customer-engagement/developer/org-service/manage-duplicate-detection-create-update
-
--->
-
 This topic will include examples using both late-bound and early-bound programming styles. More information: [Early-bound and Late-bound programming using the Organization service](early-bound-programming.md)
 
 Each of the examples uses a `svc` variable that represents an instance of a class that implements the methods in the <xref:Microsoft.Xrm.Sdk.IOrganizationService> interface. For information about the classes that support this interface see [IOrganizationService Interface](iorganizationservice-interface.md).
@@ -37,14 +27,21 @@ Each of the examples uses a `svc` variable that represents an instance of a clas
 > You should create a new entity instance, set the id attribute and any attribute values you are changing, and use that entity instance to update the record.
 
 > [!NOTE]
-> The metadata for attributes includes a `RequiredLevel` property. When this is set to `SystemRequired`, you cannot set these attributes to a null value. More information: [Attribute requirement level](../entity-attribute-metadata.md#attribute-requirement-level)
+> The metadata for attributes includes a `RequiredLevel` property. When this is set to `SystemRequired`, you cannot set these attributes to a null value. If you attempt this you will get error code  `-2147220989` with the message `Attribute: <attribute name> cannot be set to NULL`.
+> 
+> More information: [Attribute requirement level](../entity-attribute-metadata.md#attribute-requirement-level)
 
 ## Basic update
 
 Both of the examples below uses the <xref:Microsoft.Xrm.Sdk.IOrganizationService>.<xref:Microsoft.Xrm.Sdk.IOrganizationService.Update*> method to set attribute values for an entity that was previously retrieved.
 
 Use the <xref:Microsoft.Xrm.Sdk.Entity>.<xref:Microsoft.Xrm.Sdk.Entity.Id> property to transfer the unique identifier value of the retrieved entity to the entity instance used to perform the update operation.
 
+> [!NOTE]
+> If you attempt to update a record without a primary key value you will get the error: `Entity Id must be specified for Update`.
+> 
+> If you don't have a primary key value, you can also update records using alternate keys. More information: [Update with Alternate Key](#update-with-alternate-key)
+
 ### Late-bound example
 
 The following example shows using the <xref:Microsoft.Xrm.Sdk.Entity> class to create an account record using the  <xref:Microsoft.Xrm.Sdk.IOrganizationService>.<xref:Microsoft.Xrm.Sdk.IOrganizationService.Update*> method. 
@@ -223,6 +220,30 @@ svc.Update(account);
 
 When updating an entity you may change the values so that the record represents a duplicate of another record. More information: [Detect duplicate data using the Organization service](detect-duplicate-data.md)
 
+## Update with Alternate Key
+
+If you have an alternate key defined for an entity, you can use that in place of the primary key to update a record. You cannot use the early-bound class to specify the alternate key. You must use the [Entity(String, KeyAttributeCollection)](/dotnet/api/microsoft.xrm.sdk.entity.-ctor#Microsoft_Xrm_Sdk_Entity__ctor_System_String_Microsoft_Xrm_Sdk_KeyAttributeCollection_) constructor to specify the alternate key.
+
+If you want to use early bound types, you can convert the <xref:Microsoft.Xrm.Sdk.Entity> to an early bound class using the <xref:Microsoft.Xrm.Sdk.Entity.ToEntity``1> method.
+
+The following example shows how to update an `Account` entity using an alternate key defined for the `accountnumber` attribute.
+
+> [!IMPORTANT]
+> By default there are no alternate keys defined for any entities. This method can only be used when the environment is configured to define an alternate key for an entity.
+
+```csharp
+var accountNumberKey = new KeyAttributeCollection();
+accountNumberKey.Add(new KeyValuePair<string, object>("accountnumber", "123456"));
+
+Account exampleAccount = new Entity("account", accountNumberKey).ToEntity<Account>();
+exampleAccount.Name = "New Account Name";
+svc.Update(exampleAccount);
+```
+
+More information: 
+- [Work with alternate keys](../define-alternate-keys-entity.md)
+- [Use an alternate key to create a record](../use-alternate-key-create-record.md)
+
 ## Use Upsert
 
 Typically in data integration scenarios you will need to create or update data in Common Data Service from other sources. Common Data Service may already have records with the same unique identifier, which may be an alternate key. If an entity record exists, you want to update it. If it doesn't exist, you want to create it so that the data being added is synchronized with the source data. This is when you want to use upsert.
@@ -370,5 +391,4 @@ More information: [Behavior of specialized update operations](../special-update-
 
 [Create entities using the Organization Service](entity-operations-create.md)<br />
 [Retrieve an entity using the Organization Service](entity-operations-retrieve.md)<br />
-[Associate and disassociate entities using the Organization Service](entity-operations-associate-disassociate.md)<br />
-
+[Associate and disassociate entities using the Organization Service](entity-operations-associate-disassociate.md)<br />