web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Purchase Requisition Line Workflow Condition Sales tax group uses wrong field (ProjtaxgroupID)

(0) ShareShare
ReportReport
Posted on by 50

L.s,

I have created a workflow for Purchase Requisition Line Review
- I want an automatic action and created a condition for the line
- When I check in the condition on the field "purchase requisition lines.Product name" it works as expected, so the concept and setup seems fine

But I want to check on the field "sales tax group" and this don't work as expected:
- I select in the condition the field "purchase requisition lines.Sales Tax group"
- Condition don't give the expected result

I did some research and tests:
- In the DataBase table "Expressions" I see in the Expression that the field "ProjTaxGroupID" from the PRline is used instead of the field "(Sales)TaxGroup"
- I didn't use a Project for my PR so I use "(Sales)TaxGroup" in the PRline.
- When I enter on de PRline both fields and fill them with a different Tax Group. I see the field "ProjTaxGroupID" is evaluated in the condition.
- I experimented with other fields in the condition in the workflow but can't find one that evaluates the field "(sales) Tax Group".

Question:
- Is there a table or something where I can set the relation between:
   "purchase requisition lines.Sales Tax group" and the actual field that will be used in the condition?
- Any other option so I can evaluate the field "(sales)taxgroup" in the condition in the PR line review workflow?

Thx in advanced
Peter

image_2D00_2021_2D00_02_2D00_19_2D00_00_2D00_24_2D00_14_2D00_643.png

I have the same question (0)
  • Suggested answer
    Michal Krejza Profile Picture
    Microsoft Employee on at

    Hi Peter,

    Thank you for all details and analysis. I haven't found any solution. Could you please open a ticket to Microsoft Support team ?

  • Suggested answer
    PeterHS Profile Picture
    50 on at

    Hi Michal,

    Thanx for your reply, sorry I it took some time for my response (COVID).

    I looked at it with the programmer and we found out that we can change the labels at the database (\AOT\Extended_Data). Here the two fields have the same "alias". The programmer made the "aliases" unique and now the problem seems to be gone.

    Greetings

    Peter

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 658

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 495 Super User 2026 Season 1

#3
Syed Haris Shah Profile Picture

Syed Haris Shah 315 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans