Skip to content

Commit fb61723

Browse files
committed
Merge branch 'mints-troubleshoot-tah' of https://github.com/MicrosoftDocs/powerapps-docs-pr into mints-troubleshoot-tah
2 parents ae59234 + b242fc6 commit fb61723

File tree

3 files changed

+12
-9
lines changed

3 files changed

+12
-9
lines changed

powerapps-docs/maker/canvas-apps/service-request-support.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -52,12 +52,13 @@ The following examples show app bugs and how to describe them to app owners. You
5252
- Expected behavior: Invoices created by the user are displayed.
5353
- Actual behavior: No invoices are shown.
5454

55-
1. Model-driven app doesn't show invoices
56-
1. Sign in to the Contoso app in a particular environment.
57-
1. On the **Dashboard** page, select **Invoices** on the site map.
58-
1. On the **Invoices** page, set the view to **My active invoices**. The list of invoices are displayed.
59-
- Expected behavior: Invoices created by the user are displayed.
60-
- Actual behavior: No invoices are shown.
55+
#### Model-driven app doesn't show invoices
56+
57+
1. Sign in to the Contoso app in your environment.
58+
1. On the **Dashboard** page, select **Invoices** on the site map.
59+
1. On the **Invoices** page, set the view to **My active invoices**. The list of invoices are displayed.
60+
- Expected behavior: Invoices created by the user are displayed.
61+
- Actual behavior: No invoices are shown.
6162

6263
Bugs can have great variance because features, user interfaces, and tables are specific to an app and organization, making the cause of bugs different for everyone. For example, **invoice** isn't a built-in table in Power Apps. There isn't a specialized feature in canvas apps for filtering records by a certain user, therefore the app maker must write Power Fx expressions or configure data connectors. Similarly, the maker must configure **Views** in model-driven apps to display desired records.
6364

powerapps-docs/maker/canvas-apps/working-with-experimental-preview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,8 +31,8 @@ At each stage, the number of people who use the feature increases, helping us to
3131

3232
In short, the stages are:
3333
- **New:** These features are new and generally available (GA), fully supported, and documented. Generally these features are on by default for new apps, but might take time to deploy everywhere. Enable for existing apps on your own schedule.
34-
- **Preview:** These features are almost done and will be **New** soon. But at this stage there still might be some changes made. This stage is the last opportunity for feedback. These features are generally turned off by default and are documented. These features aren't GA, shouldn't be used in production, and are covered by the [Preview terms of service](https://powerplatform.microsoft.com/legaldocs/supp-powerplatform-preview/).
35-
- **Experimental:** An early stage "Preview," these features truly are experiments and might never reach GA. We're assessing the value proposition and design of the feature, and the feature might radically change or be removed completely at any time. These features are off by default and aren't generally documented. These features aren't GA, shouldn't be used in production, and are covered by the [Preview terms of service](https://powerplatform.microsoft.com/legaldocs/supp-powerplatform-preview/).
34+
- **Preview:** These features are almost done and will be **New** soon. But at this stage there still might be some changes made. This stage is the last opportunity for feedback. These features are generally turned off by default and are documented. These features aren't GA, shouldn't be used in production, and are covered by the [Preview terms of service](https://go.microsoft.com/fwlink/?linkid=2189520).
35+
- **Experimental:** An early stage "Preview," these features truly are experiments and might never reach GA. We're assessing the value proposition and design of the feature, and the feature might radically change or be removed completely at any time. These features are off by default and aren't generally documented. These features aren't GA, shouldn't be used in production, and are covered by the [Preview terms of service](https://go.microsoft.com/fwlink/?linkid=2189520).
3636
- **Retired:** These features are GA features but are on their way to being removed from the product. They're still fully supported and document, but we either have a new, better way to do the same thing or usage is low. Disable for existing apps on your own schedule. Generally, these features are off by default.
3737

3838
How long does a feature remain in each stage? It varies from feature to feature. We look at many factors, including the number of apps that use the feature, the number of issues reported, and how urgently the feature is needed. Features can remain in a stage for weeks to many months. We might also skip some stages if we don't believe it would be helpful.

powerapps-docs/mobile/offline-limitations.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Mobile offline limitations for model-driven apps
33
description: Mobile offline capabilities and limitations for Power Apps and Dynamics 365 phones and tablets app
44
ms.custom:
5-
ms.date: 06/18/2024
5+
ms.date: 07/03/2024
66
ms.reviewer: sericks
77
ms.suite:
88
ms.tgt_pltfrm:
@@ -118,6 +118,8 @@ These tables and corresponding commands are available in offline mode.
118118

119119
- **Mapped fields** - When you run an app in offline mode, mapped fields aren’t prepopulated when you create a new record from a table that has fields mapped to another table.
120120

121+
- **Lookup fields** - The value of a lookup field may not be updated in a form or grid when the display name of the lookup item is updated.
122+
121123
- **Filter operations** - Not all filter operations are supported in offline mode. For a full list of supported operators, see [Supported Filter Operations Per Attribute Type in Mobile Offline using FetchXML](/power-apps/developer/model-driven-apps/clientapi/reference/xrm-webapi/retrievemultiplerecords#supported-filter-operations-per-attribute-type-in-mobile-offline-using-fetchxml).
122124

123125
- **Appointments** - Appointments can be created or updated in Dataverse, but they're not sent to recipients with server-side synchronization. For more information, see [Appointment table/entity reference](../developer/data-platform/reference/entities/appointment.md) and [Server-side synchronization tables](../developer/data-platform/server-side-synchronization-entities.md).

0 commit comments

Comments
 (0)