Merge pull request #3748 from MicrosoftDocs/master

updates

Author: mduelae

.acrolinx-config.edn

@@ -1,12 +1,5 @@
 {:allowed-branchname-matches ["^master$"]
  :allowed-filename-matches ["powerapps-docs"]
- :targets
- {
-     :scores
-     {
-         :qualityscore 80
-     }
- }
  :guidance-profile "dc59e3ef-24fd-46d7-9156-0491aaae6bef" ;; Profile ID for "BAG-specific" 
  :acrolinx-check-settings
  {

powerapps-docs/developer/common-data-service/media/isv-failure-details-drill-through.png

@@ -15,8 +15,6 @@ search.app:
 ---
 # Controls (Client API reference)
 
-
-
 A control represents an HTML element present on the form. Some controls are bound to a specific attribute, whereas others may represent unbound controls such as an IFRAME, Web resource, or a sub grid that has been added to the form. 
 
 The **control** object provides methods to change the presentation or behavior of a control and identify the corresponding attribute. You access controls using one of the following collections: 
@@ -330,6 +328,13 @@ The Sliverlight web resource has these additional methods:
 </tr>
 </table>
 
+> [!TIP]
+> If you want to modify all the controls bound to an attribute on a form, use the controls collection inside the attribute type. For example, to add notification to each control bound to the `name` attribute, you can do the following:
+ >  ```JavaScript
+ >   const notification = { messages: ['Sample Notification on Name Controls'], notificationLevel: 'RECOMMENDATION', uniqueId: 'my_unique_id'};
+ >  formContext.getAttribute("name").controls.forEach(control => control.addNotification(notification));
+ > ```
+
 
 ### Related topics
 

powerapps-docs/developer/common-data-service/media/isv-install-error-details.png

@@ -37,6 +37,16 @@ When the `arg` value is not provided, it returns an array of all the controls on
 
 **Description**: Object if you use the method with parameter; object collection if you use the method without any parameters.
 
+> [!TIP]
+> If you want to modify the all the controls bound to an attribute on a form, use the controls collection inside the attribute type.
+For example, to add notification to each control bound to the `name` attribute, you can do the following:
+> ```JavaScript
+>  const notification = {
+>  messages: ['Sample Notification on Name Controls'],
+>  notificationLevel: 'RECOMMENDATION',
+>  uniqueId: 'my_unique_id'};
+> formContext.getAttribute("name").controls.forEach(control => control.addNotification(notification));
+> ```
 
 
 ### Related topics

powerapps-docs/developer/common-data-service/media/isv-install-failure-icon.png

@@ -16,8 +16,6 @@ search.app:
 ---
 # setVisible (Client API reference)
 
-
-
 Sets a value that indicates whether the control is visible. 
 
 ## Control types supported
@@ -34,6 +32,9 @@ All
 |--|--|--|--|
 |bool|Boolean|Yes|Specify **true** to show the control; **false** to hide the control.|
 
+>[!NOTE]
+> If a control is set to false and is in a section that is hidden and if you set the control to true, the section will be visible.
+
 ### Related topics
 
 [getVisible](getVisible.md)

powerapps-docs/developer/common-data-service/media/isv-install-failure-report.png

@@ -3,8 +3,7 @@ title: "Define ribbon actions (model-driven apps) | Microsoft Docs" # Intent and
 description: "Learn about defining the actions to be performed by a command bar or ribbon control in a <CommandDefinition> element together with rules that control whether the control is enabled or visible in the ribbon." # 115-145 characters including spaces. This abstract displays in the search result."
 keywords: ""
 ms.date: 05/07/2020
-ms.service:
-  - PowerApps
+ms.service: powerapps
 ms.topic: article
 ms.assetid: fbb7ff68-e4be-d8c2-069f-6a4a69665b56
 author: Nkrb # GitHub ID
@@ -20,8 +19,6 @@ search.app:
 
 # Define ribbon actions
 
-<!-- https://docs.microsoft.com/dynamics365/customer-engagement/developer/customize-dev/define-ribbon-actions -->
-
 Define the actions to be performed by a command bar or ribbon control in a `<CommandDefinition>` element together with rules that control whether the control is enabled or visible in the ribbon.  
 
  A Ribbon control can perform two types actions and may include multiple actions:  

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

@@ -6,9 +6,9 @@ ms.date: 05/07/2020
 ms.service: powerapps
 ms.topic: article
 ms.assetid: 201f5db9-be65-7c3b-8202-822d78338bd6
-author: HaoZhou 
-ms.author: hazhouMSFT 
-manager: annbe 
+author: Nkrb 
+ms.author: nabuthuk
+manager: kvivek 
 ms.reviewer: kvivek 
 search.audienceType: 
   - developer