Sage 100

For those of you using / testing Sage 100 2018 Payroll -- is there any way now to create custom Crystal Reports from Sage payroll data now that everything is encrypted? #2018pioneer

You have to add it to the menu (can't be outside of Sage) and it will ask if you want to add a special temp file when you're adding to the menu. That special temp file has unencrypted info in it. Only has the data while the report is running, like other temp files.

So how do you develop the report to begin with if you can't see the data? Do you have to rough in the report without being able to see a copy of the initial output - attach it to the menu then run/preview from Sage custom reports?

I would say that sounds about right...

This is going to catch some people by surprise

And not a good surprise

Data File Display and Maintenance Personally identifiable employee information is not visible in Data File Display and Maintenance. Report Manager When you run the Report Manager Menu Wizard to add a report, if you select Payroll from the Module list, you'll have the option to include a PII worktable in the report. If you include the worktable, it will be populated with unencrypted data when the report is run from the report menu. The ""Allow Viewing, Printing and Editing of Highly Sensitive Personally Identifiable Information"" security event in Role Maintenance determines whether Social Security numbers, bank account numbers, and bank routing numbers are masked. 9Sage 100PayrollUserGuide AdditionalSecurityforPersonallyIdentifiableInformation If you include the PII worktable, you must link the work table to the existing report tables and insert the PII data into the report. Anyone who has rights to run the report will see the PII data. As with the standard reports, the ability to view Social Security numbers, bank account numbers, and bank routing numbers is based on the ""Allow Viewing, Printing and Editing of Highly Sensitive Personally Identifiable Information"" security event in Role Maintenance. External Reporting through ODBC Personally identifiable employee information cannot be accessed via external reporting using an ODBC data source. The encrypted fields will be blank.

You can pull check history info or fields like hire date without an issue but can't pull info like SS#, Birth Date using Crystal, at least from outside the application.