New post
Question
· Feb 26

Trakcare parameter to Jreport

#InterSystems Reports (Logi) #TrakCare

Hi ,

          I am creating a report on Trakcare with the help of Jreport. But the date parameter from trakcare is not reading on Jreport and the report is blank.

If I hardcode the date on Jreport,it is displaying on Trakcare but not taking report from Trakcare.

Parameter used on report manager on Trakcare is $g(%request.Data("DateFrom",1)).

Can anyone please tell me any change of settings on Trakcare or Jreport will help to work ? 

 

Thanks for the help

 

Jude

Product version: IRIS 2023.3
Discussion (8)2
Log in or sign up to continue
Timo Lindenschmid · Mar 6

Hi Jude, better option to get help is to open an iService ticket to get specialist help here.

Just a high level:

1. make sure that the parameter you want to use are added via the URL expression on the mun item used to call the report  

2. then the parameter can used in the report manager definition and assigned

Also make sure the parameter id in the format expected. IRIS dates are usually in $Horolog format and not in yyyy-mm-dd as might be expected by LogiReports.

0 0
Steven Potashnyk · Mar 11

There is not enough infromation in the post to really give you guidance.   As Timo mentioned iService ticket may be a better approach to get help. A few things to look at

  1. Check to see what values are being saved in the print history.  if you can see values populating in P1-P9 then Trakcare technically should pass them off to Logi.
  2.  Check the Logi reports configuration in Trakcare. Ensure its configured correctly for the environment.
  3. Put some debug into the stored procedure being called from the Logi Catalogue to see if the parameters are being passed.
0 0
Steven Potashnyk · Mar 13

You will find the String "07/03/2025" is not recognised as a date when using a JDBC connection :

You will need to pass Logical or the date as an ODBC/JDBC with a format of "yyyy-mm-dd"

-- Passing Date as String : '07/03/2025'
select * 
from SQLUser.PA_Adm
where PAADM_AdmDate = '07/03/2025'
-- ERROR
--SQL Error [400] [S1000]: [SQLCODE: <-400>:<Fatal error occurred>]
--[Error: <<ZODAT>%rtpcHelper1+1^%sqlcq.Config.cls43.1>]
--[Location: <ServerLoop>]
--[%msg: <Error: '07/03/1025' is an invalid ODBC/JDBC Date value>]

--Passing Date as String : '2025-01-01' (ODBC/JDBC format)
select * 
from SQLUser.PA_Adm
where PAADM_AdmDate = '2025-01-01'
--Executes without error

--Passing Date as Logical : +$H (67278)
select * 
from SQLUser.PA_Adm
where PAADM_AdmDate = +$H
--Executes without error
0 0
Luke Evers · Mar 17

Hi Jude,

We have further explored the possibilities of passing date parameters with Logi Reports/JReports, which are built on Queries, with TrakCare.
 
The date value of the parameter is now being passed to the Logi Reports from TrakCare, and it is filtering the results as expected. This was tested using the report "Logons For Date Range" in UAT (your organizations environment).
 
Here are the changes we have made:
 1.When queries are used, the Logi Report parameter name and the TrakCare report definition parameter name must match.
2.The date format for parameters in the report must align with the date format passed from TrakCare (dd/MM/yyyy).
 
As previously mentioned, while Logi Report supports the concept of building queries from the catalogue, this has not been tested or considered in the communication between TrakCare and the Logi Report Server. 
Therefore, the resolution time for any Logi Report issues may take longer and will be handled on a best-effort basis.

Thanks,
Luke

0 0