Structuring Appsheet DB/Table/Data

I’m moving some data from Google Sheets into Appsheet Database/Tables, which I do see is in preview. It’s not the most complicated stuff, and I’m using references.

So my main concern is to track people – and people belong to offices, have emails/phones, and achieve certifications. So I’ve made tables for offices, and all related data. emails/phones are simple columns – but certifications is throwing me for a loop. I started by creating a table of certs, and then made a reference to that in the original table – so a person ends up with a column, that is an enumlist, generated from that table.

but certs have two dimensions of data, once a person achieves one. one is the name of the certification – easy enough – but the other is the date they got it. that date can’t go in the certs table unless it’s blank, cuz it’ll be different for everyone.

how should i be structuring this?

With another table… don’t be shy.

Just add another table that has the actual certifications and not just the “certification types” as I use to call those tables in similar scenarios. The “Types” are the base from which you select your cert and then generate the actual one that’s tied to a certain person, date, etc

ok so i think i follow what you’re saying.

table that is types of classes (english, history, whatever)

table of classes that lists like (june 2022 english class, class type english, name bob, etc)

but how do you reference multiples? like in the name table, which has a column that’ll point to the classes table…how do you designate that this person was 22 classes they’ve taken?

I can’t understand fully your particular use case, but maybe you are thinking about it the other way around. Could you explain better your schema?

thanks for the help. i think th emore i think about it, i understand. i’ll have a table of types, a table of specifics which uses types, and go from there.