Skip to main content

Dynamics AX 7– (Project) Resource management changes

This was an interesting find under the projects module. Now you can put your hours against a Resource rather than a Worker. A resource can be a machine or facility or a worker. I feel this was lacking in prior versions and is a great addition. In prior version you were able to schedule against a resource but the time booked was always against the worker.

What this means is now all the Worker references have changed to Resource

1. Hours forecast and actuals are against a Resource


2. Project/Worker validaiton and Category/Worker validation.



If you look at the details of the resrouces you will see that it is linked to a worker but it can now be linked to Vendor/Machine/Tool/Location/Facitlity.


From a code perspective if you are upgrading it is fairly straight to port over your code. You should change from Worker to Resource.

From if (! ProjValEmplProjSetup::checkWorkerProj(this.Worker, this.ProjId))
To if (! ProjValEmplProjSetup::checkResourceProj(ResourceFacade::findOrCreateByWorker(this.Worker), this.ProjId))


From if (! ProjValEmplCategorySetUp::checkWorkerCategory(this.Worker, this.CategoryId))

if (! ProjValEmplCategorySetUp::checkResourceCategory(ResourceFacade::findOrCreateByWorker(this.Worker), this.CategoryId))

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.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

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.