Pulling Field Values Through of a Specific qState

HLN — Sat, 21 Dec 2024 02:18:08 GMT

I don't believe this is currently supported and wondered if we could get support for this as it would optimize API usage and expand extension capability.

When we call this or the createList equivalent:

app.createGenericObject({ qInfo: { qType: "ListObject" }, qListObjectDef: { qDef: { qFieldDefs: [field name] }, qShowAlternatives: true, qInitialDataFetch: [{ qTop: 0, qLeft: 0, qWidth: 1, qHeight: chunk size }] } })

Can we narrow the scope of the data we are looking to pull? Granular level like qState would be the most obvious.

So I for example could pull all SELECTED qState values of a field and not get any other qState come through on the data request.
Currently without this it's very inefficient to pull data through.

Re: Pulling Field Values Through of a Specific qState

Øystein_Kolsrud — Fri, 03 Jan 2025 08:36:41 GMT

The simplest way is to use a hypercube instead of a list object for this. At least as long as you are only looking to pull "SELECTED" values. If you want something more generic then you can use a combination of a list object and a hypercube. If you for instance want to extract "EXCLUDED" values, then call "SelectExcluded" on the list object and then you're back to the case where you can use the hypercube to extract the selected values.

It might also be worth reminding that it's perfectly fine to have both a list object and a hypercube in the same GenericObject. So you could define your properties something like this:

app.createGenericObject({
  qInfo: { qType: "MyObjectType" },
  qListObjectDef: {qDef: {qFieldDefs: [field name]}},
  qHyperCubeDef: {qDimensions: [{qDef: {qFieldDefs: [field name]}}]}
})

topic Pulling Field Values Through of a Specific qState in Integration, Extension & APIs

Pulling Field Values Through of a Specific qState

Re: Pulling Field Values Through of a Specific qState