So as most of you know I have developed my own credit card integration which has been working great and was an awesome learning experience until official integration comes. With this integration I have went out of my comfort zone significantly with learning SambaPOS features and also currently also noticing some limits slowing the system down.
With the Credit Card Integration, I needed a way to store transaction information for every credit card transaction. I also need to show that information in my printed receipt for the customer. So what I did is I saved transaction information as Tasks and then for ticket printing I call a script inside printer template to insert all credit card transaction information in the printout.
This worked great for 3-4 months of saving a lot of transactions 7 days a week. Now the Issue came up when the client called me saying his credit card receipts are taking over 25 seconds to print. This is a huge issue for them as they get slammed busy and need everything to be snappy fast performance.
I have verified that the printing is taking long because all those scripts querying credit card transaction data are running slow.
So with Task Types I have made the assumption that we can use them to store and query a large amount of data very quickly? Is this a bad assumption to make when working with Task Types?
If I am understanding this correctly… a single = checks if the number value is equivlent… Double == checks if a string is equivlent? So techincally if we use your ternary expression we shouldnt need quotes and a single = should work? If I manually type in ticket id number for ex. 23424 then it works fine. Techinically speaking 23424 should be equal to [=TN(’{TICKET ID}’)] but it seems in this situation its not lol.