Why only some embedded variables are showing up in XM Directory workflow? | XM Community
Skip to main content

 

Hi there,

 

I have created embedded variables, all mapped correctly and I can pull from these using pipped text so I know the embedded variables are working. 

Embedded data in the workflow

For some reason when I am trying to import embedded data into the XM Directory workflow, only one variable (“postal 2”) is showing up and the rest are only available under “transactional data” (e.g., “emaile”; ps. I spelled email like that to differentiate it from the contact ‘email’). 

 

Showing the only embedded data showing up
Showing that embedded data is showing up as transactional

Does anyone know why this is the case?

 

Thanks in advance!

Hi ​@Makgomes,
 

My understanding is that 

  • Only the embedded data fields explicitly declared before the survey starts (in the Survey Flow) are registered as “Embedded Data” in XM Directory workflows.
  • Any fields that are created or modified during the survey (e.g., via Set Embedded Data blocks that appear after the Start of Survey or are conditionally set) are usually treated as transaction-level fields, not as embedded directory fields.

That’s why only "postal 2" is appearing in the “Embedded Data” category—it seems to be the only one defined up front in the Survey Flow before the survey begins. The rest (like "email2", "First_name", etc.) are being created dynamically later in the survey and thus show up as transactional fields.

To fix this, go to your Survey Flow—preferably at the very beginning—and add an Embedded Data block that lists all the variables you want to appear in XM Directory (e.g., email2, First_name, Last_name, etc.). You don’t need to assign values; just pre-declaring them ensures they’re recognized as embedded fields rather than transaction-level data.

 

Let me know if that resolves the issue!

– Rochak

Terms & ConditionsAccessibility statement