I would like to show one of 12 images in one table in hundreds of linked rows of ticket data

[Juwlz]

Hi

I’m creating my very first ever Glide project, so please be gentle with me, and explain things in simple terms, as I’m definitely still finding my way around with the help of multiple YouTube videos!

I’m also up against a tight deadline. We’ve been selling Advance tickets for a 3 day Music Festival over this coming Bank Holiday weekend, and the ticket data downloaded from the website is pretty horrid. But I’ve cleaned that up, ready to use.

I’m creating an app to check in ticket holders as smoothly as possible (taking into account the fact that not all members of a group will turn up together, a customer may have more than one order, and orders may have more than one ticket type).

The structure is basically in three tables:
Orders
Order ID, with relevant Customer info, and we want to be able to search on any of that (Order ID, Name, first part of email address, post code).

Tickets (linked to Orders by Order ID)
Once the people on the gate pick an Order, they’re shown the various tickets within that order.

Ticket type images (linked to Tickets by SKU)

And here’s where I need help. I would really like to add an image to the information they’re shown. I have 12 different ticket types (Weekend / Saturday / Sunday / Monday, for each of 3 age groups (Adult, Under 18, Under 8). The ticket SKUs relate to the images I want to use, but I’ve been unable to add and select a relation that will allow me to include the related image in the ticket line info.

I have a Detail Tab set up, with an inline list which allows the user to search for orders, and then click through to see the tickets for that order. That’s working well, with the second inline list being based on the relation between order and ticket, as in this screenshot - other than the missing image. The Action for the inline detail line is set to show a line from the Ticket dataset.

It’s within this view that I’d like to be able to add the image for the appropriate SKU, to make it obvious whether it’s one person who’s bought a ticket for each of two days (two different shapes and colours) or a group of people of different ages all coming on the same day (all the same basic shape and colour).

e.g. ticket 1054 is for tickets in all three age brackets, all for Sunday, so they can all be checked in together (if they all arrive together)

But ticket 1059 is 2 tickets for 2 different days, so we don’t want to check them in for their Monday ticket when they arrive on Saturday.

The images will not only make the app look better, but they’ll also help to prevent errors when people are checking in.

Although I’ve set up the relation between the SKU and images in a Glide table with the ticket lines (currently 600 and growing fast - with just a small fraction of those in my test data), I haven’t been able to select the relationship anywhere to pull in the images for each of the ticket lines to be able to display the lines with the images, whilst also only displaying the correct ticket lines for the order and details about the customer from the Order. The relationship just doesn’t appear in the drop down list for me to choose from.

I know I’m probably missing something fundamental, but I’m struggling to work out what.

Help!

Thanks in advance
Julie

[Juwlz]

Order 1054 - different age groups, all on the same day

[Juwlz]

Order 1059 - the same person on 2 different days

[Juwlz]

The images and their relation to the tickets (in my small set of test data).
Most of the data is in Google Sheets, but the images are a Glide table.

Sorry for the multiple replies, but as a new user, I can only post one image at a time

[Jeff_Hager]

I’m not sure I’m completely following what connects to what in your data, but a relation is a connection to an entire row or an entire set of rows. If you need a specific item from that related row, then you can use a lookup column to retrieve a specific column from the relation.

It’s hard to say for sure, but it seems like you should have a relation from the tickets table to the materialistic-egg table. Rather it looks like you have it the other way around. If you create a Single Relation in the tickets table, then you can link the ticket SKU to the SKU in the materialistic-egg table. Then use a Lookup column to return the image for each ticket. Then you should be able to use that lookup column as an image when viewing the tickets.

[Juwlz]

Thanks Jeff

Order ID is the column in both Orders and Tickets which is the relationship between them.
Lineitem SKU in the Tickets dataset is the relation to SKU in the materialistic egg dataset.

I think I did try setting up a relationship from Ticket to materialistic-egg first, but I’ll check, and try it that way. I still may need to work out how to get the related image into the rows displayed for the Tickets from the Order, but I’ll give it a try.

Thanks
Julie

[MattLB]

Did it work? You have a relationship from “egg” to all tickets via SKU.

Next
a. create a relationship back between the ticket and materielistic-egg relating ticket SKU to ‘egg’ SKU
b. create a lookup column in the ticket table and bring in the SKU Image

I think your done, you have access to the image in your ticket in-line list.

good luck!

[Juwlz]

Ah … the missing link. Or rather, the missing Lookup.

As I thought, I had already created a relationship from Ticket to materialistic-egg, but I couldn’t work out how to use it to show the image.

I could see the relationship column in the ticket dataset, which is showing me the images which is why I was confused that I couldn’t actually select the images in the list.
The bit about a LOOKUP Column in the data grid had escaped me. I was looking for somewhere in the design page to include it.

That you very much! That will help a lot.

[MattLB]

As a rule it seems Glide really likes wide tables. Things normally considered ‘design’ elements are often/usually created in the table-row. Like bringing in images, other data and especially creating custom labels.

For example, you could use a template column to combine the date and the ticket type so it might be more legible. It could say on one line: “Sun 28 Aug: Child 0-7” or “Sun 28 Aug: Adult”. This would all be done in the table-row using the template column to create the “label” which you would then use the built-in Glide typography (title, details, caption, etc) to display.

have fun - looks great

[Juwlz]

Those are really useful tips. Thank you.

The big takeaway here, I think, is that the Data view is where all this kind of stuff gets done. I’ve been going round and round in circles trying to do it in the Design view, which is why I was struggling.

A Template column sounds like a good idea, as I was actually thinking that it would be beneficial to combine Day and Age in much the way you’ve suggested, but I had planned to do it in the spreadsheet (I’m creating the data from what I can download, and then copying and pasting VALUES to get data for Glide to use), but I suspect it’ll be more efficient to do it in Glide itself.

The person who initially set up the website and the purchasing on it just used the default SKUs he was offered (basically the same couple of letters and what might as well have been a 6 digit random number ). There was no logic to them at all, so I’ve had to go through all the early tickets substituting old SKUs for new with a global replace in the spreadsheet. Apart from anything else, it has made ticket sales analysis much more straight-forward.

The SKUs are NOW logical: Day (where 0 = all weekend, and 1, 2 & 3 are the first, second and third days)
A=Adult
B=in Betweener (Under 18)
C=Child (Under 8)

The rest of it is just related to when the tickets were bought (Early Bird pricing or not) - which makes no difference to the checking in - and a human-readable day of the week or “Weekend” on the end

I’ve actually done quite a bit of pre-processing on the data coming in from the website (which is horrible) to split data out of the SKU, rather than relying on picking it up from less consistent places, but I may rethink this.

I’ll definitely have some more questions, but it’s late enough that if I keep going now, I won’t be thinking clearly enough.

Thanks again to both of you, Jeff and Matt.