SSRS Reports: Precision Design

Why SSRS is still the backbone of F&O reporting

Precision design vs auto design

Every SSRS report in F&O uses one of two design approaches:

Auto design = quick internal lists. Precision design = polished external documents.

Aspect	Auto Design	Precision Design
Layout creation	Generated automatically from dataset fields	Manually designed in RDLC designer (Visual Studio)
Control over placement	Minimal — columns render in order	Complete — every textbox, image, line is placed precisely
Use case	Simple tabular lists, internal reports	Invoices, cheques, packing slips, any externally-facing document
Grouping / subtotals	Basic grouping supported	Full control: nested groups, conditional visibility, sub-reports
Effort to build	Low — drag dataset, done	Higher — manual layout, expressions, formatting
Modification approach	Change dataset or query	Edit .rdl XML or use VS designer

💡 Exam tip: When to pick which design

The exam tests this distinction. Rule of thumb:

• “The report must match an existing printed form layout exactly” → Precision design
• “The report shows a simple list of records for internal review” → Auto design
• “The customer invoice must include a company logo at specific coordinates” → Precision design
• “A developer needs a quick data dump to verify business logic” → Auto design

Building an SSRS report: the full pipeline

Here’s the end-to-end flow for creating a custom SSRS report:

┌─────────────┐    ┌─────────────┐    ┌──────────────┐    ┌──────────────┐
│ 1. Contract  │───▶│ 2. RDP      │───▶│ 3. Report    │───▶│ 4. Menu Item │
│    Class     │    │    Class    │    │    Design    │    │   + Privilege │
│ (parameters) │    │ (data logic)│    │  (VS .rdl)   │    │  (security)  │
└─────────────┘    └─────────────┘    └──────────────┘    └──────────────┘
                                              │
                                    ┌─────────┴─────────┐
                                    │ 5. Deploy to       │
                                    │    Report Server   │
                                    └────────────────────┘

Step 1: Contract class (parameters)

The contract class defines what the user enters before running the report.

[DataContractAttribute]
class PFProductionReportContract
{
    TransDate   fromDate;
    TransDate   toDate;
    ProdPoolId  prodPool;

    [DataMemberAttribute('FromDate'),
     SysOperationLabelAttribute(literalStr("From date"))]
    public TransDate parmFromDate(TransDate _fromDate = fromDate)
    {
        fromDate = _fromDate;
        return fromDate;
    }

    [DataMemberAttribute('ToDate'),
     SysOperationLabelAttribute(literalStr("To date"))]
    public TransDate parmToDate(TransDate _toDate = toDate)
    {
        toDate = _toDate;
        return toDate;
    }

    [DataMemberAttribute('ProdPool'),
     SysOperationLabelAttribute(literalStr("Production pool"))]
    public ProdPoolId parmProdPool(ProdPoolId _prodPool = prodPool)
    {
        prodPool = _prodPool;
        return prodPool;
    }
}

ℹ️ Key decorators explained

Decorator	Purpose
[DataContractAttribute]	Marks the class as a serialisable data contract
[DataMemberAttribute('Name')]	Exposes the property as a parameter with a serialisation name
[SysOperationLabelAttribute]	Sets the label shown to users in the parameter dialog
[SysOperationGroupAttribute]	Groups parameters visually in the dialog
[SysOperationDisplayOrderAttribute]	Controls the order parameters appear

Step 2: RDP class

The RDP class runs the actual data retrieval and business logic.

[SRSReportParameterAttribute(classStr(PFProductionReportContract))]
class PFProductionReportDP extends SRSReportDataProviderBase
{
    PFProductionReportTmp tmpTable;

    [SRSReportDataSetAttribute(tableStr(PFProductionReportTmp))]
    public PFProductionReportTmp getTmpTable()
    {
        select tmpTable;
        return tmpTable;
    }

    public void processReport()
    {
        PFProductionReportContract contract = this.parmDataContract()
            as PFProductionReportContract;

        TransDate fromDate = contract.parmFromDate();
        TransDate toDate   = contract.parmToDate();

        ProdTable prodTable;

        while select prodTable
            where prodTable.SchedDate >= fromDate
               && prodTable.SchedDate <= toDate
        {
            tmpTable.ProdId    = prodTable.ProdId;
            tmpTable.ItemId    = prodTable.ItemId;
            tmpTable.QtyGood   = prodTable.QtyGood;
            tmpTable.SchedDate = prodTable.SchedDate;
            tmpTable.insert();
        }
    }
}

ℹ️ Sophie asks: Why a temp table and not a direct query?

Sophie Chen asks Elena: “Why can’t the report just read from ProdTable directly?”

Elena explains:

• Business logic — you often need calculated fields, joined data from multiple tables, or conditional logic that a simple query can’t express
• Performance — the temp table is populated once, then the report reads from it. The live table isn’t locked during rendering
• Isolation — the report’s data snapshot is frozen at execution time. No dirty reads mid-render
• Reusability — the same RDP class can feed multiple report designs

“For simple reports with no logic, use an AOT query instead,” Elena adds. “But most real-world reports need the RDP class.”

Step 3: Report design in Visual Studio

Task	How
Add report to project	Right-click project → Add → New Item → Report
Add dataset	In report, add dataset → select RDP class or query
Auto design	Right-click Designs → Add Auto Design → fields render automatically
Precision design	Right-click Designs → Add Precision Design → opens RDLC designer
Expressions	Use =Fields!FieldName.Value for data, =Parameters!Param.Value for parameters
Grouping	In precision design, add row groups for subtotals and page breaks

Step 4: Menu item and security

Every report needs a menu item output to be accessible:

Element	Purpose
Menu item output	The entry point — Object = ReportName, ObjectType = SSRSReport
Privilege	Grants access to the menu item
Duty	Contains the privilege
Role	Contains the duty — users with this role can run the report

Step 5: Deploying reports

Method	When
Build + Deploy from VS	Development environment — right-click report → Deploy
Incremental sync	After code deployment — new or changed reports deploy automatically
PowerShell	Force-refresh on report server for stubborn deployments
Admin page	System Administration → Setup → Deploy reports

💡 Exam tip: Report deployment troubleshooting

If a report doesn’t appear after deployment:

1. Check the deploy log in Visual Studio output window for errors
2. Verify the report’s menu item exists and is correctly linked
3. Confirm the user’s security role includes the privilege
4. Run Deploy reports from System Administration if incremental sync missed it
5. Clear browser cache — sometimes old report parameter dialogs are cached

Extending standard reports

You should never modify a standard report directly (that’s overlayering). Instead, use extensions.

Extension approaches — from lightest touch to full replacement

Extension approach	What it does	When to use
Delegate handler	Subscribe to report events to modify data or parameters	Add calculated fields, filter data, change default parameters
Custom RDP extending standard	Create a new RDP class that extends the standard one	Need to add new data sources or heavy custom logic
Report format customisation	Duplicate the .rdl design, modify layout, register as custom	Change visual layout (logo placement, column order, totals)
Print management override	Configure Print Management to use your custom report instead of standard	Replace the standard invoice/packing slip with your version

ℹ️ Scenario: Elena extends the sales invoice

PacificForge needs the standard sales invoice to include a “Production Batch Number” column. Elena’s approach:

1. Creates a new report design — duplicates the standard SalesInvoice precision design
2. Extends the RDP class — adds a delegate handler to the standard SalesInvoiceDP that populates the batch number field
3. Registers the custom design — creates a new report with the modified layout
4. Configures Print Management — sets the custom report as the default for sales invoices

“We never touch the standard report,” Elena tells compliance officer Kenji. “If Microsoft updates it, our extension still works because we’re subscribing to events, not modifying source.”

Print Management

Print Management decides which report design to use when printing documents like invoices, purchase orders, and packing slips.

Concept	Detail
Report format	Maps a document type to a specific report design
Conditions	Print different designs based on customer, vendor, or other criteria
Destinations	Screen, printer, email, file — configurable per document type
Override hierarchy	Module defaults → Account-level → Transaction-level

---

Question

What is the difference between precision design and auto design in SSRS?

Click or press Enter to reveal answer

Answer

Auto design generates the layout automatically from dataset fields — good for quick tabular lists. Precision design gives you full manual control over every element's position — required for pixel-perfect documents like invoices and cheques. Precision design uses the RDLC designer in Visual Studio.

Click to flip back

Question

What are the three main components of an RDP-based SSRS report?

Click or press Enter to reveal answer

Answer

1) Contract class — defines user parameters (decorated with [DataContractAttribute]). 2) RDP class — runs processReport() to populate a temp table with data. 3) Temp table — the bridge between X++ logic and the SSRS report design. The report's dataset binds to this table.

Click to flip back

Question

How do you make a custom SSRS report accessible to users?

Click or press Enter to reveal answer

Answer

Create a menu item output (Object = report name, ObjectType = SSRSReport). Create a privilege that grants access to the menu item. Add the privilege to a duty, and the duty to a role. Users with that role can then see and run the report.

Click to flip back

Question

How should you modify a standard SSRS report in F&O?

Click or press Enter to reveal answer

Answer

Never modify directly (no overlayering). Use extensions: subscribe to report delegate events for data changes, extend the RDP class for new logic, duplicate and customise the report design for layout changes, then configure Print Management to use your custom version.

Click to flip back

---

Knowledge Check

Elena needs to create a production report that calculates weighted average costs across multiple warehouses with conditional discount logic. Which data source approach should she use?

AAOT query with computed columnsBReport Data Provider (RDP) classCDirect table binding in the report datasetDEntity store aggregate measurement

Check Answer

Knowledge Check

PacificForge's customer invoices must include a company logo at exact coordinates and match a government-mandated layout. Which report design type should Elena use?

AAuto design with custom stylingBPrecision design in RDLC designerCPower BI paginated reportDElectronic Reporting format

Check Answer

Knowledge Check

Vik needs to add a custom field to the standard purchase order report without overlayering. What is the correct approach?

AEdit the standard report's .rdl file directly in Visual StudioBModify the standard RDP class to add the new fieldCCreate an extension: duplicate the design, extend the RDP via delegate handler, configure Print ManagementDAdd the field directly to the standard temp table

Check Answer

Next up: Power BI & Analytical Workspaces — embedding interactive dashboards and KPI tiles directly in F&O.