# Customer Ticket History

**URL:** <https://forum.sambapos.com/t/customer-ticket-history/6397>\
**Category:** V4 Question\
**Created:** [July 29, 2015, 7:18pm UTC](https://forum.sambapos.com/t/customer-ticket-history/6397 "2015-07-29T19:18:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neil](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/n/839c29/32.png) [@Neil](https://forum.sambapos.com/u/Neil)\
**Post date:** [July 29, 2015, 7:18pm UTC](https://forum.sambapos.com/t/customer-ticket-history/6397/1 "2015-07-29T19:18:46Z")

</div>

New here. Trying to setup SambaPOS V4. I specifically need a way/button to pull up previous orders by customers which I’ve allocated orders to previously. I need to access this whilst bust putting their new order through, and potentially duplicate previous orders.

Any suggestions?

---

<div class="post-metadata">

**Author:** ![JTRTech](https://forum.sambapos.com/user_avatar/forum.sambapos.com/jtrtech/32/21270_2.png) [@JTRTech](https://forum.sambapos.com/u/JTRTech)\
**Post date:** [July 29, 2015, 7:31pm UTC](https://forum.sambapos.com/t/customer-ticket-history/6397/2 "2015-07-29T19:31:39Z")

</div>

Side by side viewing of last ticket I don’t think is possible.  
Duplicating might be… thought I saw a similar topic somewhere.

A simpler solution might be to add a new field to the customer entity of last ticket ID, make a rule for on ticket payment if customer entity is not null set the entity field for last ticket as the ticket id.  
Then make an automation command to reprint that bill using the customer entity field last ticket… Probably the closest youll get to side by side viewing last bill while making new ticket.

Do a search for print last bill button which will give you most parts, just adapt to set the entity field rather than a program setting.

---

<div class="post-metadata">

**Author:** ![pizzaeilat4](https://forum.sambapos.com/user_avatar/forum.sambapos.com/pizzaeilat4/32/461_2.png) [@pizzaeilat4](https://forum.sambapos.com/u/pizzaeilat4)\
**Post date:** [July 30, 2015, 12:17am UTC](https://forum.sambapos.com/t/customer-ticket-history/6397/3 "2015-07-30T00:17:18Z")

</div>

@Neil  
Try This.

> [@Question About entity last order](http://forum.sambapos.com/t/question-about-entity-last-order/745):
>
> Hi Again Samba team, I’m trying to create a rule That will show me the last order of the customer entity selected., But the “load last order” action does not work How can I make it so that when I choose an Existing Customer I could automatically receive details of the last order that he performed such as date, time, order items and the amount paid. what information can be displayed and where they will be displayed Is it possible at all??

---

<div class="post-metadata">

**Author:** ![QMcKay](https://forum.sambapos.com/user_avatar/forum.sambapos.com/qmckay/32/27925_2.png) [@QMcKay](https://forum.sambapos.com/u/QMcKay)\
**Post date:** [July 30, 2015, 5:39pm UTC](https://forum.sambapos.com/t/customer-ticket-history/6397/4 "2015-07-30T17:39:47Z")

</div>

Which will lead you to this …

> [@Recall & Clone (Customer) Last Ticket (2 methods)](http://forum.sambapos.com/t/recall-clone-customer-last-ticket-2-methods/3104):
>
> Here are 2 different methods to recall a Customer Last Ticket and Orders, and optionally Clone the Ticket. Personally, I prefer the 2nd method because it is “cleaner” and avoids unnecessary prompts. The first method (this post) uses Entity Custom Data to store the Last Ticket Id and an Ask Question Action to determine if the user wants to Load Last Ticket. The second method (2nd post) uses Entity State to store the Last Ticket Id and 2 Automation Command buttons to Load and Clone the Last Tic…

---

<div class="post-metadata">

**Author:** ![Neil](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/n/839c29/32.png) [@Neil](https://forum.sambapos.com/u/Neil)\
**Post date:** [July 31, 2015, 7:49am UTC](https://forum.sambapos.com/t/customer-ticket-history/6397/5 "2015-07-31T07:49:28Z")

</div>

Thanks QMcKay!!! This was really helpfulp, and seems simple for a lay-person like me!
