REPORT ORDER STATES Reporting and Others

V5 Question
1

Hi @emre

I not sure if I am supposed to use a work around for this TAG?

>>Order Counts per State
{REPORT ORDER STATES}

Produces this result:

Should there be a line above for Refunds?

I have just 2 tickets in the Work Period with 1 Order on Each; 1 Order is Void and 1 is Order is Refund.
I guess the Refund Ticket Count is not being shown because the Price has been set back to Zero “0” and the {REPORT ORDER STATES} is ignoring that Order?

refundOrderState.JPG848×297 29.1 KB

ISSUE 2:
This syntax does not seem to support the Department Expression.

[Sales:1, 1]
{REPORT TICKET TYPES:!PreOrder && TotalAmount >= 0}
>Department
{REPORT TICKET TYPES:(DE=Bar)}

I know we had the discussion about using Teminal ID in stead, which would be suitable for Draw Balances. A consolidated report by Department may have Random Terminal ID’s associated to it and mapping Department to Terminal is logistically problematic.

A venue wide consolidated report with individual Departments listed may use:

>Department
{REPORT TICKET TYPES:(DE=$1)}

$1 would be the result of a {REPORT SQL:X} tag.

Your comments Emre…

2

So we can use this syntax:

>Department
{REPORT TICKET TYPES:!PreOrder && TotalAmount >= 0 && DepartmentID == 1}

But I would prefer to use a generic “Name” and also have the Department name listed in:
>Department: Kitchen

3

So you have this as v5 issue… where exactly is the broken feature? I am asking so we can try and reproduce the issue. This mostly just sounds like a feature question.

Some of the report syntax does not support full expressions like the other tags. I think I have mentioned this before but some of them are hardcoded for doing specific things and were not meant to be apart of the typical tags that use the expressions.

4

Hmm seems like your working on a common idea in two different threads. Did the previous thread not solve this issue?

5

I am glad you asked @Jesse.

I started a new thread as I was trying to resolve the issue with advice on working around the DE= syntax.

This works:
{REPORT PAYMENT DETAILS:P.Name,P.Amount.Percent,P.Amount.Sum:(DE=Bar) && Payment.Amount > 0}

But this does not:
{REPORT TICKET TYPES:(DE=Bar) && !PreOrder && TotalAmount >= 0}

My reference was the documentation at:
https://sambapos.com/wiki/doku.php?id=custom_reporting_tags#list_of_all_possible_expression_fields

Clearly it shows that DE for department is an appropriate command. I just felt this might be an admission.

The issue has been resolved using && DepartmentId = $1.

6

REPORT TICKET TYPES is a hard coded report syntax that was not part of the original custom reporting. Emre built it when converting the original Work Periods report over to custom reports. I wouldnt say this is an issue its more of a feature request. REPORT TICKET TYPES tag is working as intended.

In the thread where it says supported by REPORT TICKET tags… its referring to these:

  {REPORT TICKET DETAILS:<fields>:<expression>}
  {REPORT TICKET TOTAL:<expression>}
  {REPORT TICKET COUNT:<expression>}
7

@pauln that documentation was originally a discussion in v4 when custom reports first introduced it is great documentation but its certainly not complete since v5. We have expanded on the report capabilities substantially since v5 and we have tried to document most of it. Most of the report syntax that supports expressions, fields etc has been documented however some specific hard coded tags like the one you mentioned were added quickly to support converting original Work Periods report over to Custom reports and have very little expression support or documentation.

I said that to show a point that some of the newer tags since v5 cant be related to all of that documentation.

8

Ah Crap - that is the 2nd time that document has caught me out. Here is the full context for others:

List of all possible expression fields

Supported by REPORT TICKET, ORDER, PAYMENT, CALCULATION and TICKET ORDER EXP tags.

TEN. Ticket Entity Name Equals
TENC. Ticket Entity Name Contains
TEC.. Ticket Entity Field Equals
TECC.. Ticket Entity Field Contains
TU Ticket User Name Equals
DE Ticket Department Name Equals
TE Ticket Terminal Name
TY Ticket Type
PA Ticket Contains a Payment *
CA Ticket Contains a Calculation
TCET Ticket Contains an Entity Type
TT. Ticket Tagged With
TS. Ticket is in State

I saw the Supported by REPORT TICKET and assumed it supports the variations of REPORT TICKET.

9

I can see how you got confused by that. When he wrote it… it was true because those were the only tags… but since v5 we have much more. Perhaps @emre should have went about it differently but perhaps not. Some of those tags were built for a single purpose.

Obviously TEN. or PA. would not make since with REPORT TICKET TYPES… I hope you can see why some tags dont support the expressions.

10

Yes understand - it very difficult for me working in an “upside down timezone” as I stubbornly try to get things working. The Departments Reporting is slightly more difficult as you may have a number of terminal feeding into a department.

I will push on and declare this a Question, thanks.

11

Maybe start a thread with your project and document it with us so we can help you with ideas? Instead of focusing on specific feature… Emre might be able to implement something for you if he can see bigger picture.

12

Actually @Jesse I do have one issue:

{REPORT ORDER STATES} will not print $0.00 Orders? Do you have a suggested work around for that?
You can see the initial post on this thread.

13

Its not meant too perhaps @emre could allow that similar to how we have {REPORT TICKET TYPES:TotalAmount < 0}

14

Well that is my other issue the TotalAmount = 0 so TICKET TYPES also give me a few problems.

15

What is the problem with it?

16

BTW you can build a report for order states without that spcific syntax…You can use REPORT ORDER DETAILS:X tags.

17

Well I have implemented Q’s refund item automation for RETURNS. It is simple BUT is sets the price to “$0” and thse 2 REPORT Tags must omit lines if values are “$0”.

Will REPORT ORDER DETAILS:x print Orders of $0 dollars?

18

Ok so you need to use a REPORT DETAILS tag then. its hard to help you with one though because I dont know exactly what you need.

Emre implemented these expressions:

ODI > Order.DecreaseInventory (voids)
OII > Order.IncreaseInventory (refunds)
OCP > Order.CalculatePrice    (gifts)

Example using long form and the new expression (Both will work):

{REPORT ORDER DETAILS:O.Quantity.Sum:Order.DecreaseInventory=True}   
{REPORT ORDER DETAILS:O.Quantity.Sum:(ODI=True)}
19

Umm this may save me…

Voids seem work automatically as shown in my first post.

20

https://sambapos.com/wiki/doku.php?id=custom_reporting_tags#list_of_all_possible_expression_fields

On top of this documentation I tried to explain which types of report tags it applies to. In general it documents xxx details, xxx total and xxx count tags. Sorry for the confusion.