GQL [Payments] table BUG

[QMcKay]

I was having deja vu here. I think this BUG reported a long time ago is probably the cause, and it has not been fixed …

GQL closeTerminalTicket() BUG causes subsequent Merge Tickets failure with Tickets that have partial Payments made by Entities that were changed

@Tayfun, please report this major issue regarding the GraphQL Engine to the appropriate parties… This issue is caused by GraphQL payTerminalTicket() mutation. That mutation fails to update [Payments] table columns [AccountTransaction_Id] and [AccountTransaction_AccountTransactionDocumentId] when done via GQL. SambaPOS updates these columns properly. EDIT: wow, that ^ too is incorrect. The payTerminalTicket() mutation DOES update the [Payments] table properly. It is the changeEnt…

EDIT: yup, take a look at that, same bug, still not fixed …

SELECT
 p.[Id]
,p.[TicketId]
,t.[TicketNumber]
--,p.[PaymentTypeId]
--,p.[DepartmentId]
,p.[Name]
,p.[Date]
,p.[AccountTransactionId]
,p.[Amount]
--,p.[TenderedAmount]
--,p.[UserId]
--,p.[TerminalId]
,p.[AccountTransaction_Id]
,p.[AccountTransaction_AccountTransactionDocumentId]
,p.[Description]
,p.[ExchangeRate]
FROM [Payments] p
JOIN [Tickets] t on t.[Id]=p.[TicketId]
WHERE 1=1
and p.[PaymentTypeId]=4
and p.[AccountTransaction_Id] is null
ORDER by t.[TicketNumber], p.[Date]

---

@Tayfun, please refresh the Developers regarding this bug that was originally reported January 21 2018, since it has not been fixed (running SambaPOS 5.2.3 [2017-11-25 10:44:00]).

Direct them to the Topic linked above for a good walkthrough on steps to reproduce the problem and the Cause of the Issue, or the next post which has a video showing the Cause of the Issue …