Hello. So I am writing logic to match “App: Sales” entry as it happens (row inserted) event to what the user was trying to buy. In my case, a user can purchase multiple instances of a service I am offering via my App. User can try multiple instances of my service in trial mode and then decide to pay…

hmm, that surprises me, but like I said, I haven’t really played with the buy button. I did give it a try in staging and now I see what you are talking about. I wonder if that’s something Glide could change since this is a good use case. I was thinking you could use the template column to encode …

How to handle this with "App: Sales"?

Feature Requests

mthakershi February 12, 2020, 6:06am 9

Thanks Jeff. I keep exploring this. But if those two attributes of the buy button start acting like the first three, it would be really great.

1 Like

How to pass on complex SKU to Product ID buy button?

Topic		Replies	Views
Lifetime membership access, how to access App:Sales Ask for Help	41	1243	January 30, 2022
How can I proceed mutiple user's entry to the data at the same time Ask for Help	3	209	July 12, 2023
Accessing App: Sales data to filter what the signed in user sees Ask for Help	4	572	February 11, 2020
Paywall Request 🔑 Feature Requests	18	1427	January 6, 2020
Crosscheck Over Row Owner Ask for Help	12	249	August 31, 2023

How to handle this with "App: Sales"?

Related topics