Export (0) Print
Expand All

Walkthrough: Add a Computed Column to a Union View [AX 2012]

Updated: October 23, 2009

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic explains how you can add a computed column to a union view in Microsoft Dynamics AX. When a T-SQL union is involved, the support method that generates the T-SQL code for the computed column must input an int parameter. The parameter specifies one particular branch of the union query of the view. The T-SQL code that the method must output often differs depending on the branch.

This walkthrough illustrates the following tasks:

  • Create a union query.

  • Create the view with regular columns.

  • Add a computed column to the union view.

  • Examine the T-SQL code that is generated for the view.

To complete this walkthrough you need:

In the following subsections you use the Application Object Tree (AOT) to perform the following actions:

  • Create a new query.

  • Change the QueryType property from its default of Join to Union.

  • Add two tables to the query as data sources.

  • Make lists of fields that match by type under each data source.

Gg846293.collapse_all(en-us,AX.60).gifCreate a New Query Node

To create a query with a QueryType of Union, follow these steps:

  1. Click AOT > Queries > New Query.

  2. Right-click the new node for your query, and then click Properties.

  3. In the Properties window, change the Name property value to TestQryUnion.

  4. Set its QueryType property to Union.

Gg846293.collapse_all(en-us,AX.60).gifAdd Tables as Data Sources for the Query

To add two tables as data sources for the query, follow these steps:

  1. Drag the node AOT > Data Dictionary > Tables > CustTable onto the node AOT > Queries > TestQryUnion > Data Sources. The system sets the Name property of the new node to CustTable_1.

  2. Drag the node AOT > Data Dictionary > Tables > AssetBook onto the node AOT > Queries > TestQryUnion > Data Sources. The system sets the Name property of the new node to AssetBook_1.

Gg846293.collapse_all(en-us,AX.60).gifAdd Fields to Each Data Source that Match by Type

To add fields to both data sources, follow these steps:

  1. Delete all fields under AOT > Queries > TestQryUnion > Data Sources > CustTable_1 > Fields.

  2. Click AOT > Queries > TestQryUnion > Data Sources > CustTable_1 > Fields > New > Field. Then set the Field property to AccountNum.

  3. Repeat the previous step, except set the Field property to Party.

  4. Repeat the previous field related steps for the AOT > Queries > TestQryUnion > Data Sources > AssetBook_1 > Fields node. Populate the Fields node first with the field CustAccount, and then with LifeTime. Note that the fields must appear in the exact sequence described, so that the corresponding data types match between the two data sources.

    Caution noteCaution

    The field types under the CustTable_1 > Fields and AssetBook_1 > Fields must match at each ordinal position. In this case, both AccountNum and CustAccount are strings of length 20, and both Party and LifeTime are 32 bit integers.

In the following subsections you create a view that has regular columns. The data source for the view is the query that you created in the previous section.

Gg846293.collapse_all(en-us,AX.60).gifCreate a New View Node

To create a view that uses the previous query as its data source, follow these steps:

  1. Create a view named TestViewUnion.

  2. Drag the node AOT > Queries > TestQryUnion onto AOT > Data Dictionary > Views > TestViewUnion > Data Sources.

  3. Click TestViewUnion > Metadata > TestQryUnion > Data Sources > AssetBook_1. Then set the Union property to UnionAll.

Gg846293.collapse_all(en-us,AX.60).gifAdd Regular Columns to the View

To add regular columns to the view, follow these steps:

  1. Click TestViewUnion > Fields > New > Field.

  2. For the new field, set the DataSource property to CustTable_1. Set the DataField property to AccountNum.

  3. Set the Name property to AccountNum, to match the DataField name.

  4. Repeat the previous three steps to add the Party field.

In the following subsections you add a method that supports a computed column.

Gg846293.collapse_all(en-us,AX.60).gifAdd a Support Method to the View

In this section you add a static method that will support the computed column that you plan to add later. The method outputs part of the T-SQL string that defines the computed column in the underlying database server. The method runs only when the view is synchronized from the AOT to the database server.

The support method must input an int parameter when the method is supporting a union view. The int parameter value tells the method which branch of the union the present call is meant for. The first branch is number 1, not 0. There is one branch for each data source of the TestQryUnion query.

  1. Click TestViewUnion > Methods > New Method. This opens the code Editor window. Paste the following code into the Editor window. The method name is Comp_Party_LifeTime.

    private static server str Comp_Party_LifeTime(int branchNum)
    {
        #define.ViewName(TestViewUnion)
        #define.DataSourceNameBranch1("CustTable_1")
        #define.DataSourceNameBranch2("AssetBook_1")
        #define.FieldToComputeWith1("Party")
        #define.FieldToComputeWith2("LifeTime")
    
        str sReturn,
            sTemp99,
            sTemp98,
            sTemp97;
        DictView dictView2;
        //-------- EndOf variable declarations. ---------
    
        dictView2 = new DictView(tableNum(#ViewName));
    
        // Use T-SQL 'top 1', not X++ 'firstOnly'.
        sTemp99 =
            "(SELECT top 1 bg.DiscNoticeDelayDays"
            + " from BankGroup as bg"
            + " where bg.DiscNoticeDelayDays <= (123 + "
            ;
    
        switch (branchNum)
        {
            case 1:
                sTemp98 = dictView2.computedColumnString
                    (
            DataSourceNameBranch1, // Branch 1.
            FieldToComputeWith1,
                    FieldNameGenerationMode::WhereClause,
                    true
                    );
                sTemp97 =
                    ") /*1*/ )";
                sReturn = sTemp99 + sTemp98 + sTemp97;
                break;
    
            case 2:
                sTemp98 = dictView2.computedColumnString
                    (
            DataSourceNameBranch2, // Branch 2.
            FieldToComputeWith2,
                    FieldNameGenerationMode::WhereClause,
                    true
                    );
                sTemp97 =
                    ") /*2*/ )";
                sReturn = sTemp99 + sTemp98 + sTemp97;
                break;
        }
        sTemp99 = "For TestUnionView.Comp_Party_LifeTime, sReturn is: "
            + sReturn;
        info(sTemp99);
    
        return sReturn;
    }
    

Gg846293.collapse_all(en-us,AX.60).gifAdd a Computed Column to the View

To add a computed column to the view, follow these steps:

  1. Click TestViewUnion > Fields > New > Int Computed Column.

  2. For the new computed field, set the Name property to ComputedInt.

  3. Set the ViewMethod property to Comp_Party_LifeTime.

The following subsections show T-SQL code that is generated for the view and its computed column.

Gg846293.collapse_all(en-us,AX.60).gifTwo Outputs from the Support Method

There are two data sources in the union view that you created. Therefore, the support method for the computed column is called twice during synchronization, one time for each branch that is delineated by the union keyword in the T-SQL create statement. The outputs from the method, for branches 1 and 2, are shown in the following blocks.

(SELECT top 1 bg.DiscNoticeDelayDays
    from BankGroup as bg
    where bg.DiscNoticeDelayDays <= (123 + A.PARTY) /*1*/ )

 

(SELECT top 1 bg.DiscNoticeDelayDays
    from BankGroup as bg
    where bg.DiscNoticeDelayDays <= (123 + A.LIFETIME) /*2*/ )

Gg846293.collapse_all(en-us,AX.60).gifThe Whole Create View Statement

The following block shows the whole create view T-SQL statement.

CREATE VIEW "DBO".TESTVIEWUNION
AS
  SELECT
     A.ACCOUNTNUM AS ACCOUNTNUM
    ,A.PARTY AS PARTY
    ,A.DATAAREAID AS DATAAREAID
    ,A.RECID AS RECID
    ,
     (CAST (((SELECT top 1 bg.DiscNoticeDelayDays
                from BankGroup as bg
                where bg.DiscNoticeDelayDays <= (123 + A.PARTY) /*1*/ ))
           AS INT))
               AS COMPUTEDINT
  FROM CUSTTABLE A

UNION

  SELECT
     A.CUSTACCOUNT
    ,A.LIFETIME
    ,A.DATAAREAID
    ,A.RECID
    ,
     (CAST (((SELECT top 1 bg.DiscNoticeDelayDays
                from BankGroup as bg
                where bg.DiscNoticeDelayDays <= (123 + A.LIFETIME) /*2*/ ))
           AS INT))
               AS COMPUTEDINT
  FROM ASSETBOOK A

Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. get your copy at the MS Press Store

Community Additions

ADD
Show:
© 2015 Microsoft