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.
