Ax2012 workflow issue probable bug

(0) Share

Report

Posted on by Mav

Hi,

I have a approval journal workfllow in GL module with 1 step of assigning work item to manager of the workflow originator. It works fine for normal scenarios.

However when user A who is assigned to worker A & position A & has none in " report to " section (basically no reporting manager) , submits GL for apporval. The workflow get assigns to worker B .

Ideally it should error out as the report to section was blank & never assigned to worker B.

What can i do to ensure any 1 of the following

A>User who has report to as blank should not be able to submit JE to workflow OR

B>If user who has report to as blank is submitting items to workflow, then workflow should error out instead of assigning it to worker B .

Thanks

Mav

All responses (16)

Answers (0)

Jeremy Driscoll on at

Like (0)

Report

RE: Ax2012 workflow issue probable bug

Hi Mav,

The system won't let you delete a position if it's been used in things like timesheets or hours journals. You would have to develop something to delete that, but it will likely break other things in the historical data so do that at your own risk.

Thanks,

Jeremy Driscoll

Microsoft Support Engineer
Mav on at

Like (0)

Report

RE: Ax2012 workflow issue probable bug

Please share how to delete this position , can it be deleted from application or it has to be deleted via sql /x++ script
André Arnaud de Cal... 294,145 Super User 2025 Season 1 on at

Like (0)

Report

RE: Ax2012 workflow issue probable bug

Hi Mav,

When the position was assigned to a hierarchy before, then there are still dependent records with an end date. This is preventing the position from being deleted.
Mav on at

Like (0)

Report

RE: Ax2012 workflow issue probable bug

Hi Andre,

I was surprised to see that inactive position is having assigned worker, not sure how can that even be possible.

As soon as i remove worker association from inactive position, the issue got resolved.& hiearchy provider class started working as expected.

Also even after removing the worker association from inactive position i cannot delete this inactive position.

Here are screen caps for a problematic system vs working system(in which i fixed the issue)

1>Inactive position form showing inactive position assigned to a worker ( user b in our case)

Problematic system

Working system

2>Position details from maintenance version window of inactive position.

Problematic system

Working system

3>Position worker assignment

Problematic system

Working system

4>Error while detesting the position is same for problematic & working system.

Error is "

Positions cannot be deleted while dependent Position hierarchies exist. Delete dependent Position hierarchies and try again." & note there are no values in position hiearchies tab for mainteannce version

Also have shared the steps to recreate the issue .

Thanks

Mav
Mav on at

Like (0)

Report

RE: Ax2012 workflow issue probable bug

Hi Saurav,

There is no role or dimensions , owner & etc. It is a simple workflow with 1 aproval step .

User A has no manager assigned to its position.

user b has 1 inactive position assigned to itself .

Please Check the recreation steps shared earlier .

Thanks

Mav
SouravDam 11,723 on at

Like (0)

Report

RE: Ax2012 workflow issue probable bug

Can you please check if this user "B" is selected as dimension "Owner" and "Manager" in the financial dimension and in operating unit under where the other user "A" is working?

If yes, then can you remove this user "B" from both this forms (Financial dimensions + Operating units) and see if it solves this case?

Keep us posted please.

Regards,
Sourav
André Arnaud de Cal... 294,145 Super User 2025 Season 1 on at

Like (0)

Report

RE: Ax2012 workflow issue probable bug

Hi Mav,

I would not expect that an inactive position would be used here. Can you share a screenshot with all validity dates of this position?

Is user B still an active user?
Mav on at

Like (0)

Report

RE: Ax2012 workflow issue probable bug

Hi Ludwig,

Thanks for your reply, yep that is 1 of the 1st thing i checked & there are no delegation setup in my case.

Shared below are steps to recreate this issue.

1>Create simple workflow with approval step configured to use line manager .

2>Submit the workflow from user A , ensure user A has no report to position assigned in HR position detail form,

3>Have user B tied to a "inactive position" in Ax.

4>Submit the item to the workflow via user A.

5>Expected case should be that workflow should error as there is no manager assigned to user A.

6>However what will happen is you will see that workflow get assigned to user B who has no relation to user A.

Ideally the system should not return anything in hierarchy provider logic because user A has no manager assigned , additionally it should not return user B 's inactive position in hierarchy provider logic .

Thanks

Mav
Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

RE: Ax2012 workflow issue

Hello Mav,

Just for curiosity because I recently experienced something related, can you check the user setup and verify that there is no delegation in place that might cause the issue here?

Best regards,

Ludwig
Mav on at

Like (0)

Report

RE: Ax2012 workflow issue

Just checked that i have inactive position which is tied to a worker B.

So for some reason ( i have deep dive more in debugging) when user A who has no manager assigned to it submits an item , it fetches this inactive position in hierarchy provider logic as default position for user A & so for all other users who do not have any manager assigned to themselves .

Ideally the system should never get position details from inactive positions, correct ?