![]() I've been optimizing the Qlik data models and the NPrinting reports, and the set analysis is totally unnecessary from Qlik's perspective. However, presently dates are being passed in as two separate selections, and then in Qlik, with the help of a variable, set analysis is used for many calculations. We pass in a variety of explicit values that the other application is aware of. NPrinting then calls Qlik, makes the selections and then NPrinting can provide a report to print. In my current use case, however, NPrinting is being called from a different application. If I then were to call the NPrinting AP, I can easily provide the explicit values because they have already been selected by Qlik. If I am in QlikView/QlikSense, I've made my selections, whether by clicking, or selecting a range, or using an advanced search. Thank you again for the response think I do understand. But what I'm not getting correct is the format of the JSON. ![]() That one seemed the most promising, since the documentation clearly mentions that you can do an advanced search. So, at the moment, there is no way to just pass in a range, numeric, or date, into a report using the API? "connectionId": "226546c7-0513-4575-8c39-1f598dd4e2a8",Īs per types everything is described in documentation: thank you so much for the quick response. "description": "Example of a filter created via API Postman", once you execute below using post method ( you should see new filter created in filters.based on what you see below you need to provide valid app id, valid connection Id and name of the existing Field in that connection.You can learn from there structure of the payloads required by inspecting them in browser developer toolsīut to cut story short here are the steps you can do via API: Instead you can use npe api which is not documented and not supported, but it is used by nprinting admin console interface. If your aim is to create a filter and associate it with report or task then it is not available via the api/v1 endpoint. There is only endpoint associating filters to users though. The problem I can see here sits in the fact that there is no endpoint to associate filter with report. So they way it works is that you first need to create filter and then associate that filter with entity. I have attempted a few variations, but I'm not getting it right. All of our current requests take the following form: I've been through the API documentation, and I can see that there is a FilterField and FilterFieldValue, but can't quite figure out how to use them the right way. I actually wrote an even longer post just a few minutes ago, and when I went to post it the website gave me an auth error and lost my post. I've tried a few variations of our API calls to mimic this, but I can't seem to nail down the right one. This works great.īut obviously we use the API for some other integrations and on demand report creation from other applications. ![]() The shortest form of my question is - is it possible to apply an Advanced Search on a field via the NPrinting API? For example, a date range. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |