Skip to main content

Workflow hierarchy assignment common errors explained and tester job [AX 2012]

Workflow hierarchy assignment has a lot of interdependent data that must be set up. If one of those is missing or is incorrect – the processor will just error out. Sometimes with very little information or confusing errors.

Below is an example of an error that is not very well written. It doesn’t tell you which record failed. Someone went into the effort of creating the labels correctly but did not use it properly.

image

Here are some common errors you would get while processing the workflow.

  • “The hierarchy provider did not return any users.” – Next Position was not found.
  • “Worker not found for position ID %1.” – No worker is attached to a position. Go to the worker and make sure they have a primary position. If no primary position exists, then the system will find the oldest position (one with the earliest start date). Also make sure the worker is an employee of the company to submit the workflow.
  • “User not found” – User not found for the worker. Check the user relations.
  • “User or job not found for position ID %1, worker %2, user %3. Verify that the position is assigned to a job.” – The position found does not have a job related to it.

Now here is a quick solution I put together to help you diagnose or test out your hierarchy. I wrote a job below for Expense lines but to change it to any other table is pretty straight forward. Fill in the missing information and run it. It will give you an infolog with the user id, worker id, position id, the reports to position id, their spending limit and approval limit.

Code:
static void navax_workflowHierarchyTester(Args _args)
{
WorkflowTypeName workflowTemplateName = 'TrvLineItemTemplate';
TrvExpTrans trvExpTrans;
TrvExpNumber trvExpNum = '000015'; //Expense id
str nodeId = '000530'; //Starting worker id

WorkflowHierarchyLevel level = 0;
WorkflowContext workflowContext;
SysWorkflowTable workflowTable;
WorkflowLimitHierarchyProvider workflowLimitHierarchyProvider;
WorkflowHierarchyProviderNode workflowHierarchyProviderNode;
HRPWorkerLimit workerLimit = new HRPWorkerLimit();
HcmWorker hcmWorker;
DirPersonUser dirPersonUser;
RefRecId hcmPositionRecId;
HcmPosition hcmPosition;
container spendingCon, approvalCon;
UserId userId;

select firstOnly workflowTable
where workflowTable.TemplateName == workflowTemplateName;

select firstOnly trvExpTrans
where trvExpTrans.ExpNumber == trvExpNum;


workflowContext = WorkflowContext::newWorkflowContext(
curext(),
tableNum(TrvExpTrans),
trvExpTrans.RecId,

workflowTable.WorkflowCorrelationId);

workflowLimitHierarchyProvider = new WorkflowLimitHierarchyProvider();

//Level 1
while (nodeId && level < 20) //20 is just a fall back. In case it goes into an endless loop.
{
workflowHierarchyProviderNode = workflowLimitHierarchyProvider.getNextNode(nodeId, level, workflowContext);
nodeId = workflowHierarchyProviderNode.getnodeId();
hcmWorker = HcmWorker::findByPersonnelNumber(nodeId);
userId = DirPersonUser::findParty(hcmWorker.Person).User;
hcmPositionRecId = HcmWorker::getPrimaryPosition(hcmWorker.RecId);
hcmPosition = HcmPosition::find(hcmPositionRecId);

spendingCon = workerLimit.getWorkerSigningLimit(
hcmWorker.RecId,
SourceDocumentRelationType::ExpenseReport,
HRPLimitType::Spending,
hcmPosition.PositionId);

approvalCon = workerLimit.getWorkerSigningLimit(
hcmWorker.RecId,
SourceDocumentRelationType::ExpenseReport,
HRPLimitType::Approval,
hcmPosition.PositionId);

info(strFmt("UserId: %1 | WorkerId: %2 | PositionId: %3 | ReportsToPosition: %4 | SpendingLimit: %5 | ApprovalLimit: %6",
userId,
hcmWorker.PersonnelNumber,
hcmPosition.PositionId,
hcmPosition.reportsToPosition(),
con2Str(spendingCon),
con2Str(approvalCon)
));

level++;
}
}



The final result looks like this.


image

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