Global Variables Not Working in Salesforce Flow Transform Element

This article answers the question: why do global variables like `$User.Id` or `CurrentDate` fail when mapped directly in a Flow Transform element, and how do I work around it?

The Error

Using a global variable directly within the Transform element mapping triggers the following error:

"These mappings or join transformations are invalid. Make sure that the fields are available and compatible on the referenced objects or Apex classes. Then save and reload the flow, or invalid mappings and invalid join transformations."

The detail typically reads something like: "The '$User.Id' field is no longer available. It was previously mapped to the 'Account[$EachItem].OwnerId' field."

Why This Happens

This is a known product limitation. The Transform element does not currently support referencing global variables (for example, the running user's ID or the current date) directly in its mapping logic.

Workaround

Create a separate formula resource to capture the global variable you need — for example, a formula resource that returns `$User.Id` or `CurrentDate` — and reference that formula resource in the Transform element mapping instead of the global variable itself.

Product Status

The Product Team has logged a bug for future improvements, including documentation updates and clearer validation messaging when global variables are used in the Transform element.