Skip to content

Commit ce29196

Browse files
authored
Live publish
2 parents 8fb6eda + 33dc2e0 commit ce29196

File tree

9 files changed

+83
-12
lines changed

9 files changed

+83
-12
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -491,8 +491,12 @@
491491
href: clientapi/reference/formcontext-ui-formselector/getId.md
492492
- name: getLabel
493493
href: clientapi/reference/formcontext-ui-formselector/getLabel.md
494+
- name: getVisible
495+
href: clientapi/reference/formcontext-ui-formselector/getVisible.md
494496
- name: navigate
495497
href: clientapi/reference/formcontext-ui-formselector/navigate.md
498+
- name: setVisible
499+
href: clientapi/reference/formcontext-ui-formselector/setVisible.md
496500
- name: formContext.ui.navigation
497501
href: clientapi/reference/formcontext-ui-navigation.md
498502
items:

powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-ui-formSelector.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "formContext.ui.FormSelector (Client API reference) in model-driven apps| MicrosoftDocs"
33
description: "Learn about working with processes in model-driven apps using client API."
4-
ms.date: 10/31/2018
4+
ms.date: 04/21/2020
55
ms.service: powerapps
66
ms.topic: "reference"
77
applies_to: "Dynamics 365 (online)"
@@ -17,8 +17,6 @@ search.app:
1717
---
1818
# formContext.ui.formSelector (Client API reference)
1919

20-
21-
2220
The **formContext.ui.formSelector** property lets you work with form items where a form item represents a form that is available to a user because it is associated with a security role that the user is also associated to. Often there will be only one form. When more than one form is available, methods for a form item can be used to change the form the user is viewing.
2321

2422
Form Items are available through any of the following:
@@ -27,14 +25,14 @@ Form Items are available through any of the following:
2725

2826
`formItem = formContext.ui.formSelector.items.get(arg);`
2927

30-
See [Collections](collections.md)) for information about the collection methods.
28+
See [Collections](collections.md) for information about the collection methods.
3129

32-
>[!NOTE]
33-
>This collection isn't available for Dynamics 365 mobile clients (phones and tablets).
30+
> [!NOTE]
31+
> This collection isn't available for [Dynamics 365 mobile clients (phones and tablets)](https://docs.microsoft.com/dynamics365/mobile-app/overview).
3432
3533
- **formselector.getCurrentItem** method: Returns a reference to the form currently being shown. When only one form is available this method will return **null**. Example:
3634

37-
`formItem = formContext.ui.formSelector.getCurrentItem();`
35+
`formItem = formContext.ui.formSelector.getCurrentItem();`
3836

3937
## Form Item methods
4038

@@ -44,6 +42,8 @@ After retrieving a form item using one of the above ways, use the following meth
4442
|--|--|
4543
|[getId](formcontext-ui-formselector/getId.md)|[!INCLUDE[formcontext-ui-formselector/includes/getId-description.md](formcontext-ui-formselector/includes/getId-description.md)]|
4644
|[getLabel](formcontext-ui-formselector/getLabel.md)|[!INCLUDE[formcontext-ui-formselector/includes/getLabel-description.md](formcontext-ui-formselector/includes/getLabel-description.md)]|
45+
|[getVisible](formcontext-ui-formselector/getVisible.md)|[!INCLUDE[formcontext-ui-formselector/includes/getVisible-description.md](formcontext-ui-formselector/includes/getVisible-description.md)]|
4746
|[navigate](formcontext-ui-formselector/navigate.md)|[!INCLUDE[formcontext-ui-formselector/includes/navigate-description.md](formcontext-ui-formselector/includes/navigate-description.md)]|
47+
|[setVisible](formcontext-ui-formselector/setVisible.md)|[!INCLUDE[formcontext-ui-formselector/includes/setVisible-description.md](formcontext-ui-formselector/includes/setVisible-description.md)]|
4848

4949

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
title: "getVisible (Client API reference) in model-driven apps| MicrosoftDocs"
3+
ms.date: 04/21/2020
4+
ms.service: powerapps
5+
ms.topic: "reference"
6+
ms.assetid: c44ca2a7-e1e0-40fc-a7a4-5ae97eacc204
7+
author: "KumarVivek"
8+
ms.author: "kvivek"
9+
manager: "annbe"
10+
search.audienceType:
11+
- developer
12+
search.app:
13+
- PowerApps
14+
- D365CE
15+
---
16+
# getVisible (Client API reference)
17+
18+
[!INCLUDE[./includes/getVisible-description.md](./includes/getVisible-description.md)]
19+
20+
21+
## Syntax
22+
23+
`formItem.getVisible();`
24+
25+
## Return Value
26+
27+
**Type**: Boolean.
28+
29+
**Description**: true if the form is visible; false otherwise.
30+
31+
### Related topics
32+
33+
[setVisible](setVisible.md)
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Returns a value that indicates whether the form is currently visible.
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Sets a value that indicates whether the form is visible.
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title: "setVisible (Client API reference) in model-driven apps| MicrosoftDocs"
3+
ms.date: 04/21/2020
4+
ms.service: powerapps
5+
ms.topic: "reference"
6+
ms.assetid: 21368fac-d4bc-4f75-8a9c-cce098fa0b45
7+
author: "KumarVivek"
8+
ms.author: "kvivek"
9+
manager: "annbe"
10+
search.audienceType:
11+
- developer
12+
search.app:
13+
- PowerApps
14+
- D365CE
15+
---
16+
# setVisible (Client API reference)
17+
18+
[!INCLUDE[./includes/setVisible-description.md](./includes/setVisible-description.md)]
19+
20+
## Syntax
21+
22+
`formItem.setVisible(bool);`
23+
24+
## Parameter
25+
26+
|Name|Type|Required|Description|
27+
|--|--|--|--|
28+
|bool|Boolean|Yes|Specify **true** to show the form; **false** to hide the form.|
29+
30+
### Related topics
31+
32+
[getVisible](getVisible.md)

powerapps-docs/maker/canvas-apps/share-app.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -121,6 +121,7 @@ If the group is not security enabled, you can enable it enable it using PowerShe
121121

122122
> [!NOTE]
123123
> You must be the owner of the Office 365 group to enable security.
124+
> Setting SecurityEnabled property to *true* does not affect how Power Apps and Office 365 features work. This command is required as SecurityEnabled property is set to *false* by default when creating Office 365 Groups outside of Azure AD.
124125
125126
After a while, you can discover this group in the Power Apps sharing panel and share apps with this group.
126127

powerapps-docs/maker/model-driven-apps/add-move-or-delete-sections-on-form.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,8 @@ To add sections to a form, use the **Components** pane.
3333
> ![](media/FormDesignerComponentsLayout.png "Layout components")
3434
3535
> [!NOTE]
36-
> Sections can only be added on main forms and quick view forms. More information: [Form types](types-forms.md)
36+
> Sections can only be added on main forms and quick view forms. More information: [Form types](types-forms.md).
37+
In Unified Interface, empty sections will not render in runtime and will be automatically hidden.
3738

3839
### Add sections to a form using drag and drop
3940
> [!NOTE]

powerapps-docs/whats-new.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: powerapps
77
ms.topic: conceptual
88
ms.custom:
99
ms.reviewer:
10-
ms.date: 02/18/2020
10+
ms.date: 04/21/2020
1111
ms.author: kvivek
1212
search.audienceType:
1313
- maker
@@ -36,9 +36,7 @@ To know more about how to browse information in the weekly release notes, read t
3636
3737
## Release plan
3838

39-
For information about new features releasing over the next few months that you can use for planning, see:
40-
- [2019 release wave 2 plan](https://docs.microsoft.com/power-platform-release-plan/2019wave2/microsoft-powerapps/planned-features)
41-
- [2020 release wave 1 plan](https://docs.microsoft.com/power-platform-release-plan/2020wave1/microsoft-powerapps/planned-features)
39+
For information about new features releasing over the next few months that you can use for planning, see [2020 release wave 1 plan](https://docs.microsoft.com/power-platform-release-plan/2020wave1/microsoft-powerapps/planned-features)
4240

4341
## Known limitations
4442

0 commit comments

Comments
 (0)