Sorry to be a pain lately but can you check if this Action is working. If I only pass a {PRICE} then the Order line is Updated correctly with the new Price BUT the Price Tag is downgraded to DEFAULT.
Desired behaviour:
If a Price Change is made to a Portion & Price Tag i.e. MIDDY & STAFF PRICE then I would expect that price to be updated? This goes toward being able to make a permanent price change to a PRICE TAG PORTION.
Well I guess if the {PRICE} was not saved to the DBO then the {PRICE} would be lost. I see no issue with this as the Operator was asked “Is this a permanent Price Change?”
I would expect Happy Hour as that was the predetermined {PRICE TAG}. Happy hour is not the best example a better one would be “FUNCTION” or “TRADE” price level.
These levels (as I think you have done) may be carried from a Customer custom Tag and therefore I would expect all the same pricing across the board if you changed Portions. Emre has done a good intuitive implementation as this as if a Price Tag PORTION is $0.00 then it used the DEFAULT Price tag - all good.
In that case the Price YES would go to Normal Price Tag or DEFAULT if no Price existed for that Tag.
The one variation Emre is looking into is what if DEFAULT is $ZERO? I have requested the Price should not move if a Update Order is issued through Automation. You were in that thread as well - thanks for your advice by the way.
OK I’m reading… Well there are a lot of price tag related topics and I’m a little lost. Why you’re setting portion, price tag and price at once with a single action? Why your default prices are 0? It is a little hard to consider what to do when you set everything at once and expect SambaPOS to resolve that. It is working fine for a long time and I don’t want to break working cases while trying to fit that to that requirement. Sorry I’m a little tired today…
Understand your not feeling so good, thanks for replying.
I am trying to change a PRICE for a PORTION that is currently using a PRICE TAG that is not DEFAULT i.e. “FUNCTIONS” or “TRADE”
I started including more parameters to try to get it to work. If I manually change a price and that price was a PORTION and PRICE TAG - the new {PRICE} becomes a “non- Price Tag” price.
Ok I know where some confusion might be. By default you mean a specific Price Tag that your using as your primary prices? Like we discussed the other day?
Emre I am pretty sure he is using a custom Price Definition for his department as a Default. He set his department to use a specific price tag. The others he is using to define non default prices.
@pauln Your wanting to keep it defined within a price tag so you can reference it in tickets and reports right?
I am trying to alter the “$4” HH to “$3” HH and keep the HH Price Tag ON?
If I just pass {PRICE} to Update Order it will set the price BUT reset the {PRICE TAG} to NULL?
I would like to have the option using Automation to permanently save to the DBO a new PRICE for say coke HH at $3". But the {PRICE TAG} is reset.