Event column header change in TSV export in Bookings
Seems like a column header of the TSV-export file had a change: column "Type" changed to "Event Type". In this colum you will find the values "Single" or "Group" reservations. Our staff is working with an Excel-file which uses an embedded Power Query to show them the hourly updates in the reservations and provides them with a printer-friendly report. Suddenly Friday afternoon February 19th CET the Power Query showed errors because of the name change of that column. Not sure if Microsoft gives a head up for such changes ... ? We use Power Query to split the Date Time field and filter out the group Bookings. In our case the single Bookings are the dates of closure. We chose this solution while awaiting a full adoption of group reservations in the Bookings web application. Till today this has a lot of limitations. Attached is the Excel-file we use to get the detail from our group reservation services in Bookings. Just as an example. If you put this Excel-file in c:\temp together with the BookingsReportingData.tsv file you download from your https://outlook.office.com/bookings/homepage it should give you the same detail. This is without the info from custom fields or even notes (special request) field. These fields are simply not in the TSV-file. To avoid misunderstanding with our customers we don't use custom or notes fields in our reservations services. The imported data is shown by means of 2 very simple pivot tables, reservations today and reservations next 7 days. This can be easily adapted in the power query. Upon opening the power query will update the Excel-file with the data of BookingsReportingData.tsv , which must also be placed in c:\temp. Update 13 March: new sample Excel-file "MS Bookings reservations v4.xlsx" because of 8 added columns by Microsoft.Bookings TSV export now requires start and end date selection
Seems the TSV-export functionality received an update. In the past, when clicking on the link the downloaded "BookingsReportingData.tsv" file provided 120 days of reservations, of which 60 in the past and 60 in the future. This behaviour changed Friday afternoon February 19th CET. Now users are required to make a start and end date selection prior to download. Also after closing and reopening the browser the date selection defaults to end date today. Now we have the change the instructions for our staff, as in the past they just needed to download the BookingsReportingData.tsv. Then they openend an Excel-file which ran a power query on the imported data and provided them with a printer friendly report. Now, staff has to take care they enter the correct date selection in the future or their report will be empty. Apologies, screenshot in Dutch language:New columns added in Bookings TSV-export
Seems Microsoft is speeding up developments related to the TSV-export functionality. 3 weeks ago I reported Bookings TSV export now requires start and end date selection and Event column header change in TSV export in Bookings . This morning our staff reported errors when opening our Excel-query-report, which uses the TSV-export as source file. Turns out Microsoft suddenly expanded the TSV-export file from 10 to 18 columns. Updated list of columns in BookingsReportingData.tsv = TSV export file : Date Time Customer Name Customer Email Customer Phone Customer Address Staff Service Location Duration (mins.) Pricing Type # new dd. 13 March Price # new dd. 13 March Currency # new dd. 13 March Cc Attendees # new dd. 13 March Count Signed Up Attendees Count # new dd. 13 March Text Notifications Enabled # new dd. 13 March Custom Fields # new dd. 13 March Event Type # formerly named "Type" dd. 19 February Booking Id # new dd. 13 March All in all this is good news, but I would appreciate a heads up. Now each change in TSV-export results in an interruption for our staff at the public swimming pool. It breaks down our print-reports in Excel Power Query.
