looks like the pricing hinges on the cCustomerID, so I would create a layout where you can see the value in each portal row... perhaps this field value is wrong? Check the data that the relationship relies on and check the data in the CustomerPrice for OrderLineItem
Using Customer Price_for OrderLineItem in the calc is correct. I'm guessing the issue is what Peter suspects, with cCustomerID. I would remove the quotes from that calculation and keep it unstored, or make it an auto-enter calculation. The ID won't recalculate for existing line items if you change the Customer.
Also, you may want to check the formatting of the Price field on Orders, maybe it's actually storing $7.99 but displaying $8.00 due to data formatting?
One thing I’m seeing is it seem like you’re trying to use the CustomerID to match to price. You would need a full list of prices for every customer doing is way. Or maybe your name CustomerID is confusing us.
The CustomerID should be unique to the customer as you could have 5 John Smiths. Their price code (CustomerPriceCode/Group) needs to be part of their master record. As you can have 0 to thousands of customers in each price group.
One suggestion, I used in a catering solution, is have fields for the cost per item and the "suggested retail". In the Sales Order when the item is selected, the "suggested retail" price comes up. It can be overwritten but you can test (in the background) that a certain cost variance can not be allowed.
Or in the customer you insert a customer discount %, so when the customer is selected to create the Sales Order the special discount is applied evenly to all items.
I figured out why only FOB price will be appeared when using the below formula for OrderLineItem::Price
not IsEmpty ( Customer Price_for OrderLineItem::CustomerPrice ) ;
Customer Price_for OrderLineItem::CustomerPrice ;
Is it because I did not use a script trigger on the Order::Customer. After creating a "Commit Records/Request" script trigger on the Order::Customer, my issue is solved. Without the script trigger, even the customer is selected, FM will still not recognize the customer name.
What is Catering solution? I am kinda a fresh meat on FM...
I worked in a country club, we catered weddings. So in my example our widgets (nuts and bolts) were baked chicken dinner, or desserts.