Skip to main content

AX - SQL query another database via ODBC

Recently I was involved in migrating a large data set from another database. The standard Excel import/export is a great tool for migrating data. Once you start importing over 500 records - it can get very slow.
Here is some code to do an ODBC connection to execute a select statement.
server static void main(Args args)
{
    LoginProperty                   loginProperty;
    ODBCConnection                  connection;
    Statement                       statement;
    ResultSet                       resultSet;
    SqlSystem                       sqlSystem;
    SqlStatementExecutePermission   sqlStatementExecutePermission;
    str                             sql = 'SELECT * FROM Vendor';
    ;

    sqlSystem = new sqlSystem();
    loginProperty = sqlSystem.createLoginProperty();
    // Set server - if you dont setServer. It will use current server the AOS is on.
    loginProperty.setServer('localhost');
    loginProperty.setDatabase('OtherDb');
    connection = new ODBCConnection(loginProperty);
    statement = connection.createStatement();

    //Assert
    sqlStatementExecutePermission = new SqlStatementExecutePermission(sql);
    sqlStatementExecutePermission.assert();

    //BP Deviation Documented
    resultset = statement.executeQuery(sql);
    CodeAccessPermission::revertAssert();
    while ( resultset.next() )
    {
        info(resultset.getString(1));
    }

}
You have use a class and run on server. If you create a job it wont work because it will run client side.

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

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

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