Skip to main content

CRUD operation in Dynamics AX 2009 through .Net business connector

Friends, rather going into more details about "How to's" of accessing Dynamics AX through .Net, my main objective is to share my experience of performing CRUD operations in Dynamics AX 2009 through .Net BC.

Here is a sample code;


    // CREATE OR INSERT SAMPLE
    // Create the .NET Business Connector objects.
    Axapta ax;
    AxaptaRecord axRecord;
    string tableName = “AddressState”;
    try
    {
        // Login to Microsoft Dynamics AX.
        ax = new Axapta();
        ax.Logon(null, null, null, null);
        // Create a new AddressState table record.
        using (axRecord = ax.CreateAxaptaRecord(tableName));
        {
            // Provide values for each of the AddressState record fields.
            axRecord.set_Field(“NAME”, “MyState”);
            axRecord.set_Field(“STATEID”, “MyState”);
            axRecord.set_Field(“COUNTRYREGIONID”, “US”);
            axRecord.set_Field(“INTRASTATCODE”, “”);
            // Commit the record to the database.
            axRecord.Insert();
        }
    }
    catch (Exception e)
    {
        Console.WriteLine(“Error encountered: {0}”, e.Message);
        // Take other error action as needed.
    }



    // READ SAMPLE
    // Create the .NET Business Connector objects.
    Axapta ax;
    AxaptaRecord axRecord;
    string tableName = “AddressState”;
    // The AddressState field names for calls to
    // the AxRecord.get_field method.
    string strNameField = “NAME”;
    string strStateIdField = “STATEID”;
    // The output variables for calls to the
    // AxRecord.get_Field method.
    object fieldName, fieldStateId;
    try
    {
        // Login to Microsoft Dynamics AX.
        ax = new Axapta();
        ax.Logon(null, null, null, null);
        // Create a query using the AxaptaRecord class
        // for the StateAddress table.
        using (axRecord = ax.CreateAxaptaRecord(tableName));
        {
            // Execute the query on the table.
            axRecord.ExecuteStmt(“select * from %1″);
            // Create output with a title and column headings
            // for the returned records.
            Console.WriteLine(“List of selected records from {0}”, tableName);
            Console.WriteLine(“{0}\t{1}”, strNameField, strStateIdField);
            // Loop through the set of retrieved records.
            while (axRecord.Found)
            {
                // Retrieve the record data for the specified fields.
                fieldName = axRecord.get_Field(strNameField);
                fieldStateId = axRecord.get_Field(strStateIdField);
                // Display the retrieved data.
                Console.WriteLine(fieldName + “\t” + fieldStateId);
                // Advance to the next row.
                axRecord.Next();
            }
        }
    }
    catch (Exception e)
    {
        Console.WriteLine(“Error encountered: {0}”, e.Message);
        // Take other error action as needed.
    }


    // UPDATE SAMPLE
    // Create an Axapta record for the StateAddress table.
    axRecord = ax.CreateAxaptaRecord(tableName);
    // Execute a query to retrieve an editable record where the name is MyState.
    axRecord.ExecuteStmt(“select forupdate * from %1 where %1.Name == ‘MyState’”);
    // If the record is found then update the name.
    if (axRecord.Found)
    {
        // Start a transaction that can be committed.
        ax.TTSBegin();
        axRecord.set_Field(“Name”, “MyStateUpdated”);
        axRecord.Update();
        // Commit the transaction.
        ax.TTSCommit();
    }



    // DELETE SAMPLE
    // Execute a query to retrieve an editable record
    // where the name is MyStateUpdated.
    axRecord.ExecuteStmt(“select forupdate * from %1 where %1.Name == ‘MyStateUpdated’”);
    // If the record is found then delete the record.
    if (axRecord.Found)
    {
        // Start a transaction that can be committed.
        ax.TTSBegin();
        axRecord.Delete();
        // Commit the transaction.
        ax.TTSCommit();
    }




Comments

Popular posts from this blog

The Dual Write implementation - Part 1 - Understand and Setup

What is Dual-write? Tightly couples – complete at one transaction level Near real time Bi-directional Master data and business documents – Customer records you are creating and modifying and at this document we are talking about sales orders or quotes and invoice. Master data could be reference data e.g. customer groups and tax information Why Dual-write and why not Data Integrator? Data Integrator is Manual or Scheduled One directional Now, Let's deep dive and understand what is required for Dual-write setup and from where to start. First thing first, check you have access to https://make.powerapps.com/ Choose right environment of CDS (CE) Make sure you have access to the environment too, click on gear icon and Admin Center  Look for required environment and Open it, you must have access as going forward you are going to configure dual write steps in the environment user the same user you are logged in now. Now, go back to power platform admin center and...

D365O - How to add financial dimension in grid

This post outlines the steps; how to add financial dimensions (segmented control) in a grid in D365O. Let's assume we are adding new table and form for below explanation; New table contains two fields  AccountType and  LedgerDimension with relation to DimensionAttributeValueCombination table  Form looks like this; Set properties for segmented control under form design; - Auto declaration = Yes - Account type field = AccountType - Controller class = DimensionDynamicAccountController - Filter expression = %1 1. Override modified method for LedgerDimension field under form's datasource 2. Override lookup and checkUserCustomLookup method on ledger dimension segmented control in form desgin Datasource | D365O_FinancialDimension | LedgerDimension | modified [DataSource]     class D365O_FinancialDimension     { ...

D365FO: Entity cannot be deleted while dependent Entities for a processing group exist. Delete dependent Entities for a processing group and try again.

Scenario: There are times when you want to delete an entity from target entity list and when you do so, you face an error message which does not tell you where exactly the entity has been used.  "Entity cannot be deleted while dependent Entities for the processing group exist. Delete dependent Entities for a processing group and try again. " Solution: Browse the environment by appending this part  /?mi=SysTableBrowser&TableName=DMFDefinitionGroupEntity&cmp=USMF   at the end.  For example; if the environment URL is  https://daxture.sandbox.operations.dynamics.com then the complete URL will be https://daxture.sandbox.operations.dynamics.com/?mi=SysTableBrowser&TableName=DMFDefinitionGroupEntity&cmp=USMF Filter for Entity and it will give you the DefinitionGroup where the entity has been added or used in data management import/export projects. Get the DefinitionGroup name and search in the export/import projects under data management and either del...