# Epicor SSRS Report Template Checklist > Source: https://netray.co/tools/epicor-ssrs-report-template-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A pre-release checklist for custom Epicor SSRS reports covering report style, data definition, layout, parameters, security and testing. ## Category epicor ## Erp Epicor Kinetic ## Audience - Epicor report developer - Epicor consultant - ERP analyst ## Tool **Kind:** checklist **Groups:** #### Requirements and setup **Items:** **Text:** Business owner, audience and delivery method (print, email, dashboard) are named **Critical:** true Existing standard report checked first, so a copy is really needed Report ID, description and version note agreed using a naming convention **Text:** Source report style cloned instead of editing the standard one **Critical:** true **Text:** Developer works in the Test environment, not Live **Critical:** true Sample documents (long, short, multi page, foreign currency) identified for testing #### Data definition **Items:** Report data definition created or cloned with only the tables needed **Text:** Custom UD fields or BAQ joins added to the data definition and tested **Critical:** true Report data refreshed after any change to the data definition Calculated fields moved into the data definition or BAQ where possible **Text:** Row counts compared between the report and the on screen document **Critical:** true Nulls and zero values handled so no blank labels appear #### Layout and formatting **Items:** Page size, orientation and margins match the printer or PDF target Company logo and legal entity details come from data, not a fixed picture Header repeats on every page for multi page tables **Text:** Long descriptions wrap or can grow without overlapping the next row **Critical:** true Number, currency and date formats follow the site and customer locale Page numbers use Page X of Y **Text:** Subtotals and totals reconcile to the transaction in the ERP **Critical:** true #### Parameters and runtime **Items:** Parameter defaults are sensible and do not run for all history Mandatory parameters are marked so the user cannot run an empty report Report runs through the correct report style for each document type **Text:** Run time with a realistic data volume is acceptable **Critical:** true Email and print routing tested if the report is sent automatically #### Security and release **Items:** **Text:** Menu or action access granted by security group, not to everyone **Critical:** true **Text:** No sensitive costs or margins appear on customer facing output **Critical:** true Report exported from Test and imported to Live through change control Printer or PDF output verified in Live with a real document Rollback plan: previous style kept and not deleted Support notes and screenshots stored with the change record **Scoring Note:** Critical items should all be checked before release. Report builder screens and names vary by Kinetic version, so adapt wording to your environment. ## Content **Intro:** Custom SSRS reports are among the most frequent Epicor changes, and also among the most frequently reworked. Use this checklist before sending a report to Live to catch the problems users usually find first. **Sections:** #### How to use the checklist **Body:** Work through the groups in order and tick items as you verify them. Export the completed list to PDF or Excel and attach it to the change request. The groups follow the real order of a report project: agree the requirement, shape the data, design the layout, test parameters and runtime, and then release with security in place. Items marked critical are the ones that most often cause an incident or a rework. #### Where reports usually go wrong **Body:** Reports break on edge cases more than on the happy path. A line description longer than expected overlaps the next row, a foreign currency order shows the wrong symbol, or a document with fifty lines runs past one page and loses its header. Test with documents that are deliberately awkward: longest description, many lines, foreign currency, zero value lines and missing optional fields. Compare totals with the screen and with a BAQ, not by eye. **Bullets:** - Test the longest description in your data - Test a multi page document - Test a foreign currency document - Test with a user who has limited security #### Data definition discipline **Body:** The report data definition is the contract between Epicor and the layout. Keep it as small as the report needs, because every extra table slows down the run. Put joins, formulas and filters in the data definition or a BAQ, so the layout only formats. When you add custom fields, refresh the report data and confirm the field arrives with real values, not just the column name. #### Security and promotion **Body:** A report copy often exposes more than the original, for example unit cost on a quote. Check what each audience sees. Promote through the same change control as any other change and keep the original style available so you can revert. Record who approved the output, as users will quote this version later. **Cta:** If report requests keep piling up, Netray can discuss a read-only assistant that answers common data questions directly from your ERP so fewer custom reports are needed. **Faq:** #### Should I edit the standard Epicor report style or copy it? **Answer:** Copy it. Editing the standard style makes upgrades harder and removes your fallback. Clone the style with a new ID, change the copy, and keep the original available for comparison and rollback. #### Why does my SSRS report show no data in Live? **Answer:** Common causes are a report data definition not refreshed after a change, a parameter filter excluding all rows, missing security on the underlying tables, or a layout referencing a field that is empty in Live. Compare the data set in both environments. #### Do I need a BAQ for an SSRS report? **Answer:** Not always. Standard reports use their own data definitions, but a BAQ is a common way to add joins and calculated fields for a custom data source. Choose whichever keeps the logic in one tested place. #### How do I check report totals are correct? **Answer:** Compare the report total with the transaction on screen and with an independent BAQ or SQL query for the same document. Test at least one multi page and one foreign currency document, since totals often fail there first. ## Search terms epicor ssrs report template, epicor custom report checklist, epicor report builder ssrs, epicor ssrs best practices, epicor report style, epicor ssrs parameters, epicor ssrs testing, epicor kinetic custom reports --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json