Book a room template app - only shows first available room

[lonelySiren]

This used to work in the past, but I'm only getting the first room now. 

I'm reusing the code from the Book a room app with the Office365.FindMeetingTimesV2 call to get all available rooms at a certain time. The Availability property is only loaded for the first hit. Thus I only get one room available at a time. I checked the behavious on the template app again and it seems to have changed. 

Anyone else noticed this behavior? 

Suggestions to get all the rooms that are available?

[LEARN_IT]

Thanks God I'm not the only one. I thought the issue was at my end. Please keep us update about this. All day long trying to resolve this problem.

[Anonymous]

Im going to post my solution on my thread, it aint pretty but it worked. 
https://powerusers.microsoft.com/t5/Building-Power-Apps/Office365outlook-findavailablemeetings-sudde...

[Anonymous]

Did you figure it out?

So ForAlls dont like ClearCollects, so you'll need to throw a clear at the top and just do a collect. 

You'll need to not use variables for the email addresses, but maybe you are looping through your AllRooms or AllRoomsConnector?, and using "Address" as the required attendees? I am not comfortable writing the code for you - we appear to be in different areas (noting the , instead of ; )because we are in different regions they work a little different as far as im aware, however the premise should be the same.. Good Luck!

[Samuel-SH]

no i didn't! Microsoft looked at your code and said they didn't get it running in my enviroment. But they are working on a fix or other workaround. So i hope it will be soon. Thx anyway

[StaffanNelemans]

Same problem here, hopefully it is fixed fast

[Samuel-SH]

just got this info from microsoft support:

I wanted to inform that this issue was related to a reversion in the FindMeetingTimes API. The fix will be deploying this afternoon and should be fully deployed by this afternoon. I will update you again once it’s been deployed and would kindly ask you to test it.

Regarding the workaround, since the issue was related with the FindMeetingTimes API, me and my colleagues tested and couldn’t get the workaround to work since the function would always retrieve the wrong information even with a ForAll() loop.

[JazzGuitarGuy]

Fantastic news... thanks for the info Samuel.

[LastResort]

Here's a workaround for existing out-the-box template code:

Thanks to Tia for clues for fix: https://powerusers.microsoft.com/t5/Building-Power-Apps/Office365outlook-findavailablemeetings-sudde...

Replace existing equivalent lines of code in both AdjustDateScreen ButtonSaveChanges OnSelect and in RoomSelectScreen OnVisible with this

Clear(MeetingGroupV1);

ForAll(AllRooms,
Collect(MeetingGroupV1,AddColumns(Office365.FindMeetingTimes({RequiredAttendees: 'Address', IsOrganizerOptional: false,
Start: StartDateTimeUTC, End: EndDateTimeUTC, MeetingDuration: DateDiff(StartDateTime, EndDateTime, Minutes),
MinimumAttendeePercentage: "1", ActivityDomain: "Unrestricted"}).MeetingTimeSuggestions,"TheData",AttendeeAvailability)));

Clear(MeetingData2);
ForAll(MeetingGroupV1,
Collect(MeetingData2, TheData));

ClearCollect(MeetingData3, Concat(Filter(MeetingData2, Availability = "Free"), Attendee.EmailAddress.Address, ","));
ClearCollect(MeetingData4, Split(First(MeetingData3).Value, ","));
ClearCollect(AvailableRoomEmailName, AddColumns(RenameColumns(MeetingData4, "Result", "Email"), "Name", LookUp(AllRooms, Email = Address).Name));

Basically it calls the FindMeetingTimes for each room in the AllRooms collection and collates them together.

Best of luck and I also see MS are going to do a fix anyway.

[LEARN_IT]

This Works for me. 

Thanks LastResort. Great JOb

[bwert]

Will this fix be deployed to all tenants or just yours because you opened the support case? I don't see any Service Health messages about this nor any posting anywhere that Microsoft is deploying a fix for this. I also could not get the workaround code working. It sometimes displayed the rooms and other times it did not. Just wondering if I need to open a support case with Microsoft to get them to deploy the fix to my tenant?