Export Data Displays Client Name Within Service Name
We encountered significant problems with Microsoft Bookings from late November through mid-December. https://techcommunity.microsoft.com/t5/microsoft-bookings/bookings-is-acting-up-since-the-end-of-november-lot-of-issues/m-p/4007098#M6546 The issues were resolved in mid-December. However, following the resolution, we have observed a problem with our Microsoft Bookings Exportation (.tsv) feature. Before mid-December, the client's name, along with the service name, was visible in the Outlook Calendar, providing a convenient overview of appointment information without the need to click for full details. Unfortunately, since mid-December, this information is also displaying on the Microsoft Bookings side. Consequently, this is impacting all our exports and data derived from this solution. Accurately compiling the data has become a significant challenge and is nearly impossible, resulting in errors on reports, given that the client's name is now visible across all services. Could you kindly investigate and address this issue exclusively on the MS Bookings data side? We would like the client's name to continue appearing on the Outlook calendar while resolving the unintended display on the Microsoft Bookings side. Thank you!Export tracking data with Graph API
We are currently working on exporting data from MS Bookings pages using the Microsoft Graph API. We are having difficulties gathering "Tracking Data" information. According to your documentation, it is possible to export data manually that included specific field (see this documentation https://learn.microsoft.com/en-us/microsoft-365/bookings/reporting-info?view=o365-worldwide), but some of the fields (tracking data) included in the improved report section are not available if extracted automatically with Microsoft Graph. Is there a possibility to export the Tracking Data automatically through a script, rather than accessing each pages and processing manually?TSV Export Unusable state in Bookings
★If there is a more appropriate forum for this (particularly a Japanese Bookings support discussion?) please redirect me. ★I can provide the original TSV file only to Microsoft employees due to it containing customer information. All screenshots in this thread will be censored to protect client info. We use bookings to keep track of seminars we teach. It has mostly been successful, but reporting all has to be done very manually. The TSV files provided for our Japanese language using environment are very clearly corrupted and not behaving as intended. Please reference the attached screenshot. I will go over each column with my feedback on what seems to be happening (this is consistent and has been for 10 months, but has been low priority for us and I have not had a chance to report it yet) Column A: As far as I can tell, the Date Time column is the only one working as intended. Column B: It seems that the system used for generating the TSV is unable to process Japanese script. Completely unrelated (Chinese?) text or random symbols are included in place of the names. I have left part of one name entered in English uncensored to show that it is likely a language problem. "Minami" was accurate. Additionally, email addresses are shifted over for some bookings, but not all. Very inconsistent bug. Column C: Because of some emails being included in Column B, only about half of the emails are available in this column. Additionally, any row with email shifted over sees phone number shifted over as well. Column 😧 Same as C. Column E appears to have not shifted over, only because we have 0 data for customer addresses. Column E: Unintelligible, not Japanese characters. Shifted over from "Staff". Column F: Unintelligible, not Japanese characters. Anything from here to the right is 100% unusable. Between the corrupted text and shifted columns, finding a single data point would take up too much time. If there are some user settings or work arounds that can fix this, I would be very grateful to hear.
Known issues with TSV export files
I have noticed a few hopefully fixable problems that currently render the exported TSV files less useful than they should be, and certainly these are issues that other users should be aware of. The files are row delimited using the LINEFEED character (ASCII character 10), and within each row the columns are delimited by the horizonatal TAB (ASCII character 9). The problem is that these characters can be embedded within an individual field as well (for example Customer Name Joe[TAB]Bloggs). When this occurs, because there are no text qualifiers, every field in the row beyond the embedded tab is pushed out by one. If a LINEFEED is embedded in a field (for example in Customer Address: 1 Microsoft Way[LINEFEED]Redmond), it creates a new line at "Redmond". Is it possible to replace the affected embedded control characters with something more benign, like SPACE (ASCII character 32) during the generation of the extract, or to use text qualifiers such as double quotes to surround affected fields? Or simply handle them at the point of entry? The file export date ranges appear to be based on the booking datetime. If there was an option to base it on the last modified date, it would open up the possibility of incremental extracts, thus hugely reducing the burden on MS's servers and everyone else who can implement incremental handling of these files. To be 100% sure all changes have been captured, the user has no alternative other than to download every single booking, every single time. It's possible, (indeed common) for customers to create bookings that are almost duplicated (say all fields except two identical). When they appear in the same extract, there seems to be no way to know which record takes precedence. If we pick the wrong record in the belief that it is the most recent, this can cause embarrassment. "What is wrong with your <&&$^%#@&^> booking system! I corrrected that!" This could be solved with by including a modified date and time in each row or some sequence number based on the time of the change. Including the selection criteria metadata in the filename would also be a big improvement eg MSBookings_mycal_20210601_20210606.tsvEvent 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.
