Qlik Community

Ask a Question

Integration, Extension & APIs

Discussion board where members can learn more about Integration, Extensions and API’s for Qlik Sense.

LINKEDIN LIVE: Democratizing data to enhance customer-centricity. JULY 29TH REGISTER TODAY
Showing results for 
Search instead for 
Did you mean: 

[QRS API] to cut a result


I'm trying to load data using QRS API. Everything goes fine, except "user/full". There are too many rows there. So I decided to cut the result.

Here is a JSON structure: https://help.qlik.com/en-US/sense-developer/February2019/APIs/repositoryserviceapi/index.html?page=1...


Filtering by "userId" field works fine: https://localhost/qrs/user/full?filter=userId eq 'some_userId_value'

But I can't use same filtering logic with "attributeValue" field: https://localhost/qrs/user/full?filter=attributeValue eq 'some_attributeValue_value' gives error "Cannot convert the constant value: attributeValue".

As I can suggest, this is because "attributeValue" is a subfield (a part of "attributes" array).

But I don't know how to write field names in such a case and if it is possible at all.

Tried to hardcode "...filter=attribute/attributeValue eq..." and so on, but didn't help.

1) So the first question is what filter construction would be correct in case we need to filter by an attribute, which is not in root table?


As a workaround, I see Offset Pagination. But I have no idea, what should be 'Start','Record','Total' REST connector parameters in the QRS API. 'Start','Record' could be 'offset','limit', but I'm not sure. And what should be Total... And I found it a bit difficult to find any information about it.

2) And next question is what parameters to fill in REST connector pagination?

Labels (4)
1 Reply
Specialist II
Specialist II

Did you find a solution about paginating QRS API?