Answered

Best way of triggering Purchase Order's version change

(0) Share

Report

Posted on by Community Member

Good afternoon,

Whole day's research on how PO confirmation versions works left me wondering what is the best approach of turning the order to unconfirmed mode, so later it can get confirmed and get a new version?

I understand that if you change something that changes the purchase agreement, such as order line's quantity or order's payment terms, by default turns the order to unconfirmed state. I see the default code for it, but I'm struggling to follow the logic in case I wanted order to become unconfirmed after I change something, what is not considered as change of an agreement by default. Say, internal/external notes fields from DocuRef table, that are associated with the order and shown in PurchTable form?

What logic should I follow in this case?

Thank you!

*This post is locked for comments

I have the same question (0)

All responses (12)

Answers (1)

Sohaib Cheema 48,843 User Group Leader on at

Like (0)

Report

RE: Best way of triggering Purchase Order's version change

in business world if you change any field which has impact on Price and/or Terms&conditions, it should ask for re-confirmation of PO

But what happens in AX; after confirmation of PO, if you change anything, it gives you option to re-confirm; you can test this thing by doing a small experiment,

simply create a PO

confirm it

now go to any text field, in lines header anywhere, just put one space, save it.

AX will give you option to re-confirm order again.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
RE: Best way of triggering Purchase Order's version change

Thank you Sohaib.

My previous response got removed from this thread for some reason, so this time I'll make it short.

Not all field changes are triggering re-confirmation. As an example, Header View > Price and discount > Payments > Due date change doesn't, and Header View > Price and discount > Payments > Terms of payment - does.

So my question is, where/how do I start this chain of re-confirmation in X++ for custom fields or those not considered as an agreement breakers? So far I've tried methods like below, but with no luck.

ttsBegin; VersioningPurchaseOrder::newPurchaseOrder(purchTable, true).change(purchTable, purchTable_Orig); purchTable.IsModified = NoYes::Yes; ttsCommit;

Was this reply helpful? Yes No
Sohaib Cheema 48,843 User Group Leader on at

Like (0)

Report

RE: Best way of triggering Purchase Order's version change

I think its totally a manual decision which is needed to be taken by business owners. They are the one who know that on changing of what it should trigger the re-confirmation of PO.

for you being a technical person, you may create a setup, where there can be selection of fields from PurchTable and PurchLine. By selection of any field(s) on this setup, it would specify that on changing of data on theses fields, system should trigger/ask for re-confirmation of PO.

Was this reply helpful? Yes No
Suggested answer

Jonathan Halland 11,310 on at

Like (0)

Report

RE: Best way of triggering Purchase Order's version change

I'm not sure if this is what you are looking for, but you can try the following (Taken from purchLineType.update() )

purchLine.updateWorkflowState(TradeWorkflowState::NotSubmitted);

purchLine.purchTable(true).updateFromPurchLines(false);

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Best way of triggering Purchase Order's version change

Thank you, Jonathan. Yes, that's something similar to what I'm looking for, but unfortunately your solution didn't worked, even though it didn't returned any errors.

So I'm trying these little code snippets that I find in PurchLine and PurchTable objects, but nothing seems to work, and I fail to see a common code that is being shared between those elements, that are breaking the agreement.

As AX documentation puts it "The purchase order is the most complex use of the versioning pattern in Microsoft Dynamics AX 2012.".

I'm hoping to find that "single line solution" somewhere :)

Was this reply helpful? Yes No
Jonathan Halland 11,310 on at

Like (0)

Report

RE: Best way of triggering Purchase Order's version change

Hi

What happens when you execute my or other solutions? What are you expecting to occur?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Best way of triggering Purchase Order's version change

Putting it simple - after my custom field in PO form gets modified, I expect Purchase > Confirm button to become active, so after clicking on it a new version of Purchase order confirmation will be generated.

When I run your solution in modified() method of my custom field, the purchLine object is filled up with the information of the first line of the order. I haven't drilled down more, I'm afraid.

Thank you!

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (2)

Report
RE: Best way of triggering Purchase Order's version change

I think I may have found it!

purchTable.type().updateDistribution(); purchTable_ds.reread(); purchTable_ds.refresh();

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Best way of triggering Purchase Order's version change

Hi Donatas, Did you manage to find a better way of doing this?

Was this reply helpful? Yes No
Suggested answer

Asim Saeed 575 on at

Like (0)

Report

RE: Best way of triggering Purchase Order's version change

Hey Donatas,

I have also came across some what the same issue, and what i did to cater the scenario is;

I created a new class extends from VersioningPurchaseOrder and Added a added a method from parent,

which sets the purchTable Modified field to TRUE to be picked for COnfiramation.

public void markModified()
{
super();
purchTable.IsModified = NoYes::Yes;
}

and finally I initialized the class and called 'markModified' method after super call.(You can do it in field modified as well) . In my case i did in clicked method.

Let me know if it worked for you as well.

Was this reply helpful? Yes No