One of our users recently made us aware that the custom fields information isn't sent in the email notifications when the appointment is reshceduled, so I assume this is connected to that. I will forward this to our developers as well, so they can check this out as well and hopefully fix soon. Sorry for any inconveniences this have caused.
If you have any other questions or concerns feel free to open a new ticket and we will gladly help.
I've just tested this and it seems to work fine on our website - I tried rescheduling both from the customer panel and in the back-end but couldn't replicate the issue, the custom fields are there, in the Google event after rescheduling. Could you please check this out once again or tell us more details about your service (the setup), maybe there is some pattern that I should replicate in order to get this outcome?
Hello Amelia Team,
I noticed a problem since last update in august.
When a client reschedule an appointment, the %custom_field% simply disappear on google calendar.
Through normal booking process, everything is fine. It's just after rescheduling.
Thanks,
Laurent
Hello Laurent,
One of our users recently made us aware that the custom fields information isn't sent in the email notifications when the appointment is reshceduled, so I assume this is connected to that. I will forward this to our developers as well, so they can check this out as well and hopefully fix soon. Sorry for any inconveniences this have caused.
If you have any other questions or concerns feel free to open a new ticket and we will gladly help.
Hello,
This bug appears again since 4.1 update. I did the update to 4.2 but it remains.
The "custom field" disappears in google calendar when we change or reschedule an appointment.
Could you check it ?
Thanks
Laurent
Hello Laurent,
I've just tested this and it seems to work fine on our website - I tried rescheduling both from the customer panel and in the back-end but couldn't replicate the issue, the custom fields are there, in the Google event after rescheduling. Could you please check this out once again or tell us more details about your service (the setup), maybe there is some pattern that I should replicate in order to get this outcome?