2 Fields update each other

weblike

HI,

Maybe someone is facing with this:

Inside an invoice I have 2 fields : DueDays; DueDate

What I want to achieve is this:
When the user inserts:
DueDays=10 => then the DueDate will be calcultated = InvoiceDate+10

When user inserts:
DueDate=10/15/2016 =>then DueDays=DAY_DIFFERENCE(DueDate,InvoiceDate)

Basically both fields are calculated and both fields can be edited.
Practically I've seen this function in many other invoicing apps, but can be achieved in AwareIM?

Thx,

pureist

I think they're both standard editable text fileds, but a dynamic rule is triggered whenever InvoiceDate or DueDays, or DueDate is changed, which updates whichever of them is necessary.

weblike

I will try, but logically this create's a inifinete loop.

pureist

you are not incrementing anything and InvDate remains static, so I don't see how.

DueDays is changed by user
rule fires
DueDate is updated/changed by rule
rule fires
DueDays is updated by rule (but not changed)
therefore rule does not fire again
You could use OLD_VALUE to prevent the unnecessary update if you want to stop it.

BLOMASKY

If I was worried about that, You could have a flag, call it "recompute flag"
then when either one is changed it turns recompute flag from no to yes
Now, all your calculations would run when flag changed to yes, and at the end of that, change the flag to No

Not sure that would work, but 1st thing that comes out of my brain that has not had enough coffee yet.

Bruce

BenHayat

George, I have had a situation similar to that and took another approach to eliminate circular rule execution.
a) No rules in customer for Due data and due days.
b) I'd use Virtual objects (none persisted) to have two attribute, due date and due days. Have to simple form created one for due date and one for due days.
c) In your customer form, have two buttons to call two processes. Process A will popup Due Days form for user to enter days, and the process calculate Due date of the customer. Process B will popup Due Date form for user to enter Due Date and the process calculates Due Days if the customer.

I have similar case for subscription date/days and this is very clean, with no loops in rules. Rules like this will kill performance, especially if that object is a "LoggedInUser" object.

johntalbott

If you want to stick with BO rules, something along these lines should work.

If Invoice.DueDays Was Changed AND Invoice.DueDate <> Invoice.InvoiceDate + Invoice.DueDays Then
Invoice.DueDate = Invoice.InvoiceDate + Invoice.DueDays

If Invoice.DueDate Was Changed AND Invoice.DueDays <> DAY_DIFFERENCE(DueDate,InvoiceDate) Then
Invoice.DueDays <> DAY_DIFFERENCE(DueDate,InvoiceDate)