I am experiencing two unexpected behaviors with a table I’ve added with the source as a Google Calendar.
With any entries, I create/update on the table, the Time set in not in the correct time zone. So for eg. I am in India and setting the time for 12:00PM results in the event actually being scheduled at 6.30AM which exactly corresponds to Indian Standard Time (GMT+05:30). This happens with the locale of the table being set as either US or India.
I have an Appointments table which has two fields: CalenderID - set as a Ref to the Google Calendar Table CaseID - set as a Ref to my Cases table.
As a result, I have a Related Appointments List in my Cases Detail View. So this way I am able to create a New Appointment from within my Cases Detail View. For creating a new Appointment I have two inputs: CaseID and CalenderID. The Calendar ID field being a Reference field allows me to create a new one. This takes me to the Form view of the Google Calendar table where I create a new Calender event. This works just as expected and the new Appointment appears correctly on my Related Appointments Inline View but only for few seconds after which it disappears from the list. This happens because the CalendarID field gets a new UniqueID which differs from its intial value at the time of its creation. This breaks the reference and I get a yellow exclamation mark against the CalenderID field as it does not exist. Then if I edit this Appointments entry by associating the CalendarID again with the entry for the Calendar event I just created, the reference is reestablished. This is an undesirable behavior - It looks like AppSheet assigns the CalendarID a temporary unique value which is later updated by Google Calendar.
Can anyone please explain how should I go about solving these two issues? Or is it a bug and the AppSheet team needs to fix it?