We are using CRM 2016, Version 8.1
Configuration
Service
Resource
CRM Scheduler Proposals
API Response:
Logged in user time zone is CST (UTC-5)
{{CRMInternal-Org-Api}}/v8.1/Search(AppointmentRequest=@request)/?@request={"ServiceId":"74849950-901d-ef11-9555-00155d104821","SearchWindowStart":"2024-06-28T13:00:00Z","SearchWindowEnd":"2020-06-28T23:00:00Z","Duration":150,"UserTimeZoneCode":"1","Direction":"2","NumberOfResults":10000}
"Proposals": [
{
"Start": "2024-06-28T13:30:00Z",
"End": "2024-06-28T16:00:00Z",
"SiteId": "d98fc0e3-36e8-ee11-954f-00155d103d85",
"SiteName": "TestSite",
"ProposalParties": [
{
"ResourceId": "a589ce99-3088-e911-9489-00155d835d7d",
"ResourceSpecId": "73849950-901d-ef11-9555-00155d104821",
"DisplayName": "Tes",
"EntityName": "equipment",
"EffortRequired": 1
}
]
},
{
"Start": "2024-06-28T18:30:00Z",
"End": "2024-06-28T21:00:00Z",
"SiteId": "d98fc0e3-36e8-ee11-954f-00155d103d85",
"SiteName": "TestSite",
"ProposalParties": [
{
"ResourceId": "a589ce99-3088-e911-9489-00155d835d7d",
"ResourceSpecId": "73849950-901d-ef11-9555-00155d104821",
"DisplayName": "Tes",
"EntityName": "equipment",
"EffortRequired": 1
}
]
}
]
The CRM scheduler proposals (3 slots) and API response (2 slots) don't match. The API response starts at "Start": "2024-06-28T13:30:00Z" UTC, which is 8:30 AM CST. This 30-minute difference is causing the last slot to be excluded because it falls outside the resource's working hours.