• When dealing with nested fields with special function names in materialized views, you can use qualified column names to avoid conflicts.

CREATE MATERIALIZED VIEW crm_view AS
SELECT
    timestamp AS timestamp,
    (crm.user).id AS user_id,
    (crm.user).device_id AS device_id,
    (crm.user).browser_type AS browser_type
FROM crm;

• Another workaround is to change the field name to avoid conflicts with special function names.

CREATE MATERIALIZED VIEW crm_view AS
SELECT
    timestamp AS timestamp,
    (user).id AS user_id,
    (user).device_id AS device_id,
    (user).browser_type AS browser_type
FROM crm;