Skip to content

fix: filter excludedFields from expandedOriginalQueryFields#1207

Open
alanjaouen wants to merge 1 commit into
forcedotcom:masterfrom
alanjaouen:fix/excluded-fields-csv-columns
Open

fix: filter excludedFields from expandedOriginalQueryFields#1207
alanjaouen wants to merge 1 commit into
forcedotcom:masterfrom
alanjaouen:fix/excluded-fields-csv-columns

Conversation

@alanjaouen

@alanjaouen alanjaouen commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Fields listed in excludedFields were correctly removed from the SOQL query but still appeared as columns in output CSV files.

Root cause: expandedOriginalQueryFields combined _originalFieldsInQuery (filtered early) with _resolveMultiselectFieldNames (unfiltered). When using SELECT all, all fields come from the multiselect resolver, so the per-field exclusion check was entirely bypassed.

Fix: Move the excludedFields filter to after all field sources are merged, so it covers both _originalFieldsInQuery and multiselect-resolved fields.

Closes #1206

@salesforce-cla salesforce-cla Bot added the cla:signed CLA signed label Jun 17, 2026
Fields listed in `excludedFields` were correctly removed from the SOQL
query but still appeared as columns in output CSV files.

Root cause: `expandedOriginalQueryFields` combined `_originalFieldsInQuery`
(filtered) with `_resolveMultiselectFieldNames` (unfiltered). When using
`SELECT all`, all fields come from the multiselect resolver, bypassing
the exclusion entirely.

Move the excluded-field filter to after all field sources are merged so
it covers both `_originalFieldsInQuery` and multiselect-resolved fields.

Closes forcedotcom#1206
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla:signed CLA signed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

excludedFields still showing up in output CSV columns

1 participant