GF front end pod creation form not populating relationship field

  • I have a POD (Ornaments) with about 10,000 records.
    I have a Table Storage POD (Collection) which represents a member’s ownership of one of the Ornaments.
    There is a one way relationship field from Collection to Ornaments.
    I created a GF form to allow signed in users to create a Collection record on the front end. That form is accessed from the Single View of an Ornament record.
    I’m dynamically populating post_title, post_id and featured_image_id to the form.
    The relationship field is a CF (Ornament) on the Collection Pod. When that field is set to Required the form gets hung up and never creates the Collection CPT. When I remove the Required, the form creates the CPT but doesn’t populate the relationship field.
    The post_title and the featured_image are correctly included in the Collection record.
    I have tried matching both the post_title and the post_id to the relationship field but neither populates the field. Manually I can create the relationship by pasting the Ornament post title onto the relationship field and it will find a match, which I then select. When I imported 16,000 of these records, I matched the Ornament Post ID to successfully populate the relationship field. The Relationship field in the Collection POD is set to single select, autocomplete. Should I be matching the Ornament Post Title or Post ID? Is the Relationship field setting of autocomplete correct? The other settings cause a memory overload when creating a manual record.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    Following up on this today

    Plugin Author Scott Kingsley Clark

    (@sc0ttkclark)

    I wasn’t able to solve this one yesterday, but I do think this one is just indicative of the limitations of relationship auto-populating when there’s a ton of records on that pod.

    I’ll look at this and see if there’s any further tweaks that could be made.

    Thread Starter rimasu

    (@rimasu)

    I think you are right Scott. The manual process is pretty high touch, so trying to dynamically populate may be too much. I was primarily using the relationship to display details not available in the Collection Record. However, I changed it to eliminate the relationship and instead I’m displaying a link to the Ornament Single page view. If they want to see those details they can jump to the link and then jump back to Collection. Thanks for taking a look

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘GF front end pod creation form not populating relationship field’ is closed to new replies.