Clarity Service Management

Expand all | Collapse all

Jasper Report - cr.customer_organization_name not usable for filtering

  • 1.  Jasper Report - cr.customer_organization_name not usable for filtering

    Posted 11-24-2018 02:00 AM

    Hello,

     

    I am struggling with Jusper Report during Domain creation (using Domain Designer).

    Everything works fine:

    1. data source created and tested

                   - Type: JDBC Data Source;

                   - JDBC Driver: com.ddtek.jdbc.openaccess.OpenAccessDriver

                   2. New Domain created using Domain Designer

                   -  table casd_cr choosed

                   -   fileds from casd_cr choosed – like ref_num; status; customer_organization_name, etc…

    1. Ad hoc view based on this domain successfully created
    2. Report based od Ad hoc successfully created…

     

    But, if I want to create pre-filter (in domain designer) based on customer_organization_name, OR fields with combo_name, I got error message.

     

    com.jaspersoft.commons.dataset.DataSetException: Exception calling JRDataSource.next() for query select top 2147483647 "casd_cr"."assignee_organization_name" as "casd_cr_assignee_organization_name" from "casd"."cr" "casd_cr" group by "casd_cr"."assignee_organization_name" order by "casd_cr_assignee_organization_name"

     

    … Caused by: java.sql.SQLException: [DataDirect][OpenAccess SDK JDBC Driver][OpenAccess SDK SQL Engine]AHD12008:Attribute casd_cr_customer_organization_name referenced by Majic SQL query not found in object(s) cr at casd_cr_customer_organization_name…

     

    (whole error message attached in txt file)

     

    The same result I got, if I try to use this field for filtering on Ad Hoc View.

    Attachment(s)

    zip
    error.txt.zip   2K 1 version


  • 2.  Re: Jasper Report - cr.customer_organization_name not usable for filtering

    Posted 11-27-2018 02:01 PM

    hiya Radek,

     

    Which version of SDM is being used here?   We started supporting only one out of the box domain (Incident Management) in 17.1 release. We were not supporting domains prior to this release.


    _R



  • 3.  Re: Jasper Report - cr.customer_organization_name not usable for filtering

    Posted 11-27-2018 02:38 PM

    Hi....SDM 17.0 and Jasper reports 6.3.0



  • 4.  Re: Jasper Report - cr.customer_organization_name not usable for filtering

    Posted 11-27-2018 03:11 PM

    Yea, unfortunately, we do not have support for domains in that release yet.  With 17.1 we provide one domain, which might give some clues in creating custom ones

     

    _R



  • 5.  Re: Jasper Report - cr.customer_organization_name not usable for filtering

    Posted 12-04-2018 04:29 PM

    Hi, I updated to SDM 17.1 and Jasper 6.4.3. 

    Where can I find the provided domain? OOB I do not see a sigle different :/



  • 6.  Re: Jasper Report - cr.customer_organization_name not usable for filtering

    Posted 12-04-2018 04:35 PM