Merge branch 'master' into matp-media-sweep

Author: Mattp123

powerapps-docs/developer/common-data-service/cds-sql-query.md

@@ -23,7 +23,9 @@ search.app:
 [!INCLUDE[cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
 > [!WARNING]
-> A problem has been identified with the Tabular Data Stream (TDS) endpoint. This feature is globally disabled, and we are working urgently to address the issue. This topic will be updated when the issue is resolved or when we have more information to share.
+> A problem has been identified with the Tabular Data Stream (TDS) endpoint. This feature is presently globally disabled as we work to address a security issue. A fix for the issue has been developed. Deployment of the fix and feature re-enablement to all public regions is planned for the first week of November 2020. A safe deployment practice is being followed so the feature may be available in your region earlier. Thank you for your patience on this matter.
+
+
 
 A SQL data connection is available on the Common Data Service endpoint. The SQL connection provides read-only access to the entity data of the target Common Data Service environment. This allows you to write and execute SQL queries against the entity data table. Table columns provide the attribute data of the entity. No custom views of the data have been provided.
 

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

@@ -91,9 +91,7 @@ Each entity that supports entity images will have three supporting attributes.
 |`EntityImage_URL`|`StringType`|An absolute URL to display the entity image in a client.|
 |`EntityImageId`|`UniqueIdentifierType`|The unique identifier of the image|
 
-More information: 
-- [Common Data Service Developer Guide Image attributes](/dynamics365/customer-engagement/developer/image-attributes)
-- [Common Data Service Developer Guide Sample: Set and retrieve entity images](/dynamics365/customer-engagement/developer/sample-set-retrieve-entity-images)
+More information: [Image attributes](image-attributes.md), [Sample: Set and retrieve entity images](org-service/samples/set-retrieve-entity-images.md)
 
 > [!NOTE]
 > This is different from the icon displayed for an entity in model-driven apps. The `IconVectorName` property contains the name of the SVG web resource that sets this.
@@ -183,7 +181,7 @@ Some entities will have different sets of options.
 |---------|---------|
 |0 : Open|1: Open|
 |1 : Completed|2: Made <br />4: Received|
-|2: Cancelled|3: Cancelled|
+|2: Canceled|3: Canceled|
 
 The set of valid state codes for an entity is not customizable, but the status codes are customizable. You can add additional `StatusCode` options for a corresponding `StateCode`.
 

powerapps-docs/developer/common-data-service/org-service/extend-code-generation-tool.md

@@ -101,7 +101,7 @@ public sealed class BasicFilteringService : ICodeWriterFilterService
 
 ```
 
-Download the sample: [CrmSvcUtilExtensions](https://code.msdn.microsoft.com/Create-extensions-for-the-b8b24d1d) and  [GeneratePickListEnums](https://code.msdn.microsoft.com/Create-extensions-for-the-3dd56a27). 
+Download the sample: [CrmSvcUtilExtensions](https://github.com/microsoft/Dynamics365-Apps-Samples/tree/master/samples-from-msdn/BasicFilteringService) and  [GeneratePickListEnums](https://github.com/microsoft/Dynamics365-Apps-Samples/tree/master/samples-from-msdn/GeneratePicklistEnums). 
 
 The **GeneratePicklistEnums** sample extension outputs a source code file that contains enumerations for all option sets, state codes, and status codes. For an example of how to use these enumerations, see the `SampleCode\CS\QuickStart` sample.  
 

powerapps-docs/developer/component-framework/sample-controls/localization-api-control.md

@@ -14,7 +14,7 @@ author: Nkrb
 
 This sample showcases how localization is done for code components. In this sample, we use the [Increment component](increment-control.md) to localize the text that is displayed on the increment button based on the user’s selected language. 
 
-Power Apps component framework uses the concept of implementing String(resx) web resources that is used to manage the localized strings shown on any user interface. More information: [String(Resx) Webresources](https://docs.microsoft.com/dynamics365/customer-engagement/developer/resx-web-resources). You can download the sample component from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework/TS_LocalizationAPI).
+Power Apps component framework uses the concept of implementing String(resx) web resources that is used to manage the localized strings shown on any user interface. More information: [String(Resx) Web resources](https://docs.microsoft.com/dynamics365/customer-engagement/developer/resx-web-resources). You can download the sample component from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/component-framework/TS_LocalizationAPI).
 
 > [!div class="mx-imgBorder"]
 > ![Localization API component](../media/localization-api-control.png "Localization API component")
@@ -181,8 +181,8 @@ export class TSLocalizationAPI
 ```xml
 <?xml version="1.0" encoding="utf-8"?>
 <root>
-<xsd:schema id="root" xmlns="" xmlns:xsd="https://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
-<xsd:import namespace="https://www.w3.org/XML/1998/namespace" />
+<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
+<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
 <xsd:element name="root" msdata:IsDataSet="true">
 <xsd:complexType>
 <xsd:choice maxOccurs="unbounded">
@@ -265,8 +265,8 @@ export class TSLocalizationAPI
 ```xml
 <?xml version="1.0" encoding="utf-8"?>
 <root>
-<xsd:schema id="root" xmlns="" xmlns:xsd="https://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
-<xsd:import namespace="https://www.w3.org/XML/1998/namespace" />
+<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
+<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
 <xsd:element name="root" msdata:IsDataSet="true">
 <xsd:complexType>
 <xsd:choice maxOccurs="unbounded">
@@ -349,8 +349,8 @@ export class TSLocalizationAPI
 ```xml
 <?xml version="1.0" encoding="utf-8"?>
 <root>
-<xsd:schema id="root" xmlns="" xmlns:xsd="https://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
-<xsd:import namespace="https://www.w3.org/XML/1998/namespace" />
+<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
+<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
 <xsd:element name="root" msdata:IsDataSet="true">
 <xsd:complexType>
 <xsd:choice maxOccurs="unbounded">

powerapps-docs/developer/model-driven-apps/clientapi/clientapi-form-context.md

@@ -103,7 +103,7 @@ reference)](reference/collections.md).
 |**formContext.ui.navigation.**[items](reference/formContext-ui-navigation.md)|The **formContext.ui.navigation.items** collection provides access to navigation items that are defined using the navigation area of the form editor. People navigate to these using the command bar.|
 | **formContext.ui.**[quickForms](reference/formContext-ui-quickForms.md) | Provides methods to access all the quick view controls and its constituent controls on the Customer Enagagement forms.| **Xrm.Page.ui.tabs** collection provides access to each of these tabs.|
 | **formContext.ui.**[tabs](reference/formContext-ui-tabs.md) | You can organize each form by using one or more tabs. This collection provides access to each of these tabs.|
-| **formContext.ui.tabs.**[sections](reference/formContext-ui-sections.md) | You can organize each form tab by using one or more sections. The tab **sections** collection provides access to each of these sections.|
+| **formContext.ui.tabs.**[sections](reference/formContext-ui-sections.md) | You can organize each form tab by using one or more sections. The tab **sections** collection provides access to each of these sections. You need to define the tab which contains the desired section or iterate through each tab to find the relevant section.|
 
 
 

powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-Navigation/openAlertDialog.md

@@ -41,7 +41,7 @@ The following sample code displays an alert dialog. Clicking **Yes** button in t
 var alertStrings = { confirmButtonLabel: "Yes", text: "This is an alert.", title: "Sample title" };
 var alertOptions = { height: 120, width: 260 };
 Xrm.Navigation.openAlertDialog(alertStrings, alertOptions).then(
-    function success(result) {
+    function (success) {
         console.log("Alert dialog closed");
     },
     function (error) {

powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-data/save.md

@@ -33,7 +33,7 @@ You can also set an object to control how appointment, recurring appointment, or
 |successCallback|Function|No|A function to call when the operation succeeds.|
 |errorCallback|Function|No|A function to call when the operation fails. An object with the following properties will be passed:<br/><br/>- **errorCode**: Number. The error code.<br/><br/>- **message**: String. A localized error message.|
 
-[!NOTE]
+> [!NOTE]
 > When working with forms, and you call the `formContext.data.save` method, make sure that you also call the [preventDefault](../save-event-arguments/preventDefault.md) to ensure that any default save operation is not triggered when a user saves the form.
 
 

powerapps-docs/maker/canvas-apps/app-from-sharepoint.md

@@ -66,7 +66,7 @@ The principles of generating an app won't change even if you create a list that'
 
 If you create an app of a custom list from the SharePoint Online command bar, the app appears as a view of that list. You can also run the app on an iOS or Android device, in addition to a web browser.
 
-1. In SharePoint Online, open a custom list, select **PowerApps** on the command bar, and then select **Create an app**.
+1. In SharePoint Online, open a custom list, select **Power Apps** on the command bar, and then select **Create an app**.
 
     ![Create an app](./media/app-from-sharepoint/generate-new-app.png)
 

powerapps-docs/maker/canvas-apps/dependent-drop-down-lists.md

@@ -60,7 +60,7 @@ After that change, you can ignore the **Title** column, or you can [remove it](h
 
 ## Open the form
 
-1. Open the **Incidents** list, and then select **PowerApps** > **Customize forms**.
+1. Open the **Incidents** list, and then select **Power Apps** > **Customize forms**.
 
     > [!div class="mx-imgBorder"]
     > ![Open the Incidents list, and then select Power Apps > Customize forms.](./media/dependent-drop-down-lists/open-form.png "Open the Incidents list, and then select Power Apps > Customize forms.")