I am putting together a Method directive that will prevent Confirming a PO if any releases have one of 4 GL codes. My first condition looks like (to fire when someone tries to save with the confirmed checkbox true): [image] My second condition looks like (to only look at releases with trans type …

Here: [image] Incorrect Relationship in BPM Query; Works in BAQ Designer ERP 10 I think the following will do exactly what you want [image] Condition: “Conf: F->T” checks for Confirmed flag changed [image] widget: “Set intPONum” sets the variable intPO (so that we don…

So I have tried a pre-processing Method Directive, but the ttPORel.TranType is null, the ttPORelTGLC.SegValue1 is null, so I cannot determine if my conditions have been met. I am able to see that ttPOHeader.Confirmed went from False to True and I put a message after that (to tell me what the previo…

You might need to use some custom code to actually query the db context and get the additional details for the validation.

You are indicating ALL ROWS. I am reading this as if all rows must = PUR-UKN. I never used this. but it my understantding… ? For exemple for myself I wanted to prevent saving if the detail classid was missing. [image] Then used the exception message to prevent saving… Pierre

First off, do you really want to check on the change of the Confirmed box? I’d think you wouldn’t want to be able to Approve a PO with “bad accts” Either way, I think you’re going to need to use a condition type of “The number of rows in the designed query …” to determine if any of the releases me…

I agree with @Hogardy , I would use Changed and Unchanged. I also agree with @ckrusen , it would probably be best to do it before approval. Also, not sure if the data is there, but I would think about checking the line level instead of the release level for the data.

Waiting to do the check when the Confirmed box is checked makes this much more difficult. Typically, the PO has already been saved (i.e. Updated), back when it was approved. Setting the Confirmed box will only update the POHeader. So you’d have to check the ttPOHeader.Changed, but the PORelTGLC (…

Pierre, I agree that I do not like how the phrase is written, but based on the choices available, I suspect this is a setting to determine which rows are being evaluated (the added row, the deleted row, the updated row, the changed row, all changed rows, or all rows). [image] So I suspect, it is …

The following should work: edit The below has a bug. See about 4 posts down for the fix end edits [image] [image] Set PONumStr widget expression: ttPOHeaderRow.PONum.ToString() Condition0: [image] Query in Condition0 [image]

Calvin, We want this set on the Confirmed box because many of our POs are time sensitive. We do not want to slow down the issuing of a PO, but we do not want to receive the goods in with a wrong GL (and we have this set on our company config). [image] For this reason, we want to check the GL w…

See my post that came in while you were composing yours. There is a shortfall, in that the Confirmed box on the UI would remain checked, even though POHeader.Confirmed is not true. A refresh of the UI form would update this UI field. The MD’s workflow I described, may work in a In-Tran DD on POHe…

Method Directive to prevent save if conditions are met

Epicor ERP 10

ckrusen (Calvin Krusen) March 15, 2021, 4:45pm 24

Here:

Topic		Replies	Views
Customization for Method Directive Epicor ERP 10 customization	8	679	February 21, 2024
Method Directive Condition question Epicor ERP 10 e10 , bpm	30	5076	December 6, 2022
Best Method Directive to use in BPM for Quote Line level required fields Epicor ERP 10 customization	11	3509	October 12, 2021
Set ReadyToPrint to false when PO is approved Epicor ERP 10 bpm	4	1534	May 29, 2018
BPM More Than One Record Error - Help Needed Epicor ERP 10 e10 , bpm	21	6786	December 21, 2020

Method Directive to prevent save if conditions are met

Related topics