Had some more thoughts about this.
I’m trying to find a way I can do this which avoids a custom table, but which lets my client manage the table of data.
I realised that I can use the repeater field to capture the data and then query it in a template that spits out JSON. My templates can then query that JSON. So that’s awesome.
What would make this great however would be a select field that can be automatically populated with the unique key of the repeater field data, say Suburb.
That then creates the link between the lookup table (my repeater field) and the place where that lookup table is needed (say a page template for listing office locations for example).
The concept of a select field being able to be populated by an external source seems to have fairly broad application too.
What do you think?
