Loading

Screen Flow File Upload component returns null contentDocIds/contentVersionIds when two File Upload components share the same screen and output variables

Fecha de publicación: Sep 1, 2026
Descripción

When a Screen Flow contains two File Upload (forceContent:fileUpload) screen components on the same screen, and both components are configured to write their outputs (contentDocIds, contentVersionIds, fileNames) to the same variables both components return null for these outputs after a file is uploaded even though the upload itself succeeds and the file is attached to the record. This occurs on Flow API version 56 and above and the flows run at API version 55 or lower are not affected.

This is expected platform behavior. Starting with Flow API version 56 the platform began nulling values for fields under certain hidden/duplicate-binding conditions to align with documented conditional-visibility behavior.

Solución

Create two separate output variables one set for each File Upload component (e.g., Uploaded_DocumentIds_One / Uploaded_VersionIds_one and Uploaded_DocumentIds_two / Uploaded_VersionIds_two).

Assign each forceContent:fileUpload component's contentDocIds/contentVersionIds/fileNames outputs to its own dedicated variable set  do not reuse the same variable across both components.

Update any downstream elements (Decisions, Assignments, other screens) that referenced the original shared variable to reference the correct component-specific variable instead.

Número del artículo de conocimiento

005393415

 
Cargando
Salesforce Help | Article