I have a Transaction object that I want to have calculate values right on the form for the user to see.
The Transaction object has the following attributes:
Fees, Taxes, Amount, Deductible & PayableAmount.
I set Fees, Taxes and Deductible to have initial values of 0.
I selected both Amount and Payable Amount to be calculated fields.
Amount = Fees + Taxes
Payable Amount = Fees+Taxes-Deductible
I first tried to setup one rule that did both calculations, one after the other. I selected dynamic recalcuation on form for the rule. I kept getting strange values in the Payable Amount specifically. I would put in Fees $1500, Deductible $500 and the PayableAmount would come out to -500.
So I separated the rules. Now when I tab through the fields one at a time, it zeros out the previous fields.
On top of all that, I think it's clearing the actual Transaction object. The Transaction Object is started by a process ENTER NEW Transaction WITH Transaction.Claim=Claim, Transaction.EnteredBy=LoggedInSystemUser
But when I go to save, it tells me I have to enter EnteredBy.
I get the feeling that this is somewhat related to initialValues, there seems to be rules auto generated if I put an initial value for an attribute. I've searched the forum for anything related and only found one post that looked like someone had a similar issue, but it was never resolved (or at least the resolution wasn't posted)
Form refresh &hilit=form+refresh#p33081
Again any help is appreciated.
