topic Re: Trouble with capability API - field selectValues in Integration, Extension & APIs

Trouble with capability API - field selectValues

jgunders — Fri, 15 Nov 2019 19:01:23 GMT

Trying to set up a mashup with two apps and shared filters. There is a listener on the selectionState of the first app like this:

which sets the field selectValues of the second app. This works for some fields but not all. I looked at one of the problem fields using

app.field('METRIC DATE.YEAR').getData();

compared to:

app1.field('METRIC DATE.YEAR').getData();

and it is identical in both apps. I also tried setting it directly as numeric and text:

app1.field('METRIC DATE.YEAR').selectValues([2016], true, true);

app1.field('METRIC DATE.YEAR').selectValues(['2016'], true, true);

but no luck.

Any ideas on what to try next?

Re: Trouble with capability API - field selectValues

agni_gold — Sat, 16 Nov 2019 17:16:07 GMT

have you tried like below

app1.field('METRIC DATE.YEAR').selectValues(2016, true, true);

or have you tried with
selectMatch method ? , is this working ?

or you can provide your js code , may be i can help

Re: Trouble with capability API - field selectValues

jgunders — Mon, 18 Nov 2019 01:23:29 GMT

I tried:

app1.field('METRIC DATE.YEAR').selectValues(2016, true, true);

but it throws:

e.forEach is not a function

I attached the source. Thanks!

Re: Trouble with capability API - field selectValues

ErikWetterberg — Mon, 18 Nov 2019 04:34:40 GMT

Try with [] since the field name contains spaces:

app1.field(‘[METRIC DATE.YEAR]’)...

Re: Trouble with capability API - field selectValues

jgunders — Mon, 18 Nov 2019 21:40:44 GMT

Thanks for the help with this @ErikWetterberg and @agni_gold . Turns out it is a problem of text verses numeric. Looks like all the selections from selectionState are text but my selections can be text and numeric ☹️. I'm going to force all my shared dimensions to be text.