Its seems a TimeZone issue as I have set up the TimeZone of GMT +1 in Customer Service Schedule and I am working from India Timezone. But if people are working from different timezone then what needs to be configure here.
Please suggest.
Thanks
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
While creating a Case in dynamics 365. SLA's first response in duration taking a Strang duration time which is not configured anywhere in SLA items.
Below is my configuration
Steps which I have done
Below is the screen shot for reference:
FYI: It is only happening when deploying Environment specific solution (where we have SLA components). Also, once this wrong 'First Response In' time is getting expired then its working as expected for other case (which is creating after getting it expired). But if in the meantime (while this wrong First Response In duration is running/not expired) and creating any other case then its taking the same time as that wrong one taking.
Please suggest a resolution for it.
Thanks and Regards,
Kuldeep
Its seems a TimeZone issue as I have set up the TimeZone of GMT +1 in Customer Service Schedule and I am working from India Timezone. But if people are working from different timezone then what needs to be configure here.
Please suggest.
Thanks
Hi @Kuldeep Patwal ,
Dynamics 365 is currently not supported in this Microsoft Q&A platform. These are the products that are currently supported in this Microsoft Q&A platform. You may ask Dynamics 365 related questions in this community.