For Account Name and Account Id, you can use one or the other. When you map an Automation Command to an Account Screen, the Account Id is automatically passed in [:CommandValue].
It used to be that the Create Account Transaction Document Action would only accept Account Name, but the Account Screen passes the Account Id (not Name), so I had to use a script to get the Name via the Id from the DB. Because of this, I made a request to have the Tx Doc accept the Account Id or the Name.
The method which you use to get the Account Name or Id is left up to you. You obviously need to get it somewhere along the line within your automation flow.
OK so I not trying o map it to a screen, just trying to create two Account Transactions in my Rule Flow. I guess this option may not work as emre showed in the link above whereby I wish to use the document to create a Sales Transaction (Samba Default) and a Points Transaction (hybrid Discount)?
Why SambaPOS crashes if I use a Rule referencing 2 Account Transactions; 1 for Sale Transaction; and 1 for Points Transaction? My solution was to move to a Transaction Document to Map the 2 transactions Note: Both actions will work if only 1 is included in the Rule Flow and Screens are above; AND
Why is a blank record created? See below - I think this was art of the original setup for rewards when a Sale Payment becomes “0”?
Look forward to your comments.
[EDIT2] Next is convert Points to Cash but bed first!
Ok I really do not wish to move on until I fully understand this Account Transaction Document? I see it used mostly to add to Entity and Account Screens but why do I need to use it here…
Also not sure if I am comfortable that I reference the new Account “Rewards” but the Sales Transaction [Default] writes to 2 other completely difference accounts?
Just trying to be complete and add to the Samba documentation as guesswork is slightly frustrating. Oh there is only 1 reference to this document type in the “Gift Cards Tutorial” and no WIKI details - its the one left blank.
Tickets already create transaction documents automatically… if your doing a transaction outside of a ticket then you need to use a transaction document. This would include automation for things triggered in a ticket IE its not part of actual ticket.
@pauln I understand your trying to learn Accounting… but what actual real situation are you trying to solve. I mean what are you wanting to do and why? Its easier to answer those type questions vs trying to answer questions about features.
Sure - during training last week I demonstrated the use of “Rewards Points” - Customer Earns Points when they make purchases, Customer can use Points for a free Item.
The first question was nice, so show me the report on the value we have given away? So I set out to record transactions…
Been there many times, see reference to blank record above, but inside ticket means what? If you said inside a Rule - well know what that means.
The first transaction shot above is from my call to the Points Sales Transaction Document I created. I fi take this out as it was an add-in it leaves the Flow close to original tutorial. The only mod was a calculation on Points…
OK so its going to be hard to see what your doing here. Why do you feel you need to rework accounting just to give them a report on points? The original tutorial had correct accounting and it was fully capable of being reported on with custom reports.
Yes sure - well if I have blank transactions as a result of when they use their points to get a free product - would there be nothing to print? I should mention nothing is shown on Work Period Report - very first place I checked.
but bed first!