Charge Configs

🛠️ Partner API Alignment Migration

🧭 This table represents the post-migration state for charges__charges_config.

1️⃣ Migrate to this table by April 2026

2️⃣ Between April 2026 and July 2026, remove FUTURE__ prefix

⚠️ Note table name change: Please note the table name change from charges__charges_config to standardise table naming

Contains charging configuration details for charging sessions. Associates charge events with their corresponding firmware settings, reservations, and scheduling parameters.

SQL: FUTURE__charge_configs

Schema

Column Name	Data Type	Description
Primary ID
id	INTEGER	primary key
Other IDs
charge_id	INTEGER	Foreign key reference to the associated charging session
Timestamps
scheduled_start_at	TIMESTAMP_NTZ	Scheduled start time for the charging session
scheduled_stop_at	TIMESTAMP_NTZ	Scheduled end time for the charging session
Attributes
firmware	VARCHAR	Version of firmware running on the charging equipment during this session
is_reservation	BOOLEAN	Indicates whether this charging session was created through a reservation. True if reserved, false if ad-hoc.
reservation_min	INTEGER	Minimum duration in minutes required for the charging reservation
native_schedule	VARCHAR	Raw schedule configuration data from the charging equipment's native format

Changes from Last Version

Standardized table naming from charges_config to FUTURE__charge_configs for consistency across datasets.
No changes to schema or data types; existing fields remain unchanged.
Inclusion criteria relaxed see below

Data inclusion criteria

This table works with FUTURE__charges table, requiring that charge_id is among the partner's FUTURE__charges.id records.

Data flow

Upstream tables	Downstream tables
`FUTURE__charges`	`FUTURE__failed_charges_info`

Alignment

-- is downstream of FUTURE__charges which has relaxed inclusion criteria -- one needs to align FUTURE__charges and use that id list to filter this table -- easiest is to ìnner join with FUTURE__charges and align that table:

     inner join FUTURE__charges as c
      on t.charge_id = c.id
            where
              -- Match OLD model logic: filter by operator_role and ensure CP/team are in OLD tables
              (
                -- For owner/both roles: charge_point must exist in OLD charge_points table
                (c.operator_role in ('owner', 'both')
                 AND c.charge_point_legacy_alignment_flag = true)
                OR
                -- For payer role: paying_team must not be deleted
                (c.operator_role  in ('payer', 'both') AND c.paying_team_deleted_at is null)
              )