Skip to main content

Microsoft Project Add-in overview [AX 2012]

Today I will cover on how the Microsoft project add-in works in AX 2012 R2 CU7.

Setup the service

To setup the service first time, go to the AOT and publish the Service group.

Right click and Deploy Service Group

2014-03-24_1546

Setup parameters

Go the Project parameters fill in the Microsoft Project integration field group.

In this example I will use Archived directory. Other option is SharePoint.

Specify a folder – I would use a network shared path rather than your local drive.

2014-03-24_1547

Setup the project

Create a project but make sure to specify the calendar.

2014-03-24_1548

Launch Microsoft project add-in

On the Project list page, you will see a button to open in in Microsoft project. You will also see a new column called Microsoft Project – this indicates if it is linked to a Microsoft project file.

2014-03-24_1547_001

When you open it in Microsoft project, you will see the Dynamics AX add-in.

2014-03-24_1549

If you click on Add resources – you will get this dialog pop up.

2014-03-24_1550

The Publish has a few options:

  • Publish – It updates the linked Project.
  • Publish New Project – Will allow you to enter a new project id. This will generate a new project and the work breakdown.

2014-03-24_1550_001

  • Replace Existing Project – Be careful with this one. It does exactly what it says – REPLACE. It will replace the activities – assigning new numbers to them.

2014-03-24_1555

  • Save a Template – This will create a new project template.

Remember, once it is linked to Microsoft project, you wont be able to modify it from AX. You have to use Microsoft Project.

But you will notice a new Unlink from Microsoft Project on the Work breakdown structure form. This is to break the link between AX and the file generated.

2014-03-24_1609

Reference:

http://technet.microsoft.com/en-us/library/dn528663.aspx

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