Skip to main content

Create AxTableContext from IAxaptaRecordAdapter or from a RecId

Somtimes we need to create a record context from a custom record but not based on a record from a data set. It is a bit tricky to create a menu item record context fram an IAxaptaRecordAdapter or a RecId.

Here is an example


// Get the recid for which record the context should be fore
// where record is any record from any given table in Ax
Int64 recId = record.GetField("RecId”);                    

int tableId = TableMetadata.TableNum(this.AxSession, "[TABLENAME]"); 

// Create a dict table
Proxy.DictTable dictTable = new Proxy.DictTable(AxSession.AxaptaAdapter, tableId);

// Get the field id
int fieldId_RecId = TableDataFieldMetadata.FieldNum(this.AxSession, dictTable.name(), "RecId");

// Create the table metadata
TableMetadata tblMetadata = MetadataCache.GetTableMetadata(AxSession, tableId);

// Create the dictinary object
Dictionary<int, object> dictRecId = new Dictionary<int, object>();
dictRecId.Add(fieldId_RecId, recId);

// Create the tablekey
AxTableDataKey tableKey = AxTableDataKey.Create(tblMetadata, dictRecId, null);

// Finally create the context and add it to tne menu item
AxTableContext context = AxTableContext.Create(tableKey);
AxUrlMenuItem menuItem = new AxUrlMenuItem("[NAME_URL_MENU_ITEM] ");
menuItem.MenuItemContext = context;

Comments

Post a Comment

Popular posts from this blog

Dynamics 365 for operations – Table extensions

Background Extensions are a new way to add functionality and custom code to the D365 system without changing the standard code. In fact, Microsoft has announced that edit standard elements like those that we have done in the past will not be possible after 2017. By using extensions, we can achieve the same result by simply extending the standard system => EXTENSIONS. To read more about the difference between overlaying and extensions follow this link https://ax.help.dynamics.com/en/wiki/customization-overlayering-and-extensions/#extensions Extending tables By using table extensions, we can create a new table that adds new fields, field groups, indexes, mappings, relations, methods, subscribe to event handlers and more. When extending tables we need to follow the naming rule as such: <TABLENAME><_Extension> the compiler understands the _Extensions suffix and knows that the table in question is extending a table from the standard system. This gives us access ...
Post a Comment
Read more

New Dynamics 365 for operations learning material

Latest Dynamics 365 for operations training material New learning material is now available on the Dynamics Learning portal 80773BE: Managing Users and Security in Microsoft Dynamics 365 for Operations 80924BE: Extending Elements, Code, and Event Handlers in Microsoft Dynamics 365 for Operations 80927BE: Form Methods and Controls in Microsoft Dynamics 365 for Operations 81002AE: Overview of the Sales and Marketing Module in Microsoft Dynamics 365 for Operations 81003AE: Set Up the Sales and Marketing Module in Microsoft Dynamics 365 for Operations 81004AE: Manage Sales with Sales and Marketing in Microsoft Dynamics 365 for Operations 81005AE: Manage Prospects in Sales and Marketing in Microsoft Dynamics 365 for Operations 81006AE: Manage Contact Information and Activities in Microsoft Dynamics 365 for Operations 81007AE: Create and Maintain Telemarketing and Campaigns in Microsoft Dynamics 365 for Operations 81008AE: Track Leads and Opportunities in Microsoft Dynamics 365 for Ope...
Post a Comment
Read more