Hi,
I have a problem with the appointment duration. This is how I usually
do my work.
I first create the case, then I add new activity to the case.
This is the problem:
1. I create a new case
2. I add "new activity"->"appointment" to the case
3. I choose the duration as 2 hours (for example)
4. Save and complete the appointment
5. When I resolve the case, the total duration shown in the case
resolution is 30 minutes, which makes me confused as the total duration
is supposed to be 2 hours as stated in the appointment.

For any other activities, the duration always adds up correctly. It's
only with the appointment that this bug shows. Can somebody please help
me with this problem as I have no idea what's going on?
Thank you very much.


Regards,
Erick

RE: Appointment bug? by MattNC

MattNC
Mon Jan 16 14:41:02 CST 2006

I have seen this in 3.0 installations in development environments as well.
Are you using 3.0? What build are you using? (In web UI go to help > about ms
crm. Release build is 3.0.5300.0). This may be a bug that needs to be
reported to Microsoft.)
--
Matt Wittemann
http://icu-mscrm.blogspot.com


"Erick.Haryono@gmail.com" wrote:

> Hi,
> I have a problem with the appointment duration. This is how I usually
> do my work.
> I first create the case, then I add new activity to the case.
> This is the problem:
> 1. I create a new case
> 2. I add "new activity"->"appointment" to the case
> 3. I choose the duration as 2 hours (for example)
> 4. Save and complete the appointment
> 5. When I resolve the case, the total duration shown in the case
> resolution is 30 minutes, which makes me confused as the total duration
> is supposed to be 2 hours as stated in the appointment.
>
> For any other activities, the duration always adds up correctly. It's
> only with the appointment that this bug shows. Can somebody please help
> me with this problem as I have no idea what's going on?
> Thank you very much.
>
>
> Regards,
> Erick
>
>

Re: Appointment bug? by Erick

Erick
Tue Jan 17 01:54:35 CST 2006

Hi Matt,
This is the release product id for the CRM that I'm using:
3.0.5300.0
I just want to ask, is everyone having the same problem as I have now?
Thank you.


Kind regards,
Erick


Re: Appointment bug? by Dave

Dave
Tue Jan 17 22:30:59 CST 2006

Erick,
I just duplicated this problem on the same build. Looks like a bug to
me... (But thanks, the fact that at least tasks update the resolution
time is good to know!)
Dave

-------------------------------------------------
David L. Carr, President
Visionary Software Consulting, Inc.
http://www.vscrm.com
971-327-6944

For a free, fully functional demo version of VAST, the Microsoft CRM
auditing solution, please visit
http://www.vscrm.com/vast_download_page.php


Re: Appointment bug? by Andrea

Andrea
Wed Jan 18 10:36:03 CST 2006

Hi all!!
We have the same problem in different build of CRM 3.0.
It's a bug of this release already suggested to microsoft! and probably
Microsoft won't fix it since new release.
This problem makes Customer Service unusefull....because I can solve my
cases with service appointment open!
And I risk to open a services activity, move my resources to customer and
notice that that case is already solved.
So what can we do as workaround?

Best Regards
Andrea Reggiani

Re: Appointment bug? by MattNC

MattNC
Thu Feb 02 15:09:31 CST 2006

Here's the inelegant workaround suggested to me by Microsoft: add the
actualdurationminutes field to the appointment form. You can put it on some
tab the users don't usually look at, and make it read only. Then, in the
form's OnSave event, add the following line of javascript:

crmForm.all.actualdurationminutes.DataValue =
crmForm.all.scheduleddurationminutes.DataValue;

This way, you use the scheduled date and time controls on the appointment
form, which calculates the scheduleddurationminutes. Then when you save the
appointment, or complete it, the actual duration gets updated.
--
Matt Wittemann
http://icu-mscrm.blogspot.com


"Andrea Reggiani" wrote:

> Hi all!!
> We have the same problem in different build of CRM 3.0.
> It's a bug of this release already suggested to microsoft! and probably
> Microsoft won't fix it since new release.
> This problem makes Customer Service unusefull....because I can solve my
> cases with service appointment open!
> And I risk to open a services activity, move my resources to customer and
> notice that that case is already solved.
> So what can we do as workaround?
>
> Best Regards
> Andrea Reggiani