Skip to content

Commit e1cd8ac

Browse files
authored
Live publish
2 parents 46887d3 + 56459c0 commit e1cd8ac

File tree

11 files changed

+143
-126
lines changed

11 files changed

+143
-126
lines changed

powerapps-docs/developer/common-data-service/org-service/entity-operations-query-data.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Query data using the Organization service (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
33
description: "Introduces the different ways to query data using Microsoft Dataverse SDK assemblies." # 115-145 characters including spaces. This abstract displays in the search result.
44
ms.custom: ""
5-
ms.date: 10/31/2018
5+
ms.date: 12/10/2020
66
ms.reviewer: "pehecke"
77
ms.service: powerapps
88
ms.topic: "article"
@@ -41,6 +41,8 @@ Both of these methods will return an <xref:Microsoft.Xrm.Sdk.EntityCollection> t
4141

4242
> [!NOTE]
4343
> To ensure best performance, each query request can return a maximum of 5000 entity records. To return larger result sets you must request additional pages.
44+
>
45+
> All filter conditions for string values are case insensitive.
4446
4547
### Null attribute values are not returned
4648

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Query Data using the Web API (Microsoft Dataverse)| Microsoft Docs"
33
description: "Read about the various ways to query Microsoft Dataverse data using the Dataverse Web API and various system query options that can be applied in these queries"
44
ms.custom: ""
5-
ms.date: 12/04/2019
5+
ms.date: 12/10/2020
66
ms.service: powerapps
77
ms.suite: ""
88
ms.tgt_pltfrm: ""
@@ -217,7 +217,9 @@ GET [Organization URI]/api/data/v9.1/accounts?$select=name,revenue
217217
|`( )`|Precedence grouping|`(contains(name,'sample') or contains(name,'test')) and revenue gt 5000`|
218218

219219
> [!NOTE]
220-
> This is a sub-set of the [11.2.5.1.1 Built-in Filter Operations](https://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html). Arithmetic operators and the comparison has operator are not supported in the Web API.
220+
> This is a sub-set of the [11.2.5.1.1 Built-in Filter Operations](https://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html). Arithmetic operators and the comparison has operator are not supported in the Web API.
221+
>
222+
> All filter conditions for string values are case insensitive.
221223
222224
<a name="bkmk_buildInQueryFunctions"></a>
223225

powerapps-docs/developer/component-framework/faq.md

Lines changed: 0 additions & 74 deletions
This file was deleted.
Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
### YamlMime:FAQ
2+
metadata:
3+
title: Power App component framework FAQs
4+
description: Get answers to frequently asked questions about Power Apps component framework.
5+
author: ghurlman
6+
ms.service: powerapps
7+
ms.search.keywords:
8+
ms.date: 12/10/2020
9+
ms.author: grhurl
10+
ms.reviewer: nabuthuk
11+
title: Power Apps component framework FAQs
12+
summary: This article provides information on frequently asked questions about Power Apps component framework.
13+
sections:
14+
- name: General
15+
questions:
16+
- question: Component changes are not reflected after the updated solution import?
17+
answer: |
18+
Update the component version (minor or patch) in the component manifest file (for example, 1.0.0 to 1.0.1).
19+
Every update in the component needs a component version bump to be reflected on the Microsoft Dataverse server.
20+
> [!NOTE]
21+
> - A new solution must be created every time if you wish to have a major version bump. Incrementing the major version number (e.g., 1.0 to 2.0) is not supported as an upgrade.
22+
> - Only three version sections are supported (i.e., MAJOR.MINOR.PATCH). These version number sections should be between 0 and 65536.
23+
24+
- question: What are the things to be considered from a performance perspective?
25+
answer: |
26+
1. If you wish to access a large chunk of data items, implement [filtering](reference/filtering.md) and [paging](reference/paging.md) methods to limit how much data should be loaded.
27+
2. Batch your network calls, and make any network calls asynchronous. Design the component in such a way that all the required information is provided with a single call.
28+
3. Design the component such that the user has to perform an action (such as clicking on a button) to initiate the loading of a specific item's data rather than making the call for each data item.
29+
4. Ensure that you clean up the resources using the [destroy](reference/control/destroy.md) function. Open network calls, connections, and event handlers need to be cleaned up to increase the performance.
30+
31+
- question: Where can I find some good examples of code components?
32+
answer: |
33+
Lots of great examples from the community are available on the [Power Apps Community Forums](https://powerusers.microsoft.com/t5/Power-Apps-Component-Framework/Community-content-sample-components-blogs-etc-Link-to-this-page/td-p/280710).
34+
35+
- question: How to use rich data types in code components such as Collections?
36+
answer: |
37+
Currently, this feature is not supported. However, there is a [JSON function](https://docs.microsoft.com/powerapps/maker/canvas-apps/functions/function-json) in canvas-apps that allows app makers to stringify their data.
38+
39+
1. Pass the collection into the JSON function.
40+
2. Pass the string representation of the collection data that is returned from the JSON function into one of the component's string properties.
41+
3. Use [JSON.parse](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse) in the component code to convert it back into a JavaScript Object.
42+
43+
- question: How can I define multiple components in a single manifest file?
44+
answer: |
45+
This is not supported at this time. Currently, you can only call dialog boxes using the [Navigation](reference/navigation.md) method in model-driven apps.
46+
47+
- question: How can I call other components from within another component?
48+
answer: |
49+
This is not supported natively by the framework. You can use one of many third-party libraries to enable this functionality in your components.
50+
51+
- question: Can I bundle font resources?
52+
answer: |
53+
Currently, font resources (files with a .ttf file extension) are not supported by the framework.
54+
55+
- question: Can I use img resource property in canvas apps?
56+
answer: |
57+
Currently, [img](manifest-schema-reference/img.md) resources are not supported in canvas apps.
58+
59+
- question: TabIndex support for components in canvas apps
60+
answer: |
61+
Currently, code components do not support `tabindex` property in canvas apps. For model-driven apps the tab assignment is assigned automatically using `tabIndex = 0`, so elements are navigated in the order they appear.
62+
63+
64+
additionalContent: |
65+
## See also
66+
67+
[Power Apps component framework API reference](reference/index.md)<br/>
68+
[Power Apps component framework overview](overview.md)

powerapps-docs/developer/component-framework/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@
4141
- name: Limitations
4242
href: limitations.md
4343
- name: FAQs
44-
href: faq.md
44+
href: faq.yml
4545
- name: Sample components
4646
items:
4747
- name: How to use the sample components?

powerapps-docs/maker/model-driven-apps/form-designer-overview.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -29,16 +29,17 @@ The new model-driven form designer provides a modern WYSIWYG authoring experienc
2929
The designer shows a real-time WYSIWYG preview (Unified Interface only) while you author a form. Changes to the form are instantly reflected in the preview, enabling you to see exactly how the form will appear to users when published. An always available property pane makes the common task of updating properties quick and easy. Updates to properties are also instantly reflected in the form preview. The columns pane with searching and filtering capabilities helps makers quickly find and add columns to the form. The components pane makes it easy to discover and use components and provide a rich end-user experience. The tree view helps visualize the hierarchy of the form’s columns and components and to quickly find and select a particular column or component on the form.
3030

3131
The form designer interface has the following areas:
32-
- Command bar – Displays available actions such as **Save**, **Publish**, **Undo**, and **Redo**.
33-
- Panes – Displays panes with specific functions
34-
- **Columns** pane to add columns to a form.
35-
- **Components** pane to add components to a form.
36-
- **Tree view** to see the hierarchy of components on the form and select them.
37-
- Form preview – Displays a real-time preview of the form as it will appear to users when published.
38-
- Property pane – Displays properties of the selected element, and also allows you to make changes.
39-
- Preview size switcher - Changes the size of the form preview helping you to see how the form will appear on various screen sizes.
40-
- Zoom slider - Zooms in or out of the form preview helping you take a closer look.
41-
- Fit to width - Quick action to fit the form preview to the available width.
32+
1. Command bar – Displays available actions such as **Save**, **Publish**, **Undo**, and **Redo**.
33+
1. Form preview – Displays a real-time preview of the form as it will appear to users when published.
34+
1. Panes – Displays panes with specific functions:
35+
- **Columns** pane to add columns to a form.
36+
- **Components** pane to add components to a form.
37+
- **Tree view** to see the hierarchy of components on the form and select them.
38+
39+
1. Property pane – Displays properties of the selected element, and also allows you to make changes.
40+
1. Preview size switcher - Changes the size of the form preview helping you to see how the form will appear on various screen sizes.
41+
1. Zoom slider - Zooms in or out of the form preview helping you take a closer look.
42+
1. Fit to width - Quick action to fit the form preview to the available width.
4243

4344
> [!div class="mx-imgBorder"]
4445
> ![Form designer layout](media/FormDesignerOverview.png "Form designer layout")
Loading

powerapps-docs/maker/portals/configure/enable-header-footer-output-caching.md

Lines changed: 3 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: sandhangitmsft
55
ms.service: powerapps
66
ms.topic: conceptual
77
ms.custom:
8-
ms.date: 11/02/2020
8+
ms.date: 12/10/2020
99
ms.author: sandhan
1010
ms.reviewer: tapanm
1111
---
@@ -30,7 +30,7 @@ For a user who upgraded to a newer version of portals, output caching is disable
3030
1. Open the [Portal Management app](configure-portal.md).
3131
2. Go to **Portals** > **Web Templates**.
3232
3. Open the Header web template.
33-
4. In the **Source** field, do the following:
33+
4. Update the code in the **Source** field:
3434
- Find the following code and update it:
3535

3636
**Existing code**
@@ -147,16 +147,8 @@ For a user who upgraded to a newer version of portals, output caching is disable
147147
1. Open the [Portal Management app](configure-portal.md).
148148
2. Go to **Portals** > **Web Templates**.
149149
3. Open the Languages Dropdown web template.
150-
4. In the **Source** field, find the following code and update it:
150+
4. In the **Source** field, find the following code, and ensure that the `language` object uses `url.substitution` attribute instead of `url`:
151151
152-
**Existing code**
153-
154-
```
155-
<a href=/{{ language.url }} title={{ language.name }} data-code={{ language.code }}>{{ language.name }}</a>
156-
```
157-
158-
**Updated code**
159-
160152
```
161153
<a href=/{{ language.url_substitution }} title={{ language.name }} data-code={{ language.code }}>{{ language.name }}</a>
162154
```

0 commit comments

Comments
 (0)