Hi @Joseph Esposito 

Good question.

When testing the Excel step, make sure to find a row that has the columns populated, so you can map those to the next Zap steps.

Hi @Troy Tessalone ,

The current excel has rows populated & the lookup is pointing to Column A, which is the “Tag” column. 

@Joseph Esposito 

Were you able to test the Excel step to successfully find and return a matching row?

The mapped Tags (tag1,tag2) for the Lookup Value don’t appear to match the Tag naming conventions in the Excel file.

Also, if there are multiple Tags, then that will likely results in 0 matched rows.

Yes, Tag functionality works correctly. Here is an example where it was able to find the resulting row & then the returning values were blank. 

@Joseph Esposito 

Can you show a screenshot of the DATA OUT from the Excel step?

This will shows the found Row ID.

Certainly, attached is a snip of the “Data Out” section. 

@Joseph Esposito 

In the Zap Editor when configuring the Zap steps, you can use the ‘Custom’ option to map dynamic variables between Zap steps.

Did you do that when you were configuring the Zap steps?

EXAMPLE

Hi @Troy Tessalone,

In this mapping instance there is no option for dynamic variables, only what is available in the dropdown menu. as you can see in the attached example, the columns from the prior excel lookup step is not populating, even though the prior steps are successful. 

In lieu of entering the variable you are able to enter the custom pill that should point to the correct column. In this instance i have tried using both the title of the column and the column name. Both fail:

The node pointing to the prior lookup: 203356069

Column E: Competitors

Ive tried the following:

{{203356069_COL$E}}

{{203356069_Competitors}} 

both fail. 

@Joseph Esposito 

Is there data in Row 1234 of the Excel file?

If yes, then provide a screenshot of that Excel Row.

@Joseph Esposito 

If you are trying to do use custom variable syntax, then you will need 2 underscores after the Step ID.

{{203356069__COL$E}}

{{203356069__Competitors}}

Nothing in Row 1234.

Hi @Troy Tessalone ,

I believe that was the missing piece, I will confirm once all updates are made!

@Joseph Esposito 

Make sure to test the Excel step to successfully find a matching row.

@Troy Tessalone 

I can confirm I was able to successfully test & deploy the update. thanks!

Joe

That’s brilliant news, @Joseph Esposito! Thanks so much for taking the time to come back here and confirm that Troy’s suggestion did the trick. It’s much appreciated!