Default Dimension Sorting

Often ERP users request that the default dimensions visible on the master records or transaction sources are sorted in a particular sequence. In D365, default dimensions are visible in the sorted order of the names. Taking this into account, following simple steps can be followed to create a sorted sequence with proper names displayed.

First create the financial dimensions with names that the sorted order is the sequence you need. Example, for this demo we need to create Region and then Business segment so this is what we do.

Create a new financial dimension with name A1Region

Go ahead and create 2^nd Financial dimension with name A2BusinessSegment

Now the end user may not like these names displayed this way. Go ahead and setup the translations as shown below:

On translation form, enter as shown below:

Now go ahead, configure account structure, assign the structure as required. Once the setups are in, check any master record or transaction source and notice the dimension sequence.

So easy to setup the sorted sequences isn’t it?

Report Parameters for Query Based Reports – D365 SSRS

The blog mentioned below beautifully explains how one can add report parameters for query-based AX SSRS reports. A good read:

Report Parameters for Query Based Reports

#D365, #SSRSReporting, #X++

Replace a Financial Dimension in Default Dimensions–Condensed [AX 2012]

In my previous post on Replacing default dimensions, I had provided a job to replace one financial dimension within a default dimension. The job was pretty big and I always thought that Microsoft should have provided some way to do these operations easily. Luckily I found a class that has helped me to condense that job and make it pretty small. I am sharing that job here:

The dimensions for Customer record looks like this before running the job:

Here is the job to change the values. We will change the values for Business Unit, Department and Worker all with this simple job:

static void replaceDefaultDimensionsCondense(Args _args)

{

* In this job, we will replace the Business Unit Value from BU-001 to BU-002

* and fill in the values for Department as Dep-001 and Worker as 114

CustTable custTable = CustTable::find(‘CUS-00004’); //Customer Record containing Financial Dimension

Struct struct = new Struct(); //Structure to hold the dimension values to replace

container defDimensionCon; //Container to prepare the required values and dimension attribute combination

DimensionDefault dimensionDefault; //Get the replaced dimension recid

DimensionAttributeSetItem dimAttrSetItem; //Table to get active dimensions for the legal entity

DimensionAttribute dimAttribute; //Table to get the Financial dimensions

int i; //For looping

//Loop for required dimensions

while select Name, BackingEntityType from dimAttribute

where dimAttribute.BackingEntityType == tableNum(DimAttributeOMBusinessUnit) ||

dimAttribute.BackingEntityType == tableNum(DimAttributeOMDepartment) ||

dimAttribute.BackingEntityType == tableNum(DimAttributeHcmWorker) &&

dimAttribute.Type != DimensionAttributeType::DynamicAccount

join dimAttrSetItem

where dimAttrSetItem.DimensionAttribute == dimAttribute.RecId &&

dimAttrSetItem.DimensionAttributeSet == DimensionCache::getDimensionAttributeSetForLedger()

{

//Add the Dimension name and display value to struct

if (dimAttribute.BackingEntityType == tableNum(DimAttributeOMBusinessUnit))

{

struct.add(dimAttribute.Name, ‘BU-002’);

}

else if (dimAttribute.BackingEntityType == tableNum(DimAttributeOMDepartment))

{

struct.add(dimAttribute.Name, ‘DEP-002’);

}

else if (dimAttribute.BackingEntityType == tableNum(DimAttributeHcmWorker))

{

struct.add(dimAttribute.Name, ‘114’);

}

//Prepare the container

defDimensionCon += struct.fields();

for (i = 1; i <= struct.fields(); i++)

{

defDimensionCon += struct.fieldName(i);

defDimensionCon += struct.valueIndex(i);

}

//if there are fields in struct

if (struct.fields())

{

//Get the DimensionAttributeValueSet table’s Record ID

dimensionDefault = AxdDimensionUtil::getDimensionAttributeValueSetId(defDimensionCon);

//Update to Customer

ttsBegin;

custTable.selectForUpdate(true);

if (custTable.DefaultDimension)

{

custTable.DefaultDimension = DimensionDefaultingService::serviceMergeDefaultDimensions(dimensionDefault, custTable.DefaultDimension);

}

else

{

custTable.DefaultDimension = dimensionDefault;

}

custTable.doUpdate();

ttsCommit;

}

Dimensions after running the job:

Pretty Neat!

The class AxdDimensionUtil is pretty handy to do all these stuff.

Reports and Data Methods

In this post, I will explain how to use data methods in Reports. We will use the same Report model and report that we created in Building a Simple Report–Precision Design.

In AX 2009, AX SSRS had good use of these data methods. But with much better integration, and Reporting framework in AX improving, Data Methods in AX SSRS are reduced to minimal use.

Also the reason is that MS is soon going to do away with .Net Business Connector from next version hence the usage of data methods for many things will be redundant. What I have also noticed is the data methods have return type only as System.String and you will not be able to change this return type. This means, data methods can only return strings.

What I will try and demonstrate here is how to add links in AX reports (to open the corresponding forms).

To achieve this first we will add the reference to SRSDrillThroughCommon project. Do the following:

Open the SKL_SampleReportProject (refer to link above)
In Application Explorer, right-click Visual Studio Projects > C Sharp Projects > SRSDrillThroughCommon and then click Edit. This adds the SRSDrillThroughCommon project to our current solution

Open the report SKL_SampleReportPrecision project
Right click on the Data Methods node and create a new DataMethod. Name it CustDrillDown
You will also notice that a Business Logic Project is automatically added

In Solution Explorer, right-click the business logic project and then click Add Reference

Go to “Projects” tab and select “SRSDrillThroughCommon” and click Ok

Double click the data method this opens the Code editor
Add this line of code the declaration

using Microsoft.Dynamics.AX.Application.Reports;

Your code editor should be like this

using System;

using System.Collections.Generic;

using System.Security.Permissions;

using System.Data;

using Microsoft.Dynamics.Framework.Reports;

using Microsoft.Dynamics.AX.Application.Reports;

public partial class SKL_SampleReportPrecision

{

[DataMethod(), PermissionSet(SecurityAction.Assert, Name = “FullTrust”)]

public static string CustDrillDown(string reportContext, string custAccount)

{

return DrillThroughCommonHelper.ToCustomerForm(reportContext, custAccount);

}

Right click on Precision Design and open the designer
Select the AccountNum text box, underline the text and set font color to Blue

Now right click on this text box and select “Text Box Properties…”, Switch to Tab “Action”
Select option “Go to URL” and click button “fx”

Set Expression “=CustDrillDown(Parameters!AX_ReportContext.Value, Fields!AccountNum.Value)”
Click Ok
Save report, go to AX, deploy the report and run it. You should see following

Click on the link and the customer form opens up

Building a Simple Report–Precision Design

In this post, we will see how we can build a report using precision design. A precision design is like a pre-printed format where the placing of report controls, the design and the spacing matters a lot.

A precision design is the standard SSRS report designer following the same principles, rules and requirements as are found in a SQL Server Business Intelligence Studio SSRS designer.

We will again use the same example of printing Customer Id, Customer name and Balance but this time instead of creating an Auto Design we will use Precision Design.

I will also show how we can use some inbuilt parameters to display some generic information like page number, execution date and time etc.

Here we will use the same AOT query created in previous example Build and Deploy Simple Report–Queries: SKL_SampleCustomer

Create the Required Dataset

Open the previously created Report Model

Right click on report model, select Add –> Report. Name the report SKL_SampleReportPrecision
Set the report title to “Customer balance”

Now in the report, go to the Datasets section and create new Dataset using the name Customer
In the query property, click the button
This opens up the query selection box to select a Microsoft Dynamics AX Query
From the list select “SKL_SampleCustomer” and click Next

Here you can select required fields. Either you can select all fields or a subset
Expand All Fields nodes under the CustTable node to select “AccountNum”
Expand Node “All Display Methods” and select “name” and “openBalanceMST”
Click “Ok”
Now Right click on the designs node, select Add and then “Precision Design”. This creates a new Precision Design and name it as PrecisionReport

Now right click on new Design and select “Edit Using Designer”

This opens up the SSRS Designer (same as standard SSRS)
You can see the standard Report Item tool bar from where you can drag and drop the controls onto the designer surface

Now from the controls tool bar, drag and drop the Table control onto the Report Designer
Select the Tablix and then set the DataSetName property = “Customer”

Now let us specify headers, Select one text box in the header section and right click, then select “Expression…”

In the expression editor, you can see lot of sections for Variables, Parameters, Fields, Datasets etc.
Here write the following in the space “Set expression for: Value” – =Labels!@SYS316441
This displays the header text using the labels in AX. This label is “Customer”

Now again specify the values in Second and third text boxes in header row
2nd Column Header(Name) : =Labels!@SYS117778
3rd Column Header (Amount): =Labels!@SYS62867

Specifying the data for the table

Now in the data row, move the mouse to first text box and you should see a button on the right side that looks as shown below

Click the button and it displays the list of fields from the dataset, select required fields

Alternatively, you can right and use “Expression…” box to specify the data fields. The expression box looks as shown below:

Now that the data is ready, we will go ahead and change the look and feel of the report

Formatting the table

You can specify the lots of formats using the properties windows like Background color, Font type color etc. You can also use the formatting tool bar above to format the data

Go ahead and specify the borders for the table for each row. Then change the background of the Header row. Make the text in the header row as center aligned and make the font as bold

Select the table rows one by one and change the font to “Segoe UI” and Font Size to “8pt”. Now your table looks as shown below:

Now we will go ahead and a Page Header and Page Footer. In Page Header, we will add Report name, Report Title and Execution Date and Time. In the Page Footer, we will add the Page Numbers in the format (Page of Total Pages)

To enable Page Header and Footer, in the Report menu select “Add Page Header” and “Add Page Footer” options

Now drag three text boxes from tool box and drop onto the Page Header area. Place two text boxes on the left hand corner and one on the right hand corner as shown below. Drag and drop one text box in the center of the Page footer as shown below.

Select the first text box, Open the expression box and in the Category section, select “Built-in Fields. Now double click on “ReportName” field and it should add the report name to value section

In the same way select “ExecutionTime” in third text box. For report title, Type in “Customer balances” in the second text box

In the footer section, select the 4th text box and type the expression ‘=Globals!PageNumber & ” of ” & Globals!TotalPages’

Apply formatting as required. Now you should see the design as follows

Now close the designer, add the report back to AOT (along with the model) and deploy the report from within AOT.

Create a new menu item

Go to AOT –> Menu Items –> Output, Right click and select “New Menu Item”. Set following properties

Now run the report and the report will be seen as shown below:

Building a simple report – Using Report Data Provider

In my previous post, I explained how we can build a simple report using just the AOT queries. Now what if we have some logic that needs to be implemented and cannot be achieved using AOT queries?

This is where Report Data Providers plays a significant roles. Let us take the same example of displaying the Customer Id, Name and Balance that was used in post “Build and Deploy Simple Report–Queries”.

We can have this report using Report Data Providers as well. For this, we will keep the query and create three more artifacts, RDP, Report and a new Output menu item.

First we create a Report Data Provider class named “SKL_SampleReportDP”. Do the following:

To create an RDP for a report, we also need a temporary table (if it is Base Provider) or a permanent table (if it is pre process provider).

For this sample, we will use CustTmpAccountSum table that is present in base product.

Here are the class methods

/// <summary>

/// The <c>SKL_SampleReportDP</c> class is the report data provider class for the

/// SKL_SampleSimpleReportQuery report.

/// </summary>

/// <remarks>

/// This is a sample class. Author: Sumit Loya

/// </remarks>

[ SRSReportQueryAttribute (querystr(SKL_SampleCustomer))]

class SKL_SampleReportDP extends SRSReportDataProviderBase

{

CustTmpAccountSum tmpAccountSum;

}

The class declaration contains one attribute “SRSReportQueryAttribute”. This attribute specifies the query that will be used for this report. In case no query is required, this attribute can be removed.

There is one other attribute that can be specified on the RDP class and that is SRSReportParameterAttribute. This attribute defines the contract class that will be used to display report parameters.

processReport method

The processReport method is the entry point for calculating the report data for dataset. Here is the method for our sample class

[SysEntryPointAttribute(false)]

public void processReport()

{

this.insertTmpAccountSum();

}

insertTmpAccountSum method

This is a private method that uses the report query to insert data into the temporary table

/// <summary>

/// This method processes the report query and inserts data into the CustTmpAccountSum temporary table

/// </summary>

private void insertTmpAccountSum()

{

QueryRun queryRun = new QueryRun(this.parmQuery());

CustTable custTable;

while (queryRun.next())

{

custTable = queryRun.get(tableNum(custTable));

tmpAccountSum.AccountNum = custTable.AccountNum;

tmpAccountSum.Txt = custTable.name();

tmpAccountSum.Balance01 = custTable.openBalanceMST();

tmpAccountSum.insert();

}

getCustTmpAccountSum method

This method is mandatory as it returns the table buffer that contains the processed report data. The Dataset uses this buffer to bind the table to the dataset.

/// <summary>

/// This method returns the table buffer that contains processed data

/// </summary>

[SRSReportDataSetAttribute(tableStr(CustTmpAccountSum))]

public CustTmpAccountSum getCustTmpAccountSum()

{

select * from tmpAccountSum;

return tmpAccountSum;

}

After creating the class, go ahead and add a new report the existing report model.

Open the previously created Report Model

Right click on report model, select Add –> Report. Name the report SKL_SampleReportDP
Now in the report, go to the Datasets section and create new Dataset using the name CustomerDP
The parameters for the new Dataset should be as shown below. The Data Source Type is “Report Data Provider”

In the query property, click the button
This opens a box to select a data provider class
Select the class we created before, SKL_SampleReportDP and click “Next”

In the next tab, Deselect all fields and just select “AccountNum, Balance01 and Txt” fields
Click Ok

This is how the data set looks like

Now create a new Auto Design as before and name it as CustDP, Select a Layout Template for the report design in Parameters window
Now right click on newly created design select “Add” and “Table”

Set following properties

Name – CustDP
Dataset – CustomerDP
Style Template – TableStyleAlternatingRowsTemplate

You will also notice that the fields are included automatically from Dataset to the “Data” node of the table

Now right click on the report model and select option “Add SKL_SampleReportProject to AOT”
Once the report is created back to AOT, go to AX, find the report in AOT –> SSRS Reports –> Reports, right click and deploy using “Deploy Element” option
Once the deployment is successful, create an output type menu item for the report
Go to AOT –> Menu Items –> Output, Right click and select “New Menu Item”. Set following properties

Now using menu item open and run report. You will notice the same dialog

The report looks like as shown below:

Build and Deploy Simple Report–Queries

In this post, I will explain about creating a simple AX SSRS Report using the queries from AX AOT. This is what you need to do:

Login to AX and open the development workspace
Go to AOT –> Queries, right click and select “New Query”
Rename the query to “SKL_SampleCustomer”
Go to Query’s data source node and right click and select “New Data Source”
Rename the data source to “CustTable” and set property table to “CustTable”
Now go to the “Fields” node of this query and set property: Dynamic to “Yes”
The query looks as shown below

Save the query
Now open visual studio and create a new reporting project by name SKL_SampleReportProject
On the reporting model, right click, select “Add” and then Report
This will add new report to the project

Name this report as “SKL_SampleSimpleReportQuery”
In the report, Right click on the Dataset node and select “Add Dataset”

Name the data set as customer
On the properties window, ensure following properties are set by default

In the query property, click the button
This opens up the query selection box to select a Microsoft Dynamics AX Query
From the list select “SKL_SampleCustomer” and click Next

Here you can select required fields. Either you can select all fields or a subset
Expand All Fields nodes under the CustTable node to select “AccountNum”
Expand Node “All Display Methods” and select “name” and “openBalanceMST”
Click “Ok”

This will generate the required fields for the dataset

Now Right click on the designs node, select Add and then “Auto Design”. This creates a new Auto Design and name it as Report

Select a layout template say “ReportLayoutStyleTemplate”

Now right click on newly created design select “Add” and “Table”

Set following properties
- Name – Cust
- Dataset – Customer
- Style Template – TableStyleAlternatingRowsTemplate
You will also notice that the fields are included automatically from Dataset to the “Data” node of the table

Click on Preview once to view the report

Note: It may not be possible to preview all reports from VS, especially when there are some internal parameters etc.

Now right click on the report model and select option “Add SKL_SampleReportProject to AOT”

Once the report is added, go to AX, find the report in AOT –> SSRS Reports –> Reports, right click and deploy using “Deploy Element” option
Once the deployment is successful, create an output type menu item for the report
Go to AOT –> Menu Items –> Output, Right click and select “New Menu Item”. Set following properties

Now using menu item open and run report.

When you open the menu item, a dialog is automatically made and shown and you will notice that there is also a select button

This happens as we had kept the Dynamics Filter property on Dataset in report to “True”. Hence the Reporting framework adds a select button.

The displaying of dialog box can be handled as well. We will cover this topic when we learn about controller classes.

The report will look like this:

Note: The name has been intentionally removed from image

Hope this helps you in building your first simple report.

Remove a Financial Dimension Value

Here is a job that can help you remove or blank out a financial dimension.

Note the Dimensions before executing this job

Job

static void sgxRemoveWorkerDimension(Args _args)

{

* We will Remove a worker dimension in this example

CustTable custTable = CustTable::find(‘CUS-00004’); //Customer Record containing Financial Dimension

DimensionSHA1Hash hash; //To store the calculated hash for DimensionAttributeValueSet

DimensionAttribute dimAttr; // Contains the financial dimensions records

DimensionAttributeValue dimAttrValue; // Contains used financial dimension values

DimensionAttributeValueSet dimAttrValueSet; //Contains default dimension records

DimensionAttributeValueSetItem dimAttrValueSetItem; //Contains individual records for default dimensions

DimensionAttributeSetItem dimAttrSetItem; // Contains the number of dimensions active for a account structure ledger

HashKey valueKeyHashArray[]; //To store the has key of dimension in question

Map dimAttrRecId, dimAttrStr; //To store the dimension attribute recid and dimension attribute value display value

Set dimAttrValueRecId;

SetEnumerator setEnum;

int dimAttrCount, i;

//Initialize the map to store the backing entity types

dimAttrRecId = new Map(Types::Int64, Types::Integer);

dimAttrValueRecId = new Set(Types::Int64);

dimAttrStr = new Map(Types::Int64, Types::String);

//Find all the active dimensions for current ledger except main account and store there

//backing entity type in the map

while select RecId from dimAttr

order by Name

where dimAttr.Type != DimensionAttributeType::MainAccount

join RecId from dimAttrSetItem

where dimAttrSetItem.DimensionAttribute == dimAttr.RecId &&

dimAttrSetItem.DimensionAttributeSet == DimensionCache::getDimensionAttributeSetForLedger()

{

dimAttrCount++;

dimAttrRecId.insert(dimAttr.RecId, dimAttrCount);

}

//initialize hash key array to null

for (i = 1; i<= dimAttrCount; i++)

valueKeyHashArray[i] = emptyGuid();

//Get individual dimension attribute records and display values except worker dimension

//Store them in sets

while select DisplayValue, DimensionAttributeValue from dimAttrValueSetItem

where dimAttrValueSetItem.DimensionAttributeValueSet == custTable.DefaultDimension

join DimensionAttribute, HashKey from dimAttrValue

where dimAttrValue.RecId == dimAttrValueSetItem.DimensionAttributeValue

join RecId from dimAttr

where dimAttr.RecId == dimAttrValue.DimensionAttribute

&& dimAttr.BackingEntityType != tableNum(DimAttributeHcmWorker) //As we ignore worker dimension, its hash key remains blank

{

dimAttrValueRecId.add(dimAttrValueSetItem.DimensionAttributeValue);

dimAttrStr.insert(dimAttrValueSetItem.DimensionAttributeValue, dimAttrValueSetItem.DisplayValue);

valueKeyHashArray[dimAttrRecId.lookup(dimAttrValue.DimensionAttribute)] = dimAttrValue.HashKey;

}

//Calculate the hash for the current values

hash = DimensionAttributeValueSetStorage::getHashFromArray(valueKeyHashArray, dimAttrCount);

//Null hash indicates no values exist, which may occur if the user entered an invalid value for one dimension attribute

if (hash == conNull())

{

throw error(“Wrong value for Dimensions”);

}

// Search for existing value set

dimAttrValueSet = DimensionAttributeValueSet::findByHash(hash);

// This value set does not exist, so it must be persisted

if (!dimAttrValueSet)

{

ttsbegin;

// Insert the value set with appropriate hash

dimAttrValueSet.Hash = hash;

dimAttrValueSet.insert();

// Insert only specified set items use this

setEnum = dimAttrValueRecId.getEnumerator();

while (setEnum.moveNext())

{

dimAttrValueSetItem.clear();

dimAttrValueSetItem.DimensionAttributeValueSet = dimAttrValueSet.RecId;

dimAttrValueSetItem.DimensionAttributeValue = setEnum.current();

dimAttrValueSetItem.DisplayValue = dimAttrStr.lookup(setEnum.current());

dimAttrValueSetItem.insert();

}

ttscommit;

}

ttsBegin;

custTable.selectForUpdate(true);

custTable.DefaultDimension = dimAttrValueSet.RecId;

custTable.doUpdate();

ttsCommit;

}

Result After Job Run

Dynamics AX Vrooms into F1

Friends, Dynamics AX has been adopted by Lotus F1 team to manage their every aspect of the business.

In turn the Microsoft Dynamics Logo will be appearing on the Lotus Race Car for everyone to see.

Way to go Team Dynamics Vrooom Vroooom.

Read the entire news here.

Report Design and Controls

Finally I have sometime on hand that I can use to continue my posts on Reporting framework. I have not been able to update my blog due to various reasons but lets get started again.

In my previous posts I had covered about reporting framework terminologies and reporting project. In this post, let us go through the types of designs available for reports and different controls that are available for a report. Together all these elements form Report Model Elements

The first and foremost model element is the “Report” element itself

Report: The report element represents a report definition. A report definition contains a collection of elements such as datasets, parameters, images, and report designs.

The elements that define a report are located under the node for the report in a model. The report in turn contains Report Designs and Report Controls. A report element can be identified by following symbol:

Report Designs

Dynamics AX SSRS reports contains two types of report designs

Precision Design
Auto Design

Precision Design

A precision design is a report design that is created by using SQL Report Designer (Standard SSRS Report Designer). Precision designs are useful when a very precise layout is required.

These reports are like pre-printed formats where we know the format of the report while designing them. You can identify a precision design by the following symbol:

Auto Design

An auto design is a report design that is automatically generated based on the report data. An auto design is created by using drag-and-drop actions, and selecting elements by using Model Editor.

You cannot have specific formats in the Auto Design. This design is useful mostly for tabular and matrix type reports with simple groupings and sorting. You can identify a precision design by the following symbol:

Report Controls

The report element can have following report controls or elements

Dataset
Data Region
Parameter
Filter
Grouping
Sorting
Data Method

Dataset

A dataset identifies data that is displayed in a report. Every report must have one or more datasets. Default data sources that are available for Datasets are “Dynamics AX” and “DynamicsAXOLAP”. The data sets can have data fetched by using anyone of the following options:

A query (Dynamics AX AOT query or an OLAP MDX Expression)
Report Data Provider
Business Logic (C# Business Logic with the reporting project only)
AX Enum Provider (Enum values)

A dataset can be identified by symbol.

Data Region

A data region is an area in a report that displays data. Data can be displayed in following formats

Table – Data displayed in columns and rows. Symbol:
Matrix – Data displayed in matrix format. Symbol:
List – Data displayed in list format. Symbol:
Pie Or Doughnut Chart – A chart type report. Symbol:
XY Chart – A chart type reports (Bars, Columns, Lines on XY axis). Symbol:

Please note that all these data regions are available in Auto Design report only. The Precision Design has its own standard SSRS report controls.

Parameter

A parameter lets you parameterize data for a report. With the help of parameters, you can filter the data to the required values.

Parameters can be identified by following symbol:

Filter

A filter is used to filter or restrict the data that is displayed in a report.The Dynamics Filter property on the dataset determines how filters are created for a report. If the Dynamics Filters property on the dataset is set to True, the end user of the report will identify the ranges when they view the report. To manually define the set ranges to filter data on a report, verify the Dynamics Filters property on the dataset is set to False and create your own filters.

Filters can be identified by following symbol: . Again these filters are available only for Auto Design. The Precision Design has its own way of defining filters

Grouping

A grouping lets you organize data that displays in a report by grouping fields. For Auto Design, you can see a node called grouping for Table or Matrix type data regions. Groupings in Precision Design follow the same procedure that is used in Standard SSRS Reports.

Groupings can be identified by symbol:

Sorting

A sort lets you control the order in which data displays in a report. For example, you can sort alphabetically by field in ascending or descending order.

Sorting can be identified by symbol:

Data Method

A data method contains code to retrieve and process data for a report. The code for a data method is written in C# or Visual Basic, depending on which project template is used.

Data Method are designated by following symbol:

Layout Templates

A layout template specifies the styles that are applied to the header, footer, and body of a report. One layout template can be applied to many reports. Layout Templates are created in a reporting project and are separate from Report Controls.

There are default layout templates available but we can define our own custom templates to suit the needs of the customers.

Layout Templates are identified by symbol:

Style Templates

A style template specifies the styles that are applied to a data region. When you create a style template, you will notice that there are several types of templates that you can create based on the data region type. A style template can be applied to more than one data region in a report, and it can be applied to data regions in more than one report.

Following are the style templates that you can create (1 per data region type)

Table – Symbol:
Matrix – Symbol:
List – Symbol:
Pie Or Doughnut Chart – Symbol:
XY Chart – Symbol:

Report Data Sources

A data source is a source of data for a report dataset. You can use the predefined data source, which connects to the Microsoft Dynamics AX application database. Or, you can define your own data sources. System by default provides data sources for “Dynamics AX” and “DynamicsAXOLAP”.

Data Sources have symbol associated with them.

This concludes the report designs and controls.

Spread the word:

Spread the word:

Spread the word:

Spread the word:

Spread the word:

Spread the word:

Spread the word:

Spread the word:

Spread the word:

Spread the word: