Skip to content

Commit b8331c3

Browse files
authored
Merge pull request #8352 from MicrosoftDocs/Srihari-KnownIssues
Srihari - Known issues
2 parents 73d00c7 + fac1e54 commit b8331c3

File tree

2 files changed

+27
-1
lines changed

2 files changed

+27
-1
lines changed

powerapps-docs/maker/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,9 @@
104104
- name: Use timeline
105105
href: ../user/add-activities.md
106106
- name: Create and join a Teams meeting from an appointment
107-
href: ../user/join-teams-meeting-from-appointments.md
107+
href: ../user/join-teams-meeting-from-appointments.md
108+
- name: Known issues about activities
109+
href: ../user/known-issues-activities.md
108110
- name: Work with email
109111
items:
110112
- name: Understand the email experience
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
title: Known issues about activities
3+
description: Learn about known issues that may occur with activities in model-driven apps.
4+
author: sriharibs-msft
5+
ms.component: pa-user
6+
ms.topic: overview
7+
ms.date: 06/20/2023
8+
ms.subservice: end-user
9+
ms.author: srihas
10+
ms.reviewer: sericks
11+
ms.custom:
12+
ms.assetid:
13+
search.audienceType:
14+
- enduser
15+
---
16+
# Known issues about activities
17+
18+
Learn about known issues that may occur with activities in model-driven apps.
19+
20+
- On appointment grids, all-day appointments may show incorrect values for **Start Time** and **End Time**. This issue is limited to the grid control showing appointment records, as forms and calendar control show correct **Start Time** and **End Time** for all-day appointments.
21+
22+
To fix this issue, use the [calendar control](../maker/model-driven-apps/add-calendar-control.md) as the default control to view appointments.
23+
24+
- The process that checks for conflicts for the people and resources on an appointment is triggered only when a valid Dynamics 365 solution is installed on the environment, as this requires a few scheduling-related tables to be a part of the environment. Appointments created in an environment without a relevant Dynamics 365 solution installed have an **Open** status, rather than the **Scheduled** status. For more information on the scheduling tables and the license required, see [Restricted tables for create, update, and delete operations](../maker/data-platform/data-platform-restricted-entities.md#restricted-tables-for-create-update-and-delete-operations).

0 commit comments

Comments
 (0)