Way to determine Current Price Definition being used

V5 Question
1

Continuing the discussion from Current Department and Price List:

I need to gain access to this setting:

currentPLdepartment.JPG730Ă—435 55.5 KB

The concern I have is I wish to use it as a constraint for Adding Orders. That infers if I use the {REPORT SQL} Tag in a constraint and hit the Table every time I need to Add/Edit an Order will this become a issue?

It would be nice to have a {:SETTINGVALUE} @emre?
My goal is to ensure once a Price Definition for a Department is in Use - then DO NOT allow prices to be changed vi Happy Hour or other means unless coded by design.

ACTION to be effected is UPDATE ORDER.

[EDIT]
I could set up a workflow using {SETTING:x} - must LOG OUT on Price List Change - do not refresh cache (to retain setting) but workflows typically are born with "holes’ and I am sure a user will find them…

2

Well it is the best I can do for now :smiley:

UpdateOrderConstraint.JPG1269Ă—609 72.9 KB

Can I claim to be the first to use a {REPORT SQL DETAILS:x} Tag as a Master constraint… haha

3

We have {PRICE TAG} is that not good?

4

No, and I did try it with a colon! lol Do you need to be in a Order for that value to be available?

5

Yes, I’m not really understanding why your doing that. I get what your doing but why?

6

You could just simply constrain it to unpaid ticket state. Preventing change until ticket is paid.

7

Ok - If a venue for the day decided to hold a Function i.e Wedding then the Terminals will be switched to Price Definition = Function.

Therefore I do not wnt any other Price Levels available. It works using the constraint above and it is quite efficient using it as a Custom Constraint.

8

So constrain it so it can’t work on unpaid tickets.

9

You’ll have {:DEPARTMENTPRICETAG} on next update.

2 Likes