Skip to main content

Generate SQL query for GL transactions [AX 2012]

In my last blog I did a demonstration of using an SQL query to build a PowerBI report for the general ledger transactions.

I hard coded the RecId for the financial dimensions. It might be cumbersome to build the query manual. So here I wrote a job you could run to get the query. It will spit out an infolog which you should be able to copy and paste.

static void navax_generateGLQuery(Args _args)
{
    DimensionAttribute  dimensionAttribute;
    str                 sqlStatement, dimNameStr, dimMaxStr, name;
    sqlStatement =
    @'
        SELECT
        GeneralJournalCube.*
        %1
        FROM GeneralJournalCube INNER JOIN
        (
            SELECT
            DAVC.RecId as CombinationId
            %2
            FROM
            DIMENSIONATTRIBUTEVALUECOMBINATION DAVC INNER JOIN
            DIMENSIONATTRIBUTEVALUEGROUPCOMBINATION DAVGC ON
            DAVC.RECID = DAVGC.DIMENSIONATTRIBUTEVALUECOMBINATION INNER JOIN
            DIMENSIONATTRIBUTELEVELVALUE AS DAVL ON
            DAVL.DIMENSIONATTRIBUTEVALUEGROUP = DAVGC.DIMENSIONATTRIBUTEVALUEGROUP INNER JOIN
            DIMENSIONATTRIBUTEVALUE AS DAV ON DAV.RECID = DAVL.DIMENSIONATTRIBUTEVALUE INNER JOIN
            DIMENSIONATTRIBUTE DA ON DA.RECID = DAV.DIMENSIONATTRIBUTE
            GROUP BY DAVC.RECID
        )
        Dimensions ON
        Dimensions.CombinationId = GeneralJournalCube.LEDGERDIMENSION
    ';
    while select ViewName, RecId, Type, Name from dimensionAttribute
    {
        if (dimensionAttribute.Type == DimensionAttributeType::CustomList)
        {
            name = dimensionAttribute.Name;
        }
        else
        {
            name = dimensionAttribute.ViewName;
        }
        dimNameStr += strFmt(',%1\n', name);
        dimMaxStr += strFmt(',MAX(CASE WHEN DA.RECID = %1 THEN DAV.ENTITYINSTANCE ELSE NULL END) AS %2\n', dimensionAttribute.RecId, name);
    }
    sqlStatement = strFmt(sqlStatement, dimNameStr, dimMaxStr);
    info(sqlStatement);
}

Its a bit crude but at least you get all the dimensions.

image

Labels:

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro
Read more

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !set.in(custTable))         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds
Read more

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi
Read more