SOLVED

Is TEAMS SHIFTS export schedule now restricting to only 45 days of data?

%3CLINGO-SUB%20id%3D%22lingo-sub-2144014%22%20slang%3D%22en-US%22%3EIs%20TEAMS%20SHIFTS%20export%20schedule%20now%20restricting%20to%20only%2045%20days%20of%20data%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2144014%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20found%20out%20today%20when%20trying%20to%20export%20my%20TEAMS%20SHIFTS%20schedule%20that%20the%20period%20available%20to%20export%20is%20now%20restricted%20to%2045%20days.%20%3CU%3EIs%20this%20something%20permanent%3F%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22karlbg_0-1613588164487.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F255584iBFCE7830702BC0A6%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22karlbg_0-1613588164487.png%22%20alt%3D%22karlbg_0-1613588164487.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3BWe%20use%20SHIFTS%20for%20our%20vacation%20calendar%20and%20need%20to%20export%20the%20whole%20year%20on%20a%20regular%20basis%20to%20update%20our%20excel%20version%20that%20is%20sent%20in%20email.%20Is%20there%20another%20way%20to%20get%20over%20this%2045%20days%20restriction%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2144014%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2144267%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20TEAMS%20SHIFTS%20export%20schedule%20now%20restricting%20to%20only%2045%20days%20of%20data%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2144267%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F969987%22%20target%3D%22_blank%22%3E%40karlbg%3C%2FA%3E%26nbsp%3BHi%2C%20I%20don't%20use%20Shifts%20(or%20work%20with%20it)%20but%20don't%20think%20the%2045-day%20limit%20is%20something%20new.%20Are%20you%20saying%20you%20previously%20been%20able%20to%20export%20schedules%20for%20a%20longer%20time%20period%3F%20You%20can%20probably%20use%20the%20Graph%20API%20for%20Shifts.%20But%20can't%20say%20more%20than%20that%20as%20I%20haven't%20used%20it%20myself.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2146029%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20TEAMS%20SHIFTS%20export%20schedule%20now%20restricting%20to%20only%2045%20days%20of%20data%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2146029%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F551905%22%20target%3D%22_blank%22%3E%40ChristianBergstrom%3C%2FA%3E%26nbsp%3BI've%20been%20able%20to%20export%20the%20SHIFTS%20schedule%20(whole%20year%20period)%20for%20over%20a%20year%20until%20a%20few%20days%20ago.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20understand%20that%20MS%20is%20constantly%20changing%20and%20improving%20TEAMS%20but%20this%20one%20is%20a%20huge%20drawback%20for%20us.%20Can't%20really%20understand%20the%20limitation%20as%20the%20data%20is%20readily%20available%20on%20the%20screen%20but%20not%20for%20export.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20someone%20could%20provide%20the%20rationale%20behind%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20reply.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2158752%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20TEAMS%20SHIFTS%20export%20schedule%20now%20restricting%20to%20only%2045%20days%20of%20data%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2158752%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F969987%22%20target%3D%22_blank%22%3E%40karlbg%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F551905%22%20target%3D%22_blank%22%3E%40ChristianBergstrom%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20in%20the%20same%20situation%2C%20we%20have%20been%20downloading%20a%20full%20year%20at%20a%20time%20to%20review%20the%20working%20patterns.%20Now%20having%20to%20download%20in%2045%20day%20chunks%20which%20is%20very%20time%20consuming.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20can%20someone%20update%20as%20to%20if%20this%20is%20a%20temporary%20issue%20%3F%3C%2FP%3E%3CP%3EOr%20if%20there%20is%20another%20way%20to%20download%20the%20shifts%20into%20a%20full%20year%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ENadine%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2158761%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20TEAMS%20SHIFTS%20export%20schedule%20now%20restricting%20to%20only%2045%20days%20of%20data%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2158761%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F969987%22%20target%3D%22_blank%22%3E%40karlbg%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20Have%20been%20using%20teams%20shifts%20for%20almost%20a%20year%20and%20exporting%20the%20data%20for%20a%20full%20calendar%20year%20to%20calculate%20time%20off%20and%20Holidays.%3C%2FP%3E%3CP%3Ethe%20limit%20to%2045%20days%20has%20only%20been%20turned%20on%20this%20week.%3C%2FP%3E%3CP%3EThis%20limit%20is%20very%20unhelpful.%3C%2FP%3E%3CP%3EIs%20it%20possible%20to%20return%20to%20the%20old%20option.%20ASAP%20please%20as%20we%20near%20year%20end%20this%20information%20is%20vital%20for%20all%20our%20business%20to%20ensure%20correct%20time%20off%20is%20calculated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20look%20forward%20to%20your%20replies.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2158767%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20TEAMS%20SHIFTS%20export%20schedule%20now%20restricting%20to%20only%2045%20days%20of%20data%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2158767%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F551905%22%20target%3D%22_blank%22%3E%40ChristianBergstrom%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20Have%20been%20using%20teams%20shifts%20for%20almost%20a%20year%20and%20exporting%20the%20data%20for%20a%20full%20calendar%20year%20to%20calculate%20time%20off%20and%20Holidays.%3C%2FP%3E%3CP%3Ethe%20limit%20to%2045%20days%20has%20only%20been%20turned%20on%20this%20week.%3C%2FP%3E%3CP%3EThis%20limit%20is%20very%20unhelpful.%3C%2FP%3E%3CP%3EIs%20it%20possible%20to%20return%20to%20the%20old%20option.%20ASAP%20please%20as%20we%20near%20year%20end%20this%20information%20is%20vital%20for%20all%20our%20business%20to%20ensure%20correct%20time%20off%20is%20calculated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20look%20forward%20to%20your%20replies.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2158814%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20TEAMS%20SHIFTS%20export%20schedule%20now%20restricting%20to%20only%2045%20days%20of%20data%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2158814%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F729077%22%20target%3D%22_blank%22%3E%40Mbeeson%3C%2FA%3E%26nbsp%3BHi%2C%20you%20should%20reach%20out%20to%20the%20official%20support%20for%20a%20proper%20answer%20to%20what%20you're%20experiencing%20with%20the%20decrease%20of%20export%20time%20period.%20Your%20IT%20admin%20can%20assist%20with%20that.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2173202%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20TEAMS%20SHIFTS%20export%20schedule%20now%20restricting%20to%20only%2045%20days%20of%20data%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2173202%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F969987%22%20target%3D%22_blank%22%3E%40karlbg%3C%2FA%3Epreviously%20we%20were%20able%20to%20extract%2012%20months%20of%20data%20from%20MS%20Shifts%2C%20on%20Thursday%2018th%202021%20this%20seems%20to%20have%20been%20now%20been%20reduced%20to%2045%20days%20which%20is%20a%20issue%20for%20us%20as%20we%20would%20need%20need%20to%20export%20data%20monthly%20across%20a%20large%20amount%20of%20teams.%20I%20have%20lodged%20a%20ticket%20to%20support%20in%20relation%20to%20matter%20also.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2174335%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20TEAMS%20SHIFTS%20export%20schedule%20now%20restricting%20to%20only%2045%20days%20of%20data%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2174335%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F981554%22%20target%3D%22_blank%22%3E%40ChristopherSchmidt%3C%2FA%3E%26nbsp%3BThanks.%20I've%20done%20the%20same%20by%20lodging%20a%20ticket%20to%20our%20IT%20support.%20Will%20ask%20them%20to%20bring%20it%20to%20MS%20if%20needed.%20Maybe%20this%20limitation%20can%20be%20changed%20by%20an%20admin%20internally.%20Fingers%20crossed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2335403%22%20slang%3D%22en-US%22%3ERe%3A%20Is%20TEAMS%20SHIFTS%20export%20schedule%20now%20restricting%20to%20only%2045%20days%20of%20data%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2335403%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F969987%22%20target%3D%22_blank%22%3E%40karlbg%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20did%20you%20get%20an%20answer%20on%20this%3F%20This%20new%20restriction%20has%20really%20screwed%20my%20shift%2Fvacation%20planning.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi everyone,

 

Just found out today when trying to export my TEAMS SHIFTS schedule that the period available to export is now restricted to 45 days. Is this something permanent?

 

karlbg_0-1613588164487.png

 We use SHIFTS for our vacation calendar and need to export the whole year on a regular basis to update our excel version that is sent in email. Is there another way to get over this 45 days restriction?

 

Thanks.

 

12 Replies

@karlbg Hi, I don't use Shifts (or work with it) but don't think the 45-day limit is something new. Are you saying you previously been able to export schedules for a longer time period? You can probably use the Graph API for Shifts. But can't say more than that as I haven't used it myself.

@ChristianBergstrom I've been able to export the SHIFTS schedule (whole year period) for over a year until a few days ago.

 

I understand that MS is constantly changing and improving TEAMS but this one is a huge drawback for us. Can't really understand the limitation as the data is readily available on the screen but not for export.

 

If someone could provide the rationale behind this.

 

Thanks for your reply.

Hi @karlbg @ChristianBergstrom 

 

We are in the same situation, we have been downloading a full year at a time to review the working patterns. Now having to download in 45 day chunks which is very time consuming.

 

Please can someone update as to if this is a temporary issue ?

Or if there is another way to download the shifts into a full year?

 

Thanks

Nadine 

@karlbg 

 

We Have been using teams shifts for almost a year and exporting the data for a full calendar year to calculate time off and Holidays.

the limit to 45 days has only been turned on this week.

This limit is very unhelpful.

Is it possible to return to the old option. ASAP please as we near year end this information is vital for all our business to ensure correct time off is calculated.

 

I look forward to your replies.

@ChristianBergstrom 

We Have been using teams shifts for almost a year and exporting the data for a full calendar year to calculate time off and Holidays.

the limit to 45 days has only been turned on this week.

This limit is very unhelpful.

Is it possible to return to the old option. ASAP please as we near year end this information is vital for all our business to ensure correct time off is calculated.

 

I look forward to your replies.

@Mbeeson Hi, you should reach out to the official support for a proper answer to what you're experiencing with the decrease of export time period. Your IT admin can assist with that.

@karlbgpreviously we were able to extract 12 months of data from MS Shifts, on Thursday 18th 2021 this seems to have been now been reduced to 45 days which is a issue for us as we would need need to export data monthly across a large amount of teams. I have lodged a ticket to support in relation to matter also.

@ChristopherSchmidt Thanks. I've done the same by lodging a ticket to our IT support. Will ask them to bring it to MS if needed. Maybe this limitation can be changed by an admin internally. Fingers crossed.

@karlbg 

Hi did you get an answer on this? This new restriction has really screwed my shift/vacation planning.

@GaryGoals 

The 45 day limit has not been helpfull.

They are still looking into it.

we are having to do month by month into a spreadsheet and using lookup.

 

Hopefully it will be returned to a whole year for export or a holiday etc calculation added to shifts.

 

best response confirmed by ThereseSolimeno (Microsoft)
Solution

@GaryGoals The official response we had from MS is that is this now by design and if we want the feature back to submit the request through https://microsoftteams.uservoice.com/. 

Thank you for updating this conversation. Sorry to hear about the 45-day now being by design.