Merge pull request #1251 from MicrosoftDocs/master

Publish: add App object to signals.md

Author: AFTOwen

powerapps-docs/developer/model-driven-apps/clientapi/reference/attributes/getAttributeType.md

@@ -1,13 +1,12 @@
 ---
 title: "getAttributeType (Client API reference)| MicrosoftDocs"
-ms.date: 12/17/2018
-ms.service: "crm-online"
+ms.date: 02/13/2019
+ms.service: "powerapps"
 ms.topic: "reference"
-applies_to: "Dynamics 365 (online)"
 ms.assetid: 9ef1c886-a0b8-4ba9-bb9f-e6ecfa9d6dff
 author: "KumarVivek"
 ms.author: "kvivek"
-manager: "amyla"
+manager: "annbe"
 search.audienceType: 
   - developer
 search.app: 
@@ -40,6 +39,6 @@ This method will return one of the following **string** values:
 - lookup
 - memo
 - money
-- multioptionset
+- multiselectoptionset
 - optionset
 - string

powerapps-docs/maker/canvas-apps/functions/function-first-last.md

@@ -33,7 +33,7 @@ The **LastN** function returns the last set of records of a table; the second ar
 ## Syntax
 **First**( *Table* )<br>**Last**( *Table* )
 
-* *Table* - Rquired. Table to operate on.
+* *Table* - Required. Table to operate on.
 
 **FirstN**( *Table* [, *NumberOfRecords* ] )<br>**LastN**( *Table* [, *NumberOfRecords* ] )
 

powerapps-docs/maker/canvas-apps/functions/media/appobject-runonstart.png

@@ -26,7 +26,7 @@ All signals return a [record](../working-with-tables.md#records) of information.
 ### Acceleration
 The **Acceleration** signal returns the device's acceleration in three dimensions relative to the device's screen. Acceleration is measured in *g* units of 9.81 m/second<sup>2</sup> or 32.2 ft/second<sup>2</sup> (the acceleration that the Earth imparts to objects at its surface due to gravity).
 
-| Signal Property | Description |
+| Property | Description |
 | --- | --- |
 | **Acceleration.X** |Right and left.  Right is a positive number. |
 | **Acceleration.Y** |Forward and back.  Forward is a positive number. |
@@ -35,21 +35,33 @@ The **Acceleration** signal returns the device's acceleration in three dimension
 ### App
 The **App** signal returns information about the running app.
 
-| Signal Property | Description |
+| Property | Description |
 | --- | --- |
 | **App.ActiveScreen** |Screen that's displayed. Returns a screen object, which you can use to reference properties of the screen or compare to another screen to determine which screen is displayed.  By using the **[Back](function-navigate.md)** or **[Navigate](function-navigate.md)** function, you can change the displayed screen. |
 
+The **App** object also has a [behavior formula](../working-with-formulas-in-depth.md) that you can set.
+
+| Property  | Description |
+| --- | --- |
+| **OnStart** | The behavior of the app when the user starts it. This property is commonly used to retrieve and cache data into collections with the **[Collect](function-clear-collect-clearcollect.md)** function, set up variables with the **[Set](function-set.md)** function, and navigate to an initial screen with the **[Navigate](function-navigate.md)** function. This formula is evaluated before the first screen appears. No screen is loaded, so you can't set context variables with the **[UpdateContext](function-updatecontext.md)** function. However, you can pass context variables with the **Navigate** function. |
+
+The **App** object appears at the top of the hierarchical list of controls in the left navigation pane, and you can select this object like a control on a screen. After you select the object, you can view and edit one of its properties if you select that property in the drop-down list to the left of the formula bar.  
+
+After you change the **OnStart** property, you can test it by hovering over the **App** object in the left navigation pane, selecting the ellipsis (...) that appears, and then selecting **Run OnStart**. Unlike when the app is loaded for the first time, existing collections and variables will already be set. Use the **[ClearCollect](function-clear-collect-clearcollect.md)** function instead of the **Collect** function to start with empty collections.
+
+ ![App item context menu with Run OnStart](media/appobject-runonstart.png)
+
 ### Compass
 The **Compass** signal returns the compass heading of the top of the screen. The heading is based on magnetic north.
 
-| Signal Property | Description |
+| Property | Description |
 | --- | --- |
 | **Compass.Heading** |Heading in degrees.  Returns a number 0 to 360, and 0 is north. |
 
 ### Connection
 The **Connection** signal returns the information about the network connection. When on a metered connection, you may want to limit how much data you send or receive over the network.
 
-| Signal Property | Description |
+| Property | Description |
 | --- | --- |
 | **Connection.Connected** |Returns a Boolean **true** or **false** value that indicates whether the device is connected to a network. |
 | **Connection.Metered** |Returns a Boolean **true** or **false** value that indicates whether the connection is metered. |
@@ -61,7 +73,7 @@ When a user accesses the ___location information for the first time, the device may
 
 As the ___location changes, dependencies on the ___location will continuously recalculate, which will consume power from the device's battery. To conserve battery life, you can use the **[Enable](function-enable-disable.md)** and **[Disable](function-enable-disable.md)** functions to turn ___location updates on and off. Location is automatically turned off if the displayed screen doesn't depend on ___location information.
 
-| Signal Property | Description |
+| Property | Description |
 | --- | --- |
 | **Location.Altitude** |Returns a number that indicates the altitude, measured in feet, above sea level. |
 | **Location.Latitude** |Returns a number, from -90 to 90, that indicates the latitude, as measured in degrees from the equator. A positive number indicates a ___location that's north of the equator. |

powerapps-docs/maker/canvas-apps/functions/signals.md

@@ -2,7 +2,7 @@
 title: "Common issues and resolutions for Solution Checker | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces"
 description: " A list of common issues and resolutions within Solution Checker"
 keywords: ""
-ms.date: 01/28/2019
+ms.date: 02/11/2019
 ms.service:
   - "powerapps"
 ms.custom:
@@ -64,6 +64,24 @@ To address this issue, check or create smaller solutions to be analyzed. To mini
 - When you add HTML web resources, include any dependent scripts that are defined within the HTML web resource.
 - When you add custom workflows, include the assembly used within the workflow.
 
+## Solution Checker run or download results don't complete 
+Shortly after running Solution Checker the operation doesn't commplete and the following message is displayed:<br />
+"We weren't able to run the check on *SOLUTIONNAME* Solution. Try running it again." <br />
+![Weren't able to run](media/solution-checker-werent-able-to-run.png)
+
+This issue occurs because the organization is in the **administration mode** state and Solution Checker is unable to validate the user's permissions executing the request. To resolve this issue, disable administration mode. 
+
+### Disable administration mode for an instance
+1. Access the Dynamics 365 for Customer Engagement instance picker: https://port.crm.dynamics.com/G/Instances/InstancePicker.aspx.
+2. Select the instance that has issues running Solution Checker.
+3. Select **ADMIN**.<br />
+![Instance Admin](media/solution-checker-instance-admin.png)
+
+4. Clear **Enable administration mode**. <br />
+![Disable Admin mode](media/solution-checker-instance-disable-admin-mode.png)
+
+5. Run Solution Checker again.
+
 ## Solution Checker will not process patched solutions
 
 If a solution has had a [patch](https://docs.microsoft.com/powerapps/developer/common-data-service/create-patches-simplify-solution-updates) applied, Solution Checker will fail to export the solution for analysis. When a solution has had a patch applied, the original solution becomes locked and it can’t be changed or exported as long as there are dependent patches that exist in the organization that identify the solution as the parent solution.
@@ -74,9 +92,9 @@ To address this issue, clone the solution so that all patches related to the sol
 
 When HTML web resources are processed within Solution Checker, the HTML web resource is processed separately than the JavaScript within the HTML web resource. Due to this, the line number of the violation found within `<script>` of the HTML web resource will not be correct.
 
-## JS1001 syntax issue for web resources
+## Web-unsupported-syntax issue for web resources
 
-ECMAScript 6 (2015) or later versions are not currently supported. When Solution Checker analyzes JavaScript using ECMAScript 6 or later, a JS1001 syntax issue for the web resource is reported.  
+ECMAScript 6 (2015) or later versions are not currently supported for Solution Checker. When Solution Checker analyzes JavaScript using ECMAScript 6 or later, a web-supported-syntax issue for the web resource is reported.  
 
 ## See also
 [Best practices and guidance for the Common Data Service for Apps](../../developer/common-data-service/best-practices/index.md)<br />