When ‘reviewing’ a previously entered visit history record under Campgrounds (one that was imported from 3.0), it adds a booking date to the visit record - today’s date. It really doesn’t matter (I’m guessing the original record didn’t have a booking date field) but it just looks a little strange to see a record from 2022 having a booking date of June 14, 2026.
Steve
Yes, the classic version didn’t have a booking date field, which seemed amiss to me. The question is how to handle this. Possibly the cleanest way would be to set the booking date to be the same as the reservation start date. That would definitely look better, and it would only be for the classic data import. The only problem with that is that the app is then introducing inaccurate data deliberately. Thoughts welcome!
I think I agree. If it has to have a date and doesn’t have one - I guess the default should be the day of arrival. in many cases for me, that would be correct as we tend to travel and make arrangements that after we know how far we may be going. I’m ‘assuming’ the date actually gets filled in with the ‘correct’ reservation date if a reservation is entered and creates a visit history record?
Steve
I’ve made this change for the next update. If we import a database from the classic version of the app (which had no booking date), we have to set the booking date to something - and our best guess is the arrival date. It’s imperfect, but I think it’s a reasonable guess for historical records. Obviously if the user wishes to change the booking date to an accurate one, the app will honor that change.