Update known-issues-activities.md

sericks007 · web-flow · commit 99aa0cd13695 · 2023-06-20T07:12:04.000-05:00
diff --git a/powerapps-docs/user/known-issues-activities.md b/powerapps-docs/user/known-issues-activities.md
@@ -21,4 +21,4 @@ Learn about known issues that may occur with activities in model-driven apps.
   
   To fix this issue, use the [calendar control](../maker/model-driven-apps/add-calendar-control.md) as the default control to view appointments.
 
-- Conflict-check for the people and resources on an appointment is triggered only with a valid Dynamics 365 solution 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 the relevant Dynamics 365 solution installed will have **Open** status and not **Scheduled**. 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).
+- Conflict-check for the people and resources on an appointment is triggered only with a valid Dynamics 365 solution 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 the 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).

Original file line number	Diff line number	Diff line change
`@@ -21,4 +21,4 @@ Learn about known issues that may occur with activities in model-driven apps.`
`21`	`21`
`22`	`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`	`23`
`24`		-- Conflict-check for the people and resources on an appointment is triggered only with a valid Dynamics 365 solution 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 the relevant Dynamics 365 solution installed will have Open status and not Scheduled. 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).
	`24`	+- Conflict-check for the people and resources on an appointment is triggered only with a valid Dynamics 365 solution 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 the 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).