Relations Full Name field selection generates error in custom reports

Modified on Tue, 12 Jun 2012 09:42 by CAREWare Help Desk — Categorized as: FAQ

The use of the relations report type field selection RLT Full Name generates the following error when the report is run. This error is reproducible in builds 594 to 627. TTP item is closed. Refer to item number 1953 for additional information regarding all relation fields in custom reports. 

The multi-part identifier "rlt_ClientList.map_cl_middle_name" could not be bound. The multi-part identifier 
"rlt_ClientList.map_cl_last_name" could not be bound. The multi-part identifier "rlt_ClientList.map_cl_first_name" 
could not be bound. The multi-part identifier "rlt_ClientList.map_cl_middle_name" could not be bound. The multi-part 
identifier "rlt_ClientList.map_cl_last_name" could not be bound. The multi-part identifier 
"rlt_ClientList.map_cl_first_name" could not be bound. The multi-part identifier "rlt_ClientList.map_cl_last_name" 
could not be bound. The multi-part identifier "rlt_ClientList.map_cl_first_name" could not be bound. 
The multi-part identifier "rlt_ClientList.map_cl_middle_name" could not be bound. The multi-part identifier 
"rlt_ClientList.map_cl_last_name" could not be bound. The multi-part identifier "rlt_ClientList.map_cl_first_name" 
could not be bound. 
The multi-part identifier "rlt_ClientList.map_cl_middle_name" could not be bound. The multi-part identifier 
"rlt_ClientList.map_cl_dob" could not be bound. The multi-part identifier "rlt_ClientList.map_cl_dob" 
could not be bound. at jProgBusiness.jBusiness.jSQLDatasetFillHelper.jTableDescriptor.FillTable(DataSet TheDataset, 
IDbConnection Connection, Int32 XMLHandle, jReportSpecification reportSpecification, jKeyLabelPair[] domains) at 
jProgBusiness.jBusiness.jSQLDatasetFillHelper.FillDataset(jServiceManager ServiceManager, ConnectionType ConnectionType, 
Boolean closeConnectionAfterUse, jReportSpecification reportSpecification, jKeyLabelPair[] domains)

This bug was found in build594
This bug was fixed in build629
TTP #1952

Back to Bugs

Back to Frequently Asked Questions