-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persist the appointment price and currency for future use #1406
Comments
Hello! This is a good idea. I think in general it would make more sense in the future to store the customer info as well, as they may change in the future. So we need to have the right information in the database for the time of booking.
|
On which data do you think here? I think the customer remains the same customer even if he moves somewhere else. That's why I'm not sure whether it's really necessary to save the customer's data on the appointment itself. For me it makes more sence to save some infos from the booked service on the appointment directly. |
For example the customer data at the time of booking would be important info to keep, as those might change later on
|
@alextselegidis I am working on this in my fork as a pre-cursor to adding #710 I saw the requirement for these new fields in my personal use case:
I'll allow the backend modal to set a custom total & currency but default to the selected service rates Do you have any specific input before I try to upstream? 🙏 |
Hello! Thanks for posting this Let's better name the fields:
Make sure there's a migration for each one of them and update the model class accordingly Also this should go to develop branch
|
I'll update my local mirror to use |
It would be great if the price currently valid at the time of booking could be saved on the appointment. Any price adjustments can be better tracked so that the customer is not charged the wrong price.
The text was updated successfully, but these errors were encountered: