Merge branch 'master' into rtw-docs

Author: KumarVivek

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

@@ -27,6 +27,8 @@
       href: use-fetchxml-left-outer-join-query-records-not-in.md
     - name: Page large result sets with FetchXML
       href: org-service/page-large-result-sets-with-fetchxml.md
+    - name: Use column comparison in queries
+      href: column-comparison.md
   - name: "Use SQL to query data (Preview)"
     href: cds-sql-query.md
   - name: Saved Queries

powerapps-docs/developer/common-data-service/authenticate-oauth.md

@@ -1,7 +1,7 @@
 ---
 title: "Use OAuth with Common Data Service (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn how to authenticate using OAuth with Common Data Service" # 115-145 characters including spaces. This abstract displays in the search result.
-ms.custom: ""
+ms.custom: has-adal-ref
 ms.date: 10/31/2018
 ms.reviewer: "pehecke"
 ms.service: powerapps

powerapps-docs/developer/common-data-service/column-comparison.md

@@ -0,0 +1,70 @@
+---
+title: "Use column comparison in queries (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+description: "Learn how to compare columns when querying business data." # 115-145 characters including spaces. This abstract displays in the search result.
+ms.custom: ""
+ms.date: 07/08/2020
+ms.reviewer: "pehecke"
+ms.service: powerapps
+ms.topic: "article"
+author: "NHelgren" # GitHub ID
+ms.author: "nhelgren" # MSFT alias of Microsoft employees only
+manager: "mayadu" # MSFT alias of manager or PM counterpart
+search.audienceType: 
+  - developer
+search.app: 
+  - PowerApps
+  - D365CE
+---
+
+# Use column comparison in queries
+
+In the Common Data Service, users can perform a column comparison for the
+following condition operators using FetchXML, Web API, or the SDK API:
+
+- Equal
+- NotEqual
+- GreaterThan
+- GreaterEqual
+- LessThan
+- LessEqual
+
+This will allow the comparison of an attribute against a specific value and
+return all found records, or allow the comparison of two attributes to return
+all records with a matching value.
+
+## Limitations
+
+Listed below are the limitations for the current Common Data Service column comparison support.
+
+- You can only compare columns within a single entity
+- Only two columns may be compared at a time.
+- Multi-value condition operators are not supported (i.e., "in").
+- Extended condition operators are not supported (i.e., "creditlimit \> spends+1000").
+- Incompatible attribute comparison is not supported. For example, "int vs. int" attributes is a valid comparison but "int vs. string" attributes is not a valid comparison.
+
+## Column comparison using FetchXML
+
+The following example shows how to compare columns using FetchXML:
+
+```xml
+<fetch>
+  <entity name='contact' >
+    <attribute name='firstname' />
+    <filter>
+      <condition attribute='firstname' operator='eq' valueof='lastname'/>
+    </filter>
+  </entity>
+</fetch>
+```
+
+For FetchXML requests, a new node `valueof` has been added inside the condition
+node. The `valueof` tag is used to identify the attribute that is being compared
+to the selected attribute. In the above example, the 'firstname' column is being
+compared against the 'lastname' column and will return any records that contain
+the same value across both attributes.
+
+### See Also
+
+[Use FetchXML to construct a query](use-fetchxml-construct-query.md)  
+[Column comparison using the Web API](webapi/query-data-web-api.md#column-comparison-using-the-web-api)  
+[Column comparison using the SDK API](org-service/use-conditionexpression-class.md#column-comparison-using-the-sdk-api)

powerapps-docs/developer/common-data-service/file-attributes.md

@@ -2,7 +2,7 @@
 title: "File attributes (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn about File attributes that store file data within the application, supporting attributes, retrieving data, and uploading file data." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 06/17/2020
+ms.date: 07/09/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -150,6 +150,18 @@ Headers:
 x-ms-transfer-mode: chunked 
 x-ms-file-name: sample.png
 ```
+
+**Request** (alternate form)
+
+This form of the request uses a query string parameter and supports non-ASCII language file names. If the file name is specified in both the header and as a query string parameter, the header value has precedence.
+
+```http
+PATCH [Organization URI]/api/data/v9.1/accounts(id)/myfileattribute?x-ms-file-name=测试.txt
+
+Headers: 
+x-ms-transfer-mode: chunked
+```
+
 **Response**
 ```http
 200 OK 

powerapps-docs/developer/common-data-service/org-service/use-conditionexpression-class.md

@@ -82,7 +82,41 @@ condition3.Operator = ConditionOperator.Equal;
 condition3.Values.Add(AccountState.Active);  
 
 ```  
-  
+
+## Column comparison using the SDK API
+
+The following example shows how to compare columns using SDK API and the Organization service:
+
+```csharp
+public ConditionExpression
+(
+  string attributeName,
+  ConditionOperator conditionOperator,
+  bool compareColumns,
+  object value
+)
+
+public ConditionExpression
+(
+  string attributeName,
+  ConditionOperator conditionOperator,
+  bool compareColumns,
+  object[] values
+)
+```
+
+In the SDK, two APIs are introduced to support column comparison. The
+first identifies the original attribute, the second allows
+for the inclusion of the attribute you want to compare it against.
+
+If `compareColumns` is passed in as `true`, it will compare the two attributes
+and return all records that match.
+
+If a `false` value is passed, it will return all records for one attribute and
+return values that match the provided value.
+
+More information: [Use column comparison in queries](../column-comparison.md)
+
 ### See also  
  [Building Queries](build-queries-with-queryexpression.md)   
  [Build Queries with QueryExpression](build-queries-with-queryexpression.md)   

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

@@ -44,16 +44,99 @@ To get Power Apps CLI, do the following:
 
 ## Common commands
 
-This table lists some common commands used in the CLI:
+This table lists some of the common commands used in the CLI:
 
-|Command|Description|Examples|
+|Command|Description|
+|-------|-----------|
+|[pcf](#pcf)|Commands to work with [Power Apps component framework](/powerapps/developer/component-framework/overview).|
+|[solution](#solution)|Commands for working with [Common Data Service solution projects](/powerapps/maker/common-data-service/solutions-overview).|
+|[auth](#auth)|Commands to [authenticate to Common Data Service](/powerapps/developer/component-framework/import-custom-controls#connecting-to-your-environment).|
+|[telemetry](#telemetry)|Manages the telemetry settings.|
+|[plugin](#plugin)|Manages to create a [plug-in](/powerapps/developer/common-data-service/plug-ins) project.|
+|[org](#org)|Command to work with Common Data Service environment.|
+
+### Pcf
+
+Commands to work with [Power Apps component framework](/powerapps/developer/component-framework/overview). It has the following parameters:
+
+#### Parameters
+
+|Property Name|Description|Example|
+|-------------|-----------|-------|
+|init|Initializes the code component project. It has the following parameters <br/> - *namespace*: Namespace of the code component. <br/> - *name*: Name of the code component. <br/> - *template*: Field or dataset| `pac pcf init --namespace<SampleNameSpace --name SampleComponent --template field`|
+|push|Pushes the code component to the Common Data Service instance with all the latest changes. It has the following parameter: <br/> - *publisher-prefix*: Publisher prefix of the organization.|`pac pcf push --publisher-prefix dev`|
+|version|Updates the component manifest file with the specified patch version. It has the following parameters: <br/> - *patchversion*: Patch version of the code component. `patchversion` will only take value of the third part of the version tuple: `Major.Minor.Patch`.<br/> - *path*: Absolute or relative path of the component manifest file.<br/> - *allmanifests*: Updates the patch version for all the component manifest files. <br/> - *updatetarget*: Updates the specified manifest file. It has two values, build and project.<br/> - *strategy*: Updates patch version for the manifest files using specified strategy values. It has the following values: <br/> - *gittags*: Use git tags to decide if a particular component’s patch version needs to be updated.<br/> *filetracking*: Use .csv file to decide if a particular component’s patch version needs to be updated. <br/> - *manifest*: Increments the patch version by 1 for all the components.|`pac pcf version --patchversion 1.0.0.0 --path c:\Users\Downloads\SampleComponent --allmanifests`  <br/><br/> `pac pcf version --strategy gittags`|
+
+
+### Solution
+
+Commands for working with [Common Data Service solution projects](/powerapps/maker/common-data-service/solutions-overview). It has the following parameters:
+
+#### Parameters
+
+|Property Name|Description|Example|
+|-------------|-----------|-------|
+|init|Initializes the solution project.  It has the following parameters:<br/>  - *publisher-name*: Publisher name of the organization. <br/>  - *publisher-prefix*: Publisher prefix of the organization.|`pac solution init --publisher-name developer --publisher-prefix dev`  |
+|add-reference|Sets the reference path to the component project folder by passing the `path` parameter.|`pac solution add-reference --path c:\Users\Downloads\SampleComponent`|
+|clone|Creates a solution project based up on the existing solution project. It has the following parameters:<br/> -*name*: The name of the solution to be exported.<br/> -*targetversion*: The version that the exported solution supports.<br/> -*include*: Settings that should be included in the solution being exported. <br/> It has the following values: autonumbering, calendar, customization, emailtracking, externalapplications, general, isvconfig, marketing, outlooksynchronization, relationshiproles, sales|`pac solution clone -–name  sampleSolution --version 1.0.0.2 --include general`|
+|export|Exports a Common Data Service solution project from the current organization. It has the following parameters:<br/> -*path*: Place where the exported solution zip file will be saved.<br/> - *name*: Name oft he solution that needs to be exported.<br/> - *managed*: Defines whether the solution should be exported as a managed solution or not.<br/>-*targetversion*: The version that the exported solution supports.<br/> -*include*: Settings that should be included in the solution being exported.|`pac solution export --path c:\Users\Documents -- name SampleComponentSolution -- managed true -- targetversion 10.0.03 --include general`|
+
+### Auth
+
+Commands to [authenticate to Common Data Service](/powerapps/developer/component-framework/import-custom-controls#connecting-to-your-environment). It has the following parameters:
+
+#### Parameters
+
+|Parameter Name|Description|Example|
+|-------------|-----------|-------|
+|create| Creates the authentication profile for your organization by passing the `url` parameter. Pass the organization url for the `url` parameter.|`pac auth create --url https://Myorg.crm.dynamics.com`|
+|list|Provides the list of authentication profiles.|`pac auth list`|
+|select|Provides a way to switch between previously created authentication profiles by passing the `index` parameter.|`pac auth select --index 2`|
+|delete|Deletes the authentication profile created by passing  the `index` parameter.|`pac auth delete --index 2`|
+|clear|Clears all the authentication profile created on the local machine.|  `pac auth clear`|
+
+### Telemetry
+
+Manages the telemetry settings. It has the following parameters:
+
+#### Parameters
+
+|Parameter Name|Description|Example|
+|------------|------------|---------|
+|enable|Enables the telemetry option.|`pac telemetry enable`|
+|disable|Disables the telemetry option.| `pac telemetry disable`|
+|status|Returns whether the telemetry is enabled or disabled.|`pac telemetry status`|
+
+### Org
+
+Command to work with Common Data Service organizations.
+
+#### Parameters
+
+|Parameter Name|Description|Example|
+|-------------|-----------|--------|
+|who|Displays information about the current Common Data Service organizations.|`pac org who`|
+
+
+### Plugin
+
+Manages to create a [plug-in](/powerapps/developer/common-data-service/plug-ins) project.
+
+#### Parameters
+
+|Parameter Name|Description|Example|
+|-------------|-----------|--------|
+|init|Initializes a directory with a new plugin class library.|`pac plugin init`|
+
+
+<!--|Command|Description|Examples|
 |------|-----------|--------|
 |**pcf**|Commands for working with [Power Apps component framework](/powerapps/developer/component-framework/overview). It has the following parameters: <br/> - **init**: Initializes the code component project. It has the following parameters <br/> - *namespace*: Namespace of the code component. <br/> - *name*: Name of the code component. <br/> - *template*: Field or dataset <br/> - **push**: Pushes the code component to the Common Data Service instance with all the latest changes. It has the following parameter: <br/> - *publisher-prefix*: Publisher prefix of the organization.<br/> - **Version**: Updates the component manifest file with the specified patch version. It has the following parameters: <br/> - *patchversion*: Patch version of the code component. `patchversion` will only take value of the third part of the version tuple: `Major.Minor.Patch`.<br/> - *path*: Absolute or relative path of the component manifest file.<br/> - *allmanifests*: Updates the patch version for all the component manifest files. <br/> - *strategy*: Updates patch version for the manifest files using specified strategy values.| `pac pcf init --namespace <specify your namespace here> --name <Name of the code component> --template <component type>` <br/> <br/> `pac pcf push --publisher-prefix <your publisher prefix>` <br/><br/> `pac pcf version --patchversion <number> --path <Absolute or relative path to component manifest file --allmanifests`  <br/><br/> `pac pcf version --strategy gittags`|
 |**solution**|Commands for working with [Common Data Service solution projects](/powerapps/maker/common-data-service/solutions-overview). It has the following parameters: <br/> - **init**: Initializes the solution project. It has the following parameters:<br/>  - *publisher-name*: Publisher name of the organization. <br/>  - *publisher-prefix*: Publisher prefix of the organization. <br/> - **add-reference**: Sets the reference path to the component project folder by passing the `path` parameter.<br/> - **clone**: Creates a solution project based up on the existing solution project by passing the following parameters:<br/> -*name*: The name of the solution to be exported.<br/> -*targetversion*: The version that the exported solution supports.<br/> -*include*: Settings that should be included in the solution being exported.<br/> -**Export**: Exports a Common Data Service solution project from the current organization. It has the following parameters:<br/> -*path*: Place where the exported solution zip file will be saved.<br/> - *name*: Name oft he solution that needs to be exported.<br/> - *managed*: Defines whether the solution should be exported as a managed solution or not.<br/>-*targetversion*: The version that the exported solution supports.<br/> -*include*: Settings that should be included in the solution being exported.|`pac solution init --publisher-name <enter your publisher name> --publisher-prefix <enter your publisher prefix>` <br/><br/> `pac solution add-reference --path <path to your Power Apps component framework project>`<br/><br/> `pac solution clone –name<name of the solution to be exported> --version <version of your solution> --include <settings that should be included>`|
 |**auth**|Commands to [authenticate to Common Data Service](/powerapps/developer/component-framework/import-custom-controls#connecting-to-your-environment). It has the following parameters: <br/> - **create**: Creates the authentication profile for your organization by passing the `url` parameter. Pass the organization url for the `url` parameter. <br/> - **list**: Provides the list of authentication profiles. <br/> - **select**: Provides a way to switch between previously created authentication profiles by passing the `index` parameter.<br/> - **delete**: Deletes the authentication profile created by passing  the `index` parameter.<br/> - **clear**: Clears all the authentication profile created on the local machine.|`pac auth create --url <your Common Data Service org’s url>` <br/> <br/> `pac auth list` <br/><br/> `pac auth select --index <index of the active profile>`<br/><br/> `pac auth clear`|
 |**telemetry**|Manages the telemetry settings. It has the following parameters: <br/>- *enable*: Enables the telemetry option.<br/> - *disable*: Disables the telemetry option.<br/> - *status*: Returns whether the telemetry is enabled or disabled.|`pac telemetry enable` <br/><br/> `pac telemetry disable`|
 |**org**|Command to work with Common Data Service.|`pac org who`|
-|**plugin**|Manages to create a [plug-in](/powerapps/developer/common-data-service/plug-ins) project|`pac plugin init`|
+|**plugin**|Manages to create a [plug-in](/powerapps/developer/common-data-service/plug-ins) project|`pac plugin init`|-->
 
 ## Uninstall Power Apps CLI
 

powerapps-docs/developer/common-data-service/webapi/query-data-web-api.md

@@ -861,6 +861,16 @@ The change tracking feature allows you to keep the data synchronized in an effic
 
 More information: [Use change tracking to synchronize data with external systems](../use-change-tracking-synchronize-data-external-systems.md).
 
+## Column comparison using the Web API
+
+The following example shows how to compare columns using the Web API:
+
+```http
+https://<environment-root>/contacts?$select=firstname&$filter=firstname eq lastname
+```
+
+More information: [Use column comparison in queries](../column-comparison.md)
+
 ### See also
 
 [Web API Query Data Sample (C#)](samples/query-data-csharp.md)<br />

powerapps-docs/developer/model-driven-apps/TOC.yml

@@ -826,6 +826,8 @@
     href: define-ribbon-display-rules.md
   - name: Define ribbon actions
     href: define-ribbon-actions.md
+  - name: Override the default behavior to open records in grids
+    href: override-default-open-behavior-grids.md
   - name: Pass data from a page as a parameter to Ribbon Actions
     href: pass-data-page-parameter-ribbon-actions.md
   - name: Define custom actions to modify the ribbon

powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-WebApi/createRecord.md

@@ -109,6 +109,9 @@ Xrm.WebApi.createRecord("account", data).then(
 
  You can create entities related to each other by defining them as navigation properties values. This is known as *deep insert*. In this example, we will create a sample account record along with the primary contact record and an associated opportunity record.
 
+> [!NOTE]
+> Creating related entity records in a single create operation is not supported for offline mode.
+
 ```JavaScript
 // define data to create primary and related entity records
 var data =
@@ -205,4 +208,4 @@ Xrm.WebApi.offline.createRecord("account", data).then(
 
 [Create an entity using the Web API](../../../../common-data-service/webapi/create-entity-web-api.md) 
 
-[Xrm.WebApi](../xrm-webapi.md)
+[Xrm.WebApi](../xrm-webapi.md)