HubSpot/SFDC Conditional Field Overpersistence

This is the opposite pattern from questionnaire-hidden-variable-data-loss. That skill covers integration values being wiped (platform clears correct values). This skill covers hidden values being incorrectly persisted (integration saves incorrect values, platform later cleans up correctly).

Affected code path:

• Repo: SpotDraft/angular-frontend
• File: sfdc-questionnaire-container.component.ts, method: getDataUpdateRequest(), ~line 1701
• Bug: Uses this.questionFormService.allValues$ instead of this.questionFormService.allValuesExcludingHiddenQuestions$
• Fix branch: cursor/prompt-therapy-conditional-logic-03ae

Available MCP Tools

BigQuery — Contract Data & Scope Identification

⚠️ Run BQ queries one at a time — parallel execute_sql calls return 500 errors.

Check ContractData entries for a contract (Prod US):

SELECT id, source, is_completed, critical_update, created, modified,
       JSON_EXTRACT(data, '$') as data_snapshot
FROM `spotdraft-prod.prod_usa_db.public_contracts_v3_contractdata`
WHERE contract_id = {contract_id}
ORDER BY created ASC
LIMIT 20

Look for:

• Early rows (source: Info-Collection, is_completed: False, critical_update: True) — hidden fields incorrectly populated with defaults
• Later rows (after UI edit) — same fields absent/wiped (cleanup fired correctly)

Check contract status and kind:

SELECT id, status, contract_kind, workflow_status, created, modified
FROM `spotdraft-prod.prod_usa_db.public_contracts_v3_contractv3`
WHERE id = {contract_id}

Identify HubSpot-initiated contracts for a workspace in a date range:

SELECT id, status, contract_kind, workflow_status, created, modified
FROM `spotdraft-prod.prod_usa_db.public_contracts_v3_contractv3`
WHERE workspace_id = {workspace_id}
  AND created >= '{start_date}'
  AND created <= '{end_date}'
ORDER BY created DESC
LIMIT 200

Cross-reference with the contract data source to confirm Info-Collection (HubSpot) origin.

Check metadata linked to questionnaire variables (to see what was deleted):

SELECT id, key, value, source, created, modified, is_deleted
FROM `spotdraft-prod.prod_usa_db.public_metadata_v2_metadatafield`
WHERE contract_id = {contract_id}
ORDER BY modified DESC
LIMIT 50

Environment-to-Dataset Mapping

Admin Panel URLs

When to Use This Skill

Use when:

• HubSpot or Salesforce-initiated contracts show mass field deletions in Activity Log triggered by a single minor edit
• Customer reports "editing one field deleted 10+ metadata fields" or "70+ fields changed at once"
• HubSpot-initiated contracts have unexpected default values in conditional fields that should be empty
• Customer reports metadata linked to questionnaire fields is suddenly missing after a contract edit
• Investigation points to the SFDC/HubSpot app running on stale code (check HubSpot deployment version vs. main app)

Do NOT use for:

• Integration connection errors (HubSpot/SFDC not syncing at all) → use email-delivery-triage or infrastructure-alert-response
• Values wiped because of always-false hidden conditions (sd_show = false) → use questionnaire-hidden-variable-data-loss
• Non-HubSpot/SFDC contract creation paths
• Questionnaire conditional logic slowness or UI rendering bugs

Step-by-Step Investigation Workflow

Step 1: Confirm the Pattern

Get the contract ID, workspace ID, and cluster from support. Open the contract data in Django Admin: