Event Move bug....

5 posts, 0 answers
  1. Bloodhound
    Bloodhound avatar
    25 posts
    Member since:
    Aug 2012

    Posted 16 Oct 2007 Link to this post

    If I drag an appointment on my calendar to say 11:30pm, and the appointment is 3 hours log, I would expect it to put the appointment at 11:30pm, and show the little arrow at the the bottom of the appointment that when clicked would take me to the next day.  That is how it worked prior the service pack.  Now what happens is that it takes the appointment that is on the schedule BEFORE the one I am moving and puts it at 11:30pm.  Looks like maybe the index is off by 1 in the move logic.
  2. Bloodhound
    Bloodhound avatar
    25 posts
    Member since:
    Aug 2012

    Posted 16 Oct 2007 Link to this post

    If I move appointments between 2 difference resources the same problem occurs....
  3. Carlo DiCelico
    Carlo DiCelico avatar
    15 posts
    Member since:
    Sep 2007

    Posted 16 Oct 2007 Link to this post

    Yes, I tried it and this does the same thing to me, as well. Instead of "spilling over" into the next day, it skips a whole day. Definitely looks like an off by one error.
  4. Bloodhound
    Bloodhound avatar
    25 posts
    Member since:
    Aug 2012

    Posted 16 Oct 2007 Link to this post

    Client side everything looks fine, but if you look at the server side event, the appointment object is not the one that I was updating.  It is always the first appointment for the resource I was moving from. 
  5. Bloodhound
    Bloodhound avatar
    25 posts
    Member since:
    Aug 2012

    Posted 16 Oct 2007 Link to this post

    I figured it out.  The field that I had for th ForeignKeyField in my resource declaration did not have unique values.  Every appointment for a given resource, had the same value. 
Back to Top