Jump to content
We've recently updated our Privacy Statement, available here ×

hainz

Members
  • Posts

    2
  • Joined

  • Last visited

hainz's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Hello, i need to export the parameters values selected (input controls) of reports in the scheduler. The REST API only gives me access to the general parameters of the reports binary, not the one specific ones selected in the scheduler. Next approach was to access the Jasperserver DB directly to gather the selected options for each parameter. Sadly they seem to be obfuscated in some way. In the DB i can find hex code like this: "xaced0005737200116a6176612e6c616e672e426f6f6c65616ecd207280d59cfaee0200015a000576616c7565787000" The datatype is somewhere in there and i assume the last 8 bit represent "TRUE" or "FALSE". Is there any easier way to aquire this info or am i missing something about decoding the hex code? Thanks!
  2. Hi, i've been working with JasperReport for about half a year now and i stumbled across my first problem which i am not able to solve by myself after a couple days. For a lot of my queries i use the $X{IN, <column_name>, <collection_param>} syntax several times in the WHERE clause to select a subset after joining. Now i would like to completely ignore / remove the JOIN adn WHERE clause if the collection is empty (= no element selected from input control). No problem removing the JOIN clause, but i am having trouble with the WHERE clause. I was thinking about something like: $P{WHERE_CLAUSE} = IF($P{COLLECTION}.isEmpty(), "", "WHERE $X{IN, column, $P{COLLECTION}}") and use $P!{WHERE_CLAUSE} - but i did not get this type of query to work. I figured it is because the query string does not take the $X parameter as an actual string, but other approches with different datatypes failed too. The only other way i could think of was using a subreport with unique query string for every possible combination of empty and not empty collections, which would create A LOT of overhead for further development. Is it somehow possible to create a parameter that can either be empty or include a WHERE clause with $X{} parameter? Thanks!
×
×
  • Create New...