Have you tried Report Tags in a Printer Template? They don’t work?
Sorry, how do you mean?
Also {ACCOUNT TRANSACTION DETAILS:.... will obviously only show transactions of a specific transaction type so isnt suitable for a ‘statement’
So what would be good is a {TRANSACTIONS} section tag to define a [TRANSACTIONS] section like we do for orders.
With tags like {TRANSACTION DATE}, {TRANSACTION TYPE}, {TRANSACTION TOTAL} {TRANSACTION DESCRIPTION} and something to either format credit/debit desperately or {TRANSACTION TOTAL} bring DEBIT or ‘(CREDIT)’ / ‘-CREDIT’.
To allow something like;
[ENTITY]
-- Statement layout
<C00>
<C00>{ENTITY NAME}
<C00>
{TRANSACTIONS}
[TRANSACTIONS]
<J00>{TRANSACTION DATE}|{TRANSACTION DESCRIPTION}|{TRANSACTION TOTAL}
Because there isnt (or at least not that I can see) a report tag which products a statement type layout regardless of report/print template.
These are the account based report tags (at least the ones listed on the template help)
ACCOUNT TOTAL:X Account Total
ACCOUNT DEBIT TOTAL:X Account Debit Total
ACCOUNT CREDIT TOTAL:X Account Credit Total
ACCOUNT TRANSACTION TOTAL:X Account Transaction Total
ACCOUNT TRANSACTION DEBIT TOTAL:X Account Transaction Debit Total
ACCOUNT TRANSACTION CREDIT TOTAL:X Account Transaction Credit Total
ACCOUNT TRANSACTION DETAILS:X Account Transaction Details
ACCOUNT TRANSACTION COUNT:X Account Transaction Count
Non of those are {REPORT… type, DETAILS is closest but can only list one transaction type…
1 Like
I mean, take a Report Template and dump it into a Printer Template. Copy/paste.
Maybe remove the header fields on the Report… or not!
Automate it all. Select Customer, click button, which in turn executes Print Job Action that is set to use the desired Printer and Printer Template.
Sorry, my reply got caught on the end of my post while you posted. (ABOVE)
This is what im trying to achive but with additional info/formatting; (there is no template in the system which I can see for this print… just an action to print it)
this is Print Account Transactions action
Maybe you already tried this, and it does not work, or you don’t understand what I am suggesting. Does this help?
Thats what I am doing;
But there is not the right tags for the job…
obviously ignore the template itself as was my drafting example for last post…
Plus the above issue;
And no tags to replicate this with additional info;
[quote=“JTRTech, post:25, topic:8029”]
this is Print Account Transactions action
[/quote]
Go to Reports.
Open the Workperiod Report.
Select All. Copy.
Go to your Printer Template. Paste.
Does that not work?
Are you missing Report Tags or Templating options? Can you design a Report that displays what you want? No? Why?
Report tags work in printer template, yes.
Yes, am trying to create a statement, these are the available account based report tags;
ACCOUNT TOTAL:X Account Total
ACCOUNT DEBIT TOTAL:X Account Debit Total
ACCOUNT CREDIT TOTAL:X Account Credit Total
ACCOUNT TRANSACTION TOTAL:X Account Transaction Total
ACCOUNT TRANSACTION DEBIT TOTAL:X Account Transaction Debit Total
ACCOUNT TRANSACTION CREDIT TOTAL:X Account Transaction Credit Total
ACCOUNT TRANSACTION DETAILS:X Account Transaction Details
ACCOUNT TRANSACTION COUNT:X Account Transaction Count
6 are TOTALS
1 is transaction count
The closest to the ‘Print Account Transactions’ action is ACCOUNT TRANSACTION DETAILS:X
But this requires {ACCOUNT TRANSACTION DETAILS:<Transaction Type>:<Account>}
Specifying transaction type will only show account sale transactions, account cash payment or account card payment transactions and not a ‘Statement’ type.
Hense the sugestion fo a
{REPORT ACCOUNT TRANSACTIONS:X} tag where we could use fields and expressions.
Something like;
{REPORT ACCOUNT TRANSACTIONS:AT.Date,AT.Description,AT.Debit,AT.Credit,AT.Balance:(AN={ENTITY NAME}}
Which would render something like;
THAT IS NOT A TEMPLATE ITS A PRE-CONFIGURED ACTION PRINT.
1 Like
@Jesse seemed to have a solution to part of your issue, passing ticket id onto the account statements. He was just waiting for the next update.
I know this does not solve your formatting issue but it could be a start.
Not sure what he was looking for in a new feature. The buttons on those screens will pass the Entity ID or Account ID. One or the other should work just fine. Why would you need a Ticket ID?
If Kendash had prepared a partial sample, we would have a starting point. He is far better with Report Tags than I am.
Entity I’d or account id would not help either way as the only way to have a statement type print is the print transactions action which uses a hard coded template.
Well, I beg to differ. The Account ID is exactly what you need to re-create that hard-coded print.
You can use the Account Name, the Entity Name or ID as a link into the Account, or whatever. But in the end you need the Account ID. Once you have that, you should be off to the races.
I am surprised this cannot be done with Report Tags. I know for certain we can create that exact report using SQL. Maybe that’s what I need to do…
I see what your saying.
The print entity action seems to be what is needed to automate the print using a printer template however the current tags do not seem to cover recreating the ‘statement’ that is printed with that hard coded template.
I am hoping emre will come back with some of his usual magic to do this simply with a report tag but will see what he says before looking at SQL.
As its been brought up a few times I think it would be good if he can bring something in to do a formatted statement with tags.
I am sure you could recreate with SQL :-p
But given the generalnes of a statement to the samba software I hope emre can see a built in tag/solution should be implemented.
Hopefully he will include a date range expression in the tag 
Oh well… you want to add custom reports inside ticket prints. Well these are entirely different concepts. You can use custom report tags inside tickets to read plain values but printing a custom report inside a ticket is not supported. Ticket Template parser won’t process custom report specific features.
Literally, I do not think that is necessary… we shouldn’t need to use a Ticket/Printer Template at all. A Report Template should suffice.
I am curious to know/understand what is missing from Report Tags that makes this type of Account Statement impossible at this time.
I really think we should concentrate on that. Producing the Report is the first step.
fair enough @emre but can we get access to change the template of the print produced by ‘Print Account Transactions’ action?
I can’t work out a way to replicate this print in either report template or ticket template with the listed report/ticket tags.
{ACCOUNT TRANSACTION DETAILS:X} is the closest I can find but as transaction type is specified it will only list one type of transactions - in mine either sale transaction, cash payment or card payment (my 3 possible account transaction types for bookings accounts. But only 1 type at a time.
The print transactions action produces a list of all transactions debit and credit for a account with a running balance. That is pretty much exactly what is needed for statement but need to be able to customise this to show entity data details etc.
You can’t use OR in your Tx Type spec?
Sorry not following?