You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/mobile/offline-capabilities.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,9 +91,9 @@ For more information, see [Run business process flows offline](/power-automate/b
91
91
92
92
## Limitations
93
93
94
-
-**Qualify a lead**: When a lead created in mobile offline is qualified and when the user goes online, the business process stage shows the qualify stage. The user has to manually select **Next stage** to move to the next stage.
94
+
-**Qualify a lead** - When a lead created in mobile offline is qualified and when the user goes online, the business process stage shows the qualify stage. The user has to manually select **Next stage** to move to the next stage.
95
95
96
-
-**Grids**: Column filtering is disabled when an offline profile is set up even when there is network connectivity. The grid works with the local database and does not support custom filters.
96
+
-**Grids** - Column filtering is disabled when an offline profile is set up even when there is network connectivity. The grid works with the local database and does not support custom filters.
97
97
98
98
-**Views** are not supported for the following tables in offline mode:
99
99
@@ -117,11 +117,11 @@ For more information, see [Run business process flows offline](/power-automate/b
117
117
118
118
Any views that have linked tables (related table) that are not available offline are also not supported.
119
119
120
-
-**Advanced lookups**: The **[Advanced lookup]**(../user/lookup-field.md#advanced-lookup) functionality isn't supported in offline scenarios. When you're offline, the **Advanced lookup** button is replaced by a **Change view** dropdown list.
120
+
-**Advanced lookups** - The **[Advanced lookup]**(../user/lookup-field.md#advanced-lookup) functionality isn't supported in offline scenarios. When you're offline, the **Advanced lookup** button is replaced by a **Change view** dropdown list.
121
121
122
-
-**Add Existing on subgrids**: **Add Existing**is not supported for mobile offline for certain types of relationships. When you are offline, certain relationships such as relationships that are N:N are read only, and the **Add Existing** command is hidden on subgrids for those relationships. Even if the button is unhidden via customization, the command doesn't work in offline.
122
+
-**Add Existing on subgrids** - The **Add Existing**functionality isn't supported for mobile offline for certain types of relationships. When you are offline, certain relationships such as relationships that are N:N are read only, and the **Add Existing** command is hidden on subgrids for those relationships. Even if the button is unhidden via customization, the command doesn't work in offline.
123
123
124
-
-**Web resources**: Web resources are partially supported in offline mode. Refer to the following table for more information.
124
+
-**Web resources** - Web resources are partially supported in offline mode. Refer to the following table for more information.
125
125
126
126
|Web resource configuration |Offline support on Android and Windows|Offline support on iOS|
127
127
|-------------|---------|--------|
@@ -134,13 +134,13 @@ For more information, see [Run business process flows offline](/power-automate/b
134
134
135
135
** Accessing RESX web resources as a dependency through Client API from within a JS file is supported.
136
136
137
-
-**Calculated and rollup fields**: Calculated and rollup fields that are part of rows synced to the client aren't reevaluated by the client. The reevaluation happens on the server when the updated row is synced.
137
+
-**Calculated and rollup fields** - Calculated and rollup fields that are part of rows synced to the client aren't reevaluated by the client. The reevaluation happens on the server when the updated row is synced.
138
138
139
-
-**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.
139
+
-**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.
140
140
141
-
-**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).
141
+
-**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).
142
142
143
-
-**Appointments**: Appointments can be created or updated in Dataverse, but they aren't 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).
143
+
-**Appointments** - Appointments can be created or updated in Dataverse, but they aren't 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