Error when saving new custom report that has no filter

Modified on Thu, 10 May 2012 16:47 by CAREWare Help Desk — Categorized as: FAQ

When attempting to save a new custom report that has no filter applied, an error message appears saying the report cannot be saved. However the report is actually saved. Error is: 
Source: Object reference not set to an instance of an object.
   at jProgBusiness.jReports.jCustomReportOperations.addCustomFieldIndexesIfNecessary(jReportFilter reportFilter)
   at jProgBusiness.jReports.jCustomReportOperations.insertSpecification(String LoginToken, 
String DomainPK, jReportSpecification specification, jUser user, Boolean isForReportCopy)
   at jProgBusiness.jReports.jCustomReportOperations.saveReportSpecification(String LoginToken, 
jReportSpecification specification, String domainPK)
   at jProgBusiness.jBusiness.jBusinessRemote.CRO_Save_Report_Specification(String SessionToken, jReportSpecification specification)
An error occurred while attempting to save a custom report specification.

If attempting to save the report again, this is the error: 
Source: jProgBusiness - Violation of PRIMARY KEY constraint 'PK_cw_report_specification'. 
Cannot insert duplicate key in object 'dbo.cw_report_specification'.The statement has been terminated. 
INSERT INTO cw_report_specification ( rpr_sp_pk , rpr_sp_name , rpr_sp_rpr_tp_rfk , rpr_sp_fld_sl_fk , rpr_sp_flt_fk , 
rpr_sp_dmn_fk , rpr_sp_is_crosstab , rpr_sp_is_readonly , rpr_sp_last_updated) VALUES (@rpr_sp_pk , @rpr_sp_name , 
@rpr_sp_rpr_tp_rfk , @rpr_sp_fld_sl_fk , @rpr_sp_flt_fk , @rpr_sp_dmn_fk , @rpr_sp_is_crosstab ,@rpr_sp_is_readonly , 
@rpr_sp_last_updated)
cw_report_specification.rpr_sp_pk=8fd04713-14bb-4643-b457-10d3d1cc4b2ccw_report_specification.rpr_sp_name=PartBcw_report_specification.
rpr_sp_rpr_tp_rfk=01cw_report_specification.
rpr_sp_fld_sl_fk=a5b27935-36c9-43e8-9b51-9f188df8d5b6cw_report_specification.rpr_sp_flt_fk=
cw_report_specification.rpr_sp_dmn_fk=ffffffff-0000-0000-0000-000000000002,
cw_report_specification.rpr_sp_is_crosstab=Falsecw_report_specification.rpr_sp_is_readonly=False    
at jProgBusiness.jReports.jCustomReportOperations.saveReportSpecification
(String LoginToken, jReportSpecification specification, String domainPK)   
at jProgBusiness.jBusiness.jBusinessRemote.CRO_Save_Report_Specification(String SessionToken, jReportSpecification specification)
An error occurred while attempting to save a custom report specification.

In spite of the error messages, the report is saved.

This bug was found in build580
This bug was fixed in build596
TTP #1898

Back to Bugs

Back to Frequently Asked Questions