Use a JavaScript object to define your flags:

```

var table = {

MLB: { A: true, B: true, C: true, etc.},

EPL: {A: true, B: true, C: false, etc.},

...etc...

};

```

Then pipe the league into the JavaScript to lookup the league in your table (e.g., `table["${e://Field/league}"]`), and loop through the league's block object and set your embedded data variables appropriately.

---

Thank you for the incredibly quick reply!



This idea seems simple enough (after I did some reading and learned about for... in loops), so I'll give it a try when I get back to the survey building. Thanks again!

---

I would use jQuery.each for the loop.

---

Thanks! I haven't used that command before, so I'll read up on it.



(I first used jQuery when doing coding for a different Qualtrics survey a month ago. That's how ignorant I am about JavaScript. But, thanks to your help now, I'm improving quickly!)

---

<p>TomG - Thanks again for your help. Just that little bit gave me enough to get started. I've spent around 50 hours this week on just the opening page of my survey, but I've learned a ton about JavaScript, variables, objects, jQuery, etc. I did a lot more than this lookup table, but that is what got me rolling and made me want to do a lot more along the way.</p>



<p>For future readers, below is a little bit of what I did. I know it isn't perfect, but I couldn't have explained this last week (much less written it), so I'm pretty pleased. Of course, I'm very open to suggested improvements.</p>

<p>First, I store the data table as an object. Below is an example of tbljsLeagues, but there were actually multiple data tables (I was getting cocky).</p>

<pre><code>

var tbljsLeagues = {

lgID_001: { lgID:1, lgSport:"American football", lgSlug:"s_m_afb_ncaad1a", lgHasProRel:false},

lgID_002: { lgID:2, lgSport:"Ice hockey", lgSlug:"s_m_hok_nhl", lgHasProRel:false},

};

</code></pre>

<p>Next, I check the user's answer to a multiple choice question. Those answer choice values have been re-coded to match the lgIDs in the tbljsLeagues table.</p>

<pre><code>

var questionObject = Qualtrics.SurveyEngine.getInstance(paramQuestionID);

var currentResponse = questionObject.getSelectedChoices()[0];

var choicesObject = questionObject.getQuestionInfo().Choices;

var thisChoiceObject = choicesObject[currentResponse];

intLgID = parseInt(thisChoiceObject.RecodeValue);

strLgObjName = "lgID_"+("00" + intLgID).slice(-3);

</code></pre>



<p>Now that I know which "table row" I want, I can work with the data. For example, if the intLgID=2 (the user selected the NHL), the following both return "s_m_hok_nhl": <code>tbljsLeagues[strLgObjName].lgSlug;</code> and <code>tbljsLeagues[strLgObjName][lgSlug];</code>. The second way of writing this was important because it allows dynamic content for the property name.</p>

<p>I ended up writing the iteration code to read each key:value pair in the table into an object variable, then write that to Qualtrics embedded data.</p>



<pre><code>

var objDataToEmbed = {};

objDataTableRows = [tbljsLeagues[strLgObjName], tbljsSurveys[strSurvObjName]];

var objTableRow = {};



jQuery.each(objDataTableRows, function(paramTableRow) {

objTableRow = objDataTableRows[paramTableRow];

jQuery.each(objTableRow, function (paramTblProperty) {

objDataToEmbed[paramTblProperty] = objTableRow[paramTblProperty];

});

});



jQuery.each(objDataToEmbed, function(propKeyED, propValueED) {

Qualtrics.SurveyEngine.setEmbeddedData(propKeyED, propValueED);

});

</code></pre>

<p>Sorry it took me so long to get back, but I just wanted you to know how much I appreciated your guidance. It has put me down a path to making this survey much better than it would have been otherwise, and I'm grateful for you (and the internet community at large) for taking the time to help others. If you ever make it west to Asheville, I'll gladly buy you a local beer.</p>

---

dtyler - will you please attach a copy of your .qsf file so I can import and see this in action?

---

Julie - See attached.



I've learned a lot about JavaScript since writing this code, and looking back on it now I'm pretty embarrassed. I'm not doing things the right way, and I'm a little surprised this works at all! But it does work, so I hope it's helpful to you.

(don't worry about about all the IU logos... they're just placeholders)

---

hi @dtyler  @Julie_130 , just thought I’d add a comment to this thread as Qualtrics (albeit 5 years down the line!) are releasing a new Lookup task which should hopefully simplify things and will work of a supplemental table.

I’ve yet to try it out and especially keen to know if this will work in a loop task situation meaning it may allow us to update or change data (embedded fields) retrospectively instead of doing complex API stuff.

 

Hope that helps someone (in some way!) :)

---

@Rod_Pestell Oh my goodness -- that lookup feature would have saved me months of headaches and workarounds.

 

Thank you for calling it to my attention!! I will probably have that as part of all my surveys going forward.

---