Sage 100

Post this on Sage City and you will likely get a developer response.  (This is the type of question they tend to answer).

It works for me.  I added a "TEST DATE" UDF to PR_Employee and mapped the same to PR_CheckHistoryReportWrk.  I added PR_Employee.UDF_TEST_DATE to emplyee maintenance and added today's date.  I then added PR_CheckHistoryReportWrk.UDF_TEST_DATE beyween @EmployeePrint and @EmployeeStatus in Group Header 5 of the Payroll, Check History Report.  The date entered in Employee Maintenance  UDF_TEST_DATE displyed on the report.

It works for me.  I added a "TEST DATE" UDF to PR_Employee and mapped the same to PR_CheckHistoryReportWrk.  I added PR_Employee.UDF_TEST_DATE to emplyee maintenance and added today's date.  I then added PR_CheckHistoryReportWrk.UDF_TEST_DATE beyween @EmployeePrint and @EmployeeStatus in Group Header 5 of the Payroll, Check History Report.  The date entered in Employee Maintenance  UDF_TEST_DATE displyed on the report.

But that's not what I was doing.  I was trying to add the standard field BIRTH DATE to the report, not an employee UDF. (And I'm doing this on my Sage 100, so Roles are OK.)

It works for me.  I added a "TEST DATE" UDF to PR_Employee and mapped the same to PR_CheckHistoryReportWrk.  I added PR_Employee.UDF_TEST_DATE to emplyee maintenance and added today's date.  I then added PR_CheckHistoryReportWrk.UDF_TEST_DATE beyween @EmployeePrint and @EmployeeStatus in Group Header 5 of the Payroll, Check History Report.  The date entered in Employee Maintenance  UDF_TEST_DATE displyed on the report.

Mine works passing the PR_Emplyee.Birthdate to PR_CheckHistoryReportWrk.UDF_BirthDate. 

But that's not what I was doing.  I was trying to add the standard field BIRTH DATE to the report, not an employee UDF. (And I'm doing this on my Sage 100, so Roles are OK.)

It works for me.  I added a "TEST DATE" UDF to PR_Employee and mapped the same to PR_CheckHistoryReportWrk.  I added PR_Employee.UDF_TEST_DATE to emplyee maintenance and added today's date.  I then added PR_CheckHistoryReportWrk.UDF_TEST_DATE beyween @EmployeePrint and @EmployeeStatus in Group Header 5 of the Payroll, Check History Report.  The date entered in Employee Maintenance  UDF_TEST_DATE displyed on the report.

And you actually saw data on your report?  I can create it and add it to the report just fine, but then it shows no data when I run the report from the standard report on the menu.

Mine works passing the PR_Emplyee.Birthdate to PR_CheckHistoryReportWrk.UDF_BirthDate. 

But that's not what I was doing.  I was trying to add the standard field BIRTH DATE to the report, not an employee UDF. (And I'm doing this on my Sage 100, so Roles are OK.)

It works for me.  I added a "TEST DATE" UDF to PR_Employee and mapped the same to PR_CheckHistoryReportWrk.  I added PR_Employee.UDF_TEST_DATE to emplyee maintenance and added today's date.  I then added PR_CheckHistoryReportWrk.UDF_TEST_DATE beyween @EmployeePrint and @EmployeeStatus in Group Header 5 of the Payroll, Check History Report.  The date entered in Employee Maintenance  UDF_TEST_DATE displyed on the report.

Yes.  if you look at the screen shot in my previous post, the "6/17/9161" is PR_Employee.Birthdate from employee DLH (apparently some old guy).  Attached to this post is a screen shot of the pick screen, the Crystal report, and an export of the UDF,  Mine is v2022 standard and no product updates.

And you actually saw data on your report?  I can create it and add it to the report just fine, but then it shows no data when I run the report from the standard report on the menu.

Mine works passing the PR_Emplyee.Birthdate to PR_CheckHistoryReportWrk.UDF_BirthDate. 

But that's not what I was doing.  I was trying to add the standard field BIRTH DATE to the report, not an employee UDF. (And I'm doing this on my Sage 100, so Roles are OK.)

It works for me.  I added a "TEST DATE" UDF to PR_Employee and mapped the same to PR_CheckHistoryReportWrk.  I added PR_Employee.UDF_TEST_DATE to emplyee maintenance and added today's date.  I then added PR_CheckHistoryReportWrk.UDF_TEST_DATE beyween @EmployeePrint and @EmployeeStatus in Group Header 5 of the Payroll, Check History Report.  The date entered in Employee Maintenance  UDF_TEST_DATE displyed on the report.

Ooh, son of a biscuit - it's that stupid Report Subsection way Sage has of doing some of their reports.  The value shows up in SOME of the records - just not the one I happened to be using on the line I was exporting.

Sorry to make you go through all of that, Doug.  

Yes.  if you look at the screen shot in my previous post, the "6/17/9161" is PR_Employee.Birthdate from employee DLH (apparently some old guy).  Attached to this post is a screen shot of the pick screen, the Crystal report, and an export of the UDF,  Mine is v2022 standard and no product updates.

And you actually saw data on your report?  I can create it and add it to the report just fine, but then it shows no data when I run the report from the standard report on the menu.

Mine works passing the PR_Emplyee.Birthdate to PR_CheckHistoryReportWrk.UDF_BirthDate. 

But that's not what I was doing.  I was trying to add the standard field BIRTH DATE to the report, not an employee UDF. (And I'm doing this on my Sage 100, so Roles are OK.)

It works for me.  I added a "TEST DATE" UDF to PR_Employee and mapped the same to PR_CheckHistoryReportWrk.  I added PR_Employee.UDF_TEST_DATE to emplyee maintenance and added today's date.  I then added PR_CheckHistoryReportWrk.UDF_TEST_DATE beyween @EmployeePrint and @EmployeeStatus in Group Header 5 of the Payroll, Check History Report.  The date entered in Employee Maintenance  UDF_TEST_DATE displyed on the report.