Migrate Config Key

Beta

The Historical User Activity feature is currently in beta for the Analytics tool.


The Analytics Cloud Connector CLI provides a new configuration key named source_config.exclude_tables, which replaces the legacy process_user_activity key. While the old legacy key remains supported for backward compatibility, Procore recommends migrating because the new configuration framework applies uniformly across all append and incremental tables.

Legacy Format (Supported)

  • process_user_activity: true # or false
    source_config:
    config_path: /path/to/config.share
    tables:

New Format (Recommended)

  • source_config:
    config_path: /path/to/config.share
    tables:
    # Tables listed here skip append/incremental loading (they'll be loaded
    # via the regular full-reload path instead). Names are case-insensitive.
    # Use ['*'] or ['__all__'] to opt every table out of append routing.
    exclude_tables: []

Migration Cheat Sheet

Old Setting

New Setting

Effect/Resulting Behavior

process_user_activity: true (or unset)

source_config.exclude_tables: [] (or unset)

Enables append/incremental loading for the user_activity table and other append-eligible tables. Required for historical user activity data sync.

process_user_activity: false

source_config.exclude_tables: ['user_activity']

Excludes the user_activity table from append routing. It will load via the regular full-reload path instead. (Not recommended due to data volume).

Note: If both configuration keys are defined in your config.yaml file, the new source_config.exclude_tables setting will take priority.

Backfill User Activity History
FAQ/Troubleshooting