Appointments & Scheduling · How-to guide

Configure the Google Calendar date range in the appointment table

Limit how much remote Google event data is loaded around the current date for useful context and responsive performance.

Audience: Staff who manage appointmentsFeature: Google event rangeModule v1.3.6
Feature pathAppointments > Settings > Google Calendar
Before you beginThis guide follows the supplied Britixo Appointments & Scheduling module version 1.3.6. The relevant access is Appointments: View. A menu, button, provider, time slot or client action can remain hidden when the signed-in user lacks the required permission, the module setting is disabled, the related record is in an ineligible state, or availability validation rejects the request.

What this feature does

Limit how much remote Google event data is loaded around the current date for useful context and responsive performance. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.

How the module flow works

The module stores past and future range settings for remote event retrieval.

When event display is enabled, the table requests only events within that configured window.

The range affects remote display, not native Britixo appointment retention.

Step-by-step workflow

  1. Open Google Calendar settings.
  2. Set a practical past period.
  3. Set the required future period.
  4. Save and reload the appointment table.
  5. Confirm remote events outside the window are intentionally absent.

Important fields and decisions

Past rangeHistorical remote-event window.
Future rangeUpcoming remote-event window.
Table displayContextual remote events shown with appointments.
Native retentionUnaffected Britixo appointment history.

What happens after completion

After this workflow completes, Britixo keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Britixo database save.

  • Open the saved appointment and confirm the final status and source.
  • Check the participant, provider, timing and timezone from the full detail page.
  • Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.

Controls, checks and common mistakes

  • Avoid very large ranges that slow API loading.
  • Do not interpret an absent old Google event as a deleted Britixo appointment.
  • Reconnect Google if no events appear within a known valid range.
  • Use the least destructive correction and retain the appointment history when the booking existed operationally.
  • Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.
Scheduling and data safetyAppointment changes can notify customers, reserve provider time, update remote calendars, create meeting links or invoices and alter reports. Confirm the exact record, timezone, status and recipients before saving.