SOLVED

Outlook: Appointment: Scheduling Assistent: Manuell changed times does not affect final appointment

%3CLINGO-SUB%20id%3D%22lingo-sub-222096%22%20slang%3D%22en-US%22%3EOutlook%3A%20Appointment%3A%20Scheduling%20Assistent%3A%20Manuell%20changed%20times%20does%20not%20affect%20final%20appointment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-222096%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethe%20following%20occurs%20after%20the%20last%20update%20of%20Office%202016%2F365%3C%2FP%3E%3COL%3E%3CLI%3ECreate%20a%20new%20appointment%3C%2FLI%3E%3CLI%3ESwitch%20to%20%22Scheduling%20Assistant%22%3C%2FLI%3E%3CLI%3EAt%20the%20bottom%20of%20the%20view%20change%20either%20%22Start%20time%22%20or%20%22End%20time%22manually%22%3C%2FLI%3E%3CLI%3ELeave%20either%20by%20mouse%20click%20or%20bei%20using%20the%20TAB-key%3C%2FLI%3E%3C%2FOL%3E%3CP%3EObserve%20the%20following%3A%3C%2FP%3E%3CUL%3E%3CLI%3EIf%20you%20save%20or%20send%20the%20appointment%20the%20new%20times%20will%20not%20be%20effective%3C%2FLI%3E%3CLI%3EAt%20the%20%22Scheduling%20Assistant%22%20the%20vertical%20lines%20indicating%20start%20and%20end%20of%20the%20appointment%20will%20also%20not%20change%3C%2FLI%3E%3CLI%3EIf%20you%20switch%20back%20to%20%22Appointment%22%20also%20the%20original%20times%20will%20be%20displayed.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EWe%20are%20on%20version%201803%20build%209126.2259%20ctr%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20looking%20forward%20for%20your%20replies.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-222096%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECalendar%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECalendar%20Booking%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%202016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%20for%20Windows%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283923%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%3A%20Appointment%3A%20Scheduling%20Assistent%3A%20Manuell%20changed%20times%20does%20not%20affect%20final%20appointm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283923%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20news%2C%20will%20be%20fixed%20with%20build%201808.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-222906%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%3A%20Appointment%3A%20Scheduling%20Assistent%3A%20Manuell%20changed%20times%20does%20not%20affect%20final%20appointm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-222906%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F168109%22%20target%3D%22_blank%22%3E%40Bernhard%20Rogge%3C%2FA%3E%26nbsp%3Bas%20I%20mentioned%20above%2C%20if%20you%20can%20reliably%20reproduce%20it%20open%20a%20support%20case%2C%20so%20that%20the%20team%20can%20investigate%20and%20escalate%20to%20the%20devs%20if%20needed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-222442%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%3A%20Appointment%3A%20Scheduling%20Assistent%3A%20Manuell%20changed%20times%20does%20not%20affect%20final%20appointm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-222442%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Vasil%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eas%20recommended%20I%20started%20Outlook%20safe%20and%20manually%20set%20active%20Add-Ins%20to%20inaktive.%20After%20a%20restart%20of%20Outlook%26nbsp%3Band%20all%20add-ins%20inaktive%20unfortunately%26nbsp%3Bsame%20behaviour.%20I%20attach%20the%20Screenshot%20for%20the%20Add-Ins%3C%2FP%3E%3CP%3EMy%20system%20is%20running%20with%20Windows%207%20Enterprise%20(Build%207601%2C%20SP1)%20in%20an%20enterprise%20environment%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-222243%22%20slang%3D%22en-US%22%3ERe%3A%20Outlook%3A%20Appointment%3A%20Scheduling%20Assistent%3A%20Manuell%20changed%20times%20does%20not%20affect%20final%20appointm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-222243%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20on%20the%20same%20build%2C%20but%20not%20able%20to%20reproduce%20this.%20Changing%20the%20start%2Fend%20time%20from%20the%20Scheduling%20assistant%20tab%20updates%20the%20vertical%20indicator%20immediately%20and%20pressing%20the%20send%20button%20creates%20the%20meeting%20request%20with%20the%20selected%20time.%20Perhaps%20you%20have%20some%20add-in%20interfering%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20any%20case%2C%20if%20you%20can%20reliably%20reproduce%20this%2C%20open%20a%20support%20ticket.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hello all,

 

the following occurs after the last update of Office 2016/365

  1. Create a new appointment
  2. Switch to "Scheduling Assistant"
  3. At the bottom of the view change either "Start time" or "End time"manually"
  4. Leave either by mouse click or bei using the TAB-key

Observe the following:

  • If you save or send the appointment the new times will not be effective
  • At the "Scheduling Assistant" the vertical lines indicating start and end of the appointment will also not change
  • If you switch back to "Appointment" also the original times will be displayed.

We are on version 1803 build 9126.2259 ctr

 

I'm looking forward for your replies.

4 Replies
Highlighted

I'm on the same build, but not able to reproduce this. Changing the start/end time from the Scheduling assistant tab updates the vertical indicator immediately and pressing the send button creates the meeting request with the selected time. Perhaps you have some add-in interfering?

 

In any case, if you can reliably reproduce this, open a support ticket.

Highlighted

Hello Vasil,

 

as recommended I started Outlook safe and manually set active Add-Ins to inaktive. After a restart of Outlook and all add-ins inaktive unfortunately same behaviour. I attach the Screenshot for the Add-Ins

My system is running with Windows 7 Enterprise (Build 7601, SP1) in an enterprise environment

Highlighted
Best Response confirmed by Bernhard Rogge (Occasional Contributor)
Solution

@Bernhard Rogge as I mentioned above, if you can reliably reproduce it open a support case, so that the team can investigate and escalate to the devs if needed.

Highlighted