Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Learn about known issues that may occur with activities in model-driven apps.
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.
To fix this issue, use the calendar control as the default control to view appointments.
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.
When you use the calendar control view for appointments and navigate through time periods (like moving from Day to Week view or using the navigation arrows), selecting Edit filters and then Apply can result in duplicate Start Time and End Time filter conditions. This duplication causes appointments not to display in the view. To resolve this issue, select Edit filters, manually remove one set of the duplicated Start Time and End Time filters, and then select Apply. Alternatively, work in the grid view instead of the calendar view.
Error message
Unable to find one-to-many relationship, entity: [entity name], referencing entity: activitypartyThis transient error appears when saving records with relationships to activity parties. The root cause of the issue is that schema information about the relationship is not loaded when you save the record. The work around is to try to save the record again because the schema information will be loaded eventually. If this error occurs due to custom scripts on the page, the script developer should catch the error and retry after a short delay.