Skip to main content

Product attributes and beyond [AX 2012]

Product attributes is a great piece of functionality that was introduced in AX 2012. It allows you to set up and capture additional information against a product.
I recently have taken it one step further to make it more visible and user friendly. At the moment it is hidden away on a form you have to open.
In a similar fashion to the way financial dimensions work, where the controls dynamically show up on a fast tab. The attribute controls do the same.
Here is a quick screenshot to show how powerful it can be.
AttributeFastTab2013-02-25_1603
I got the field groups to work by using attribute groups (which is part of retail key).

If you are looking for some info on product attributes have look at these links.
http://technet.microsoft.com/en-us/library/hh227548.aspx
http://www.slideshare.net/murrayfife/using-product-attributes-to-record-nutritional-information-part-1
http://dynamicscare.com/blog/product-attributes-in-ax-2012
This is one of many pieces of frameworks that AX 2012 provides. Its up to us to make use of them and extend them.

Updated 28th Feb 2013: I had a few questions on this. To clear the confusion, this is custom development that worked on for a project recently.

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