2.6 to 3.0 Data (Endorsement) Conversion issue?

Discussions related to Crystal Reports development.

Moderator: Lisa Ennis

Post Reply
Posts: 22
Joined: Mon Nov 17, 2014 6:14 pm

2.6 to 3.0 Data (Endorsement) Conversion issue?

Post by cgriffin » Tue Jul 07, 2015 6:27 pm

Good afternoon,

In 2.6 in the GUI and database both reflect endorsement charges.

However, in 3.0 both reflect endorsement charges in the GUI, but not in the expected places in 3.0

File ‘X’ is reflecting endorsement charges in the 3.0 database, specifically:

Endorsement (XML) field data:
AdditionalTitleCharge Guid
PolicyID (GUID)

However, file ‘Y’ is not reflecting any data whatsoever in the above XML field.

Do you know of any issues?

Should we be looking in another place?

Thank you,

Posts: 1007
Joined: Wed Jan 15, 2014 3:50 pm
Location: Raleigh, NC

Re: 2.6 to 3.0 Data (Endorsement) Conversion issue?

Post by BobRichards » Wed Jul 08, 2015 4:35 pm

If I understand your question, you are saying that you are writing directly to the Select SQL tables: You are not allowed to write nor modify any SoftPro installed data table.

Much of the information is maintained in the order and tables may be used for reading only.
Bob Richards, Software Developer, SoftPro

Lisa Ennis
Posts: 81
Joined: Thu Sep 11, 2008 1:57 pm

Re: 2.6 to 3.0 Data (Endorsement) Conversion issue?

Post by Lisa Ennis » Wed Jul 08, 2015 4:48 pm

I believe the data Colin is looking at data stored in the pt.TitleCharge. Data writes to this table when a transaction is initially posted. If that table does not have what you need, you may need to join back to the Title and Endorsement tables in the pfm schema using the ChargeSource in the pt.RevenueDetail table.
Lisa Ennis
Report Developer

Post Reply