Populating parent and child pod transparently
I have a few pods on a portal, such as restaurants, lodgings etc all which have a set of location fields. I'm tempted to create a separate 'location' pod with lat, lon, icon etc to make map population as quick and simple as possible. There will only ever be a one-one relationship with between the main pod record and location pod record. Clearly I want the user to be able to add/edit the details for the main pod and child pod in the same form.
Is this possible with UI? Is there a better approach?
Thanks
1 Answer
I think you're making things more complex than they need to be. I have a similar setup on one of my sites. I allow users to input points of interest. There is geocode information in the pod, but it gets automatically added at first display using Pods API. I don't allow the user to ever see the geocode information.
For speedy queries, you can cut down on the columns you load in your findRecords call.
