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 the SKU and event Id into description, then split it apart later once the purchase is made, but it doesn’t look like that information comes into the App:Sales sheet.
* Disclaimer, I started with the following idea, but the IF-THEN-ELSE column doesn’t allow me to compare to column values, so the following won’t work, but I’ll post it anyway in case it gives you ideas.
One last idea is to have the choice component for the plan choice.
Create a lookup in the data tab to get the SKU for the selected plan
Create a template to join the event id and the SKU.
In the sheet use the formulas to join the event id and SKU and get all of the other details you need (price etc.)
Back in the data tab, create an IF-THEN-ELSE column that will compare the template Event/SKU to the Event/SKU that’s set in the sheet. (This is where I realized this idea wouldn’t work. We really need the ability to compare 2 columns. The intent was to create a true/false value to hide the buy button until the template id/sku equaled the sheet id/sku)