Is this what you mean?
order_lineItem_PRODUCT::ItemName="Accommodations (Hotel/Motel)" and
ORDER::Accommodation Rate > 0 ;
ORDER::Accommodation Rate ;
It's generally a good idea to use an auto-entered value rather than a calculated field, so that your existing line items don't change when you change a value in the Product table.
What you have to watch out for is that a related (line item) field will not re-evaluate when you change the override field in the parent (order) table. You want to make sure that the parent record is committed and the override value entered before creating line items, or else handle it with a script trigger.
Thanks for your reply! This is what I have entered, and it doesn't seem to want to chose the rate I have entered into the side field "Accommodation Rate" for the current Order:
RatePerUnitEmpl = lineItem_PRODUCT::EmpRate and
Case (order_lineItem_PRODUCT::ItemName="Accommodations (Hotel/Motel)" and ORDER::Accommodation Rate > 0 ;ORDER::Accommodation Rate ; lineItem_PRODUCT::EmpRate)
It's set to "auto enter Calculation, replaces existing value"
I really appreciate your help! I'm presently going in, and allowing myself to enter the number manually but it's getting a bit silly!
The difference between your calculation and mine doesn't make sense to me. Our Case statements are the same, essentially saying, "if there's an Accommodation Rate, use that, else use the EmpRate." But then you're adding to that a logical test, which turns the whole thing into, "is EmpRate true? AND is the Case statement true?" I'd guess the answer is generally yes, and it returns a 1. Did you try my calc as written? Did it work? Did you understand the "watch out" warning I wrote?