Microsoft Dynamics AX 2012 报告编程模型升级：SysOperation框架与SSRS集成

2012

需积分: 9 62 浏览量更新于2024-07-19 收藏 974KB PDF 举报

本篇文档是关于Microsoft Dynamics AX 2012的报告编程模型白皮书，主要关注于如何有效地利用Microsoft SQL Server Reporting Services (SSRS) 作为主要的报表平台。在AX 2012中，原有的RunBase模型已经被SysOperation框架所取代，这为报表开发带来了新的编程策略。 **概述：** 文档首先介绍了报告编程模型的核心概念，强调了它在Microsoft Dynamics AX 2012中的重要性，旨在提供一种高效、可维护的报告开发方法。通过使用SysOperation框架，开发者可以更好地组织和管理业务逻辑，确保报表与系统其他部分的无缝集成。 **概念与用例分析：** - **概念概述**：文档详细解释了新的报告编程模型如何基于SysOperation框架设计，包括如何处理数据源、数据处理逻辑以及报表呈现的过程。开发者可以理解到，这个模型更加注重代码结构的清晰性和性能优化。 - **用例研究**： - **用例1：临时表与业务逻辑** - 当报告调用者需要在报告渲染过程中使用临时表来支持业务逻辑时，临时表Marshaller的使用被演示。开发者应了解如何适当地创建和管理这些临时表，以避免潜在的数据冗余或性能问题。 - **用例2：报告调用上下文** - 报告调用者上下文（如一个包含业务逻辑的类）的使用也被讨论，以便在处理报表时能灵活地复用和扩展业务规则。 **最佳实践与注意事项：** - **最佳实践**：文档提供了编写高质量报告的建议，包括代码组织、异常处理、性能优化以及与系统其他模块的良好交互等。 - **避免的实践**：列举了一些常见的开发陷阱，如过度依赖临时表、忽视数据一致性、不恰当的多线程处理等，帮助开发者避免这些问题。 **打印管理和预处理：** 这部分着重讲解了如何管理报告的打印流程，以及如何在运行前对报表进行预处理，比如设置参数、执行数据加载等，以确保最终用户获得一致且高效的打印体验。这篇文档为Microsoft Dynamics AX 2012的开发者提供了一个全面的指导，让他们能够利用新报告编程模型提高报表开发的效率和质量，同时遵循良好的编程习惯和性能优化策略。

REPORT PROGRAMMING MODEL FOR MICROSOFT DYNAMICS AX 2012

Use case

Developer action

Unit testing

artifact

A report needs to change the

name of the report design used at

run time.

Extend the SrsReportRunController class, override

the preRunModifyContract method, and then provide

a different name for the report in the

SrsReportDataContract class.

Test the controller.

Patterns for converting reports

Report patterns emerged when Microsoft Dynamics AX reports were converted for the current release.

The following table describes the report task, the programming model pattern, and a sample report

that uses the pattern in Microsoft Dynamics AX.

Report task

Report programming model pattern

Sample report

An RDP report needs simple

grouping and validation.

1. Create an RDP contract.

2. Implement the SysOperationValidatable class and

validation.

3. Do parameter grouping on the contract.

AssetDepreciationLedger

_IT

InventABC

An RDP report needs complex

grouping, such as horizontal,

vertical, nested, or multiple

groups.

Do parameter grouping by using Visual Studio tools for

Microsoft Dynamics AX.

A query-based, data method-

based, or OLAP-based report

needs grouping.

Do parameter grouping by using Visual Studio tools for

Microsoft Dynamics AX.

A custom field needs to be

created in the dialog box,

because, for example, the field

is not a report parameter.

The field is added based on

certain conditions.

The custom dialog box fields

are added, and the report

parameters are populated

based on them.

Create a UI builder:

1. Move the code in the addCustomCtrl method to the

UIBuilder.build method.

2. Move the getFromDialog method to the

UIBUilder.getFromDialog method, and populate

the contract.

3. Associate the UI builder class with the contract by

using the attribute

SysOperationContractProcessingAttribute(classs

tr(UIBuilderName),

SysOperationDataContractProcessingMode::Crea

teUIBuilderForRootContractOnly).

4. Optional: Create a controller, and if further

modification of the contract is required before the

report is run, add the logic to the

preRunModifyContract method.

AgreementFollowup

BOMPartOf

Code needs to react to dialog

box field events, such as when

a field is modified.

Create a UI builder:

 In postRun(), register override methods for field

events, and associate the fields events with

methods.

BudgetFundsAvailableUI

Builder

BudgetDetailsUIBuilder

A dialog box field needs to be

changed to have a different

button type than the default,

or a field needs to turn on a

flag on a grouping.

Create a UI builder:

 In the postBuild method, get the dialog box field

from the binding information, and change the field.

BudgetDetailsUIBuilder

REPORT PROGRAMMING MODEL FOR MICROSOFT DYNAMICS AX 2012

Report task

Report programming model pattern

Sample report

A helper class needs to turn

visibility of a report parameter

on or off, so that new custom

parameters can be added.

 Change the report parameter in the report design so

that it is hidden. The framework takes care of not

displaying the parameter in the Microsoft Dynamics

AX form.

A helper class needs to add a

caption for the report.

This task should be avoided. The framework uses the

label on the menu item that launches the report as a

caption.

For cases where the same report is used in multiple

reports, override the

controller.prePromptModifyContract method, and set

parmDialogCaption.

AgreementFollowUpCont

roller

A dialog box field needs to be

enabled or disabled based on

certain conditions.

Create the UI builder class:

1. Override the getFromDialog method if you want to

get the custom field value from the dialog box.

2. Override the postBuild method to enable or disable

fields.

CustAccountStatementI

A query is modified based on

the caller args before the UI is

rendered.

Create a controller:

 Override the prePromptModifyContract method.

AgreementFollowUpCont

roller

A query is modified before the

report is run.

Create a controller:

 Override the preRunModifyContract method.

AgreementFollowUpCont

roller

The report name needs to be

changed based on the caller

args or a UI parameter.

Create a controller:

 Override the preRunModifyContract method.

The helper class needs to use

print management.

Create a controller:

1. Override the run method.

2. Override the preRunModifyContract method, and

also override the prePromptModifyContract

method as needed.

CustInterestNoteHelper

The report parameter UI

should not be displayed.

Create a controller:

 In the main method, before the

controller.startOperation method, call

controller.parmShowDialog(false).

The report needs to use a

temp table from a caller.

Create a controller:

1. Get the temp table from the caller, and use the

SRSTmpTblMarshaller class to save the data.

2. Develop an RDP class to extract this data and perform

business logic processing.

Cheque_US

The report needs to use print

management.

See the "Print management" section.

SalesConfirm

PurchPackingSlip

ProjectInvoice

Using a temp table marshaller

Use of a temp table marshaller needs to be very limited. The following are the use cases for a temp

table marshaller.

Use case 1: The report caller has a temporary table that is needed as part of

business logic processing to render the report

 Use an RDP class to write the business logic.

剩余36页未读，继续阅读

kaivenzou

粉丝: 0
资源: 3

Microsoft Dynamics AX 2012 报告编程模型升级：SysOperation框架与SSRS集成

安装了Report Generation Toolkit for Microsoft Office，但是没有Excel Get Data.vi

from lmfit import Model, fit_report

for i = 1, #reportList do table.insert(report_list, 1, reportList[i]) end 移除 report_list 第四个往后的元素

v-for v-model

最新资源