Accessing additionalScope from JsCode query

Queries and Resources
1

According to the docs for Query.trigger():

  • The additionalScope option allows you to define additional variables to pass to the triggered query when it is run. It accepts an object with any number of key value pairs and all keys will be accessible inside of the triggered query as {{key}}

But the {{object}} syntax is not valid in the javascript body of a JsCode query. Just typing the name of the key gets highlighted as an error and does not seem to work. How/can the additionalScope key/values be accessed?

1 Like
2

@acoulson Do you have an example you can share?

3

Agreed, @ScottR! @acoulson it would be great to see a screenshot of where this isn't working


The below example works for me, and the row object value can be accessed in the triggered query under id.row

2004×750 60.5 KB

4

Since my app is quite complicated, I couldn't provide an example easily, but I will start with a simple test case like yours, @Tess, and work up from there. Will post back with results.
Thx

5

As I've seen it's available as variable in the other query that you trigger.
For easier development you can enumerate the values you'll plan to use with var. BUT let/const won't work for this case.

/* other_query */
var ctx_j, ctx_i; // it works without this line as well

const ctx = {
   i: ctx_i ?? 99, // set default value
   j: ctx_j || 45, // this also works if you prefer this one
};

console.log("DATA", ctx);
return ctx;

And you can call it from the other place like this:

/* original_query */

other_query.trigger({
  additionalScope: { ctx_j: 5 }
}).then((result) => console.log("Final ctx is: ", result))
1 Like
6

Yep, we got it to work. Must have a been a problem elsewhere in my logic.