Hi @shawnrosspeters 

Good question.

Try this…

Change the output to this to include the opening/closing brackets e]

output = t{id: ids index]}];

Hi @shawnrosspeters 

Good question.

Try this…

Change the output to this to include the opening/closing brackets e]

output = t{id: ids index]}];

 

 

Thanks @Troy Tessalone but that didn’t work either. I still just get an ID number of some kind and some metadata when I “Retest & review”

@shawnrosspeters 

We’d need to have you paste your exact code and inputs in order to troubleshoot further.

I tested this

Which returned this…

@Troy Tessalone

I’ve copied and pasted everything. I only changed the phone numbers so my real numbers aren’t exposed publicly.

Input Data

names

3. Primary:true,false

ids

3. Number:8305551234,8305555678

username

true

Code

const names = inputData.names.split(",");

const ids = inputData.ids.split(",");

const index = names.findIndex(name => name.includes(inputData.username));

output = t{id: ids index]}];

@Troy Tessalone sorry. I had to edit the post afterward. Weird glitch, lol.

@shawnrosspeters 

It worked for me.

CONFIG

RESULTS

I finally figured this out and got it to work!

TL;DR

The search variable (in this case “username”) is case-sensitive. If you're attempting this same How-To and your code Output isn’t working as expected then record the “Test Action” in a screen recording. This will let you slow it down to see if the data being processed actually matches what you think it should be or not. In my case, I thought everything was lowercase when in reality it was Capitalized.

The good news is that the square brackets (i.e. k ]) are not needed nor were they causing the problem.

I first tested by manually inputting the key|value pairs, just like your last comment, and it worked when I tested the action. However, it STILL didn’t work when actually using the dynamic values generated in Step #3 from the Zap.

I then edited a short screen recording so I could show you the discrepancies when I noticed for a fraction of a second the “processing test” portion of the manually entered values. I’m including links below.

Manually Entered key|value pairs

Using variables from previous step

Screenshot of variables in “Set up action”

The issue is that the “username” key was looking for “true” in all lowercase but my dynamic values from Step #3 were ACTUALLY being pushed through capitalized, i.e. “True” instead of “true”. What stumped me was that the Step #3 variables show as all lowercase when you’re viewing the “Set up action” portion of the Code Step. Even though these are actually pushed through in the code step as Capitalized.

So, thank you @Troy Tessalone for your help in narrowing this down and thank you @nicksimard for the original article and initial support! Maybe you can add a “FAQ” or “Common Problems” to your article over at 

😎

@shawnrosspeters Woohoo! This is great! I am so glad you and Troy were able to work through this one and super grateful for you coming back to this thread to share your solution with us! What a lovely team effort.