Skip to main content

The most important properties of tables in axapta



The most important properties of tables in axapta

• TitleField1 and TitleField2: Specify fields that are displayed in the active title bar of forms
• ConfigurationKey and SecurityKey: Specify that only users authorized to access the data can do so. We strongly recommend setting these options.
• CacheLookup: Specifies how the table is to be cached to optimize data access.
• CreateRecIdIndex: Allows you to create a RECID index. Axapta automatically adds
a RECID to every table when its created, so that you can use it as an index; however, if you have a well-designed data model, then that should not be necessary.
• PrimaryIndex and ClusterIndex: Specifies which field is your primary and clusteredindex, which requires that you have created the respective fields beforehand.
Defining tables consists of creating the table itself and the following subtypes:
• Fields: Dictates where your data is actually placed, and when you create these you specify the base data type each holds. However, you should as a rule set the Extended Data Type (EDT) property to an existing one so that the definition is maintained centrally for ease of reuse and maintenance.
• Field groups: Allows you to group fields that are normally used together, such as name and surname, so that you can reference them as a block when you need to use them.
• Indexes: Defines indexes that you need to optimize data access to your table.
• Relations: Defines relations between the table and others for enforcing relationalconstraints.
• DeleteActions: Specifies what to do with related tables when you delete a record; you specify a table that is the subject of the action and the action that has possible values:
• None: Disables the delete action
• Cascade: Deletes related records
• Restricted: Prohibits deletion if related records exist
• Cascade+Restricted: Behaves like the Restricted value if you delete a record directly in the table, but cascades if the record is deleted as the result of a cascading delete on a table higher on the cascade chain

Popular posts from this blog

strScan and Find a first occurrence of a string in a string using x++

strScan (Find a first occurrence of a string in a string) info("int strScan(str _text1,str _text2,int _position,int _number)"); info("Searches a text string for the occurrence of another string."); info("_text1 - The text string to search."); info("_text2 - The string to find."); info("_position - The position at which the search should start."); info("_number - The number of characters that should be searched."); info(int2str(strScan("ABCDEFGHIJ","DE",1,10)));

Get record from table on the basis of field id in Microsoft dynamics axapta x++

How to Get record from table on the basis of field id in dynamics axapta x++. just try following code in job to understand better way. emplTable emplTable; FieldId fieldId; ; fieldId = fieldNum(emplTable, Emplid); select emplTable; info(emplTable.(fieldId)); select emplTable where emplTable.(fieldId) == '1101'; info(emplTable.Name);

Code to get customer Primary Address in Ax 2012

Below Code to get customer Primary Address in Ax 2012. CustTable custTable_P; DirPartyTable dirPartyTable_P; DirPartyLocation dirPartyLocation_P; DirPartyLocationRole dirPartyLocationRole_P; LogisticsLocation logisticsLocation_P; LogisticsLocationRole logisticsLocationRole_P; LogisticsPostalAddress logisticsPostalAddress_P; LogisticsPostalAddress primaryAddress_P; while select custTable_P where custTable_P.AccountNum =='ED_01029' join dirPartyTable_P where dirPartyTable_P.RecId == custTable_P.Party join dirPartyLocation_P where dirPartyLocation_P.Party == custTable_P.Party && dirPartyLocation_P.IsPrimary==NoYes::Yes join dirPartyLocationRole_P where dirPartyLocationRole_P.PartyLocation == dirPartyLocation_P.RecId join logisticsLocationRole_P where logisticsLocationRole_P.RecId == dirPartyLocationRole