New Custom Field Not Available

  • Resolved taylormarketer

    (@taylormarketer)


    6 years, 5 months ago

    I created a new custom field in Infusionsoft around three hours ago but it’s not showing as a selectable option in the field mapping list: https://screencast.com/t/2JiQQB5JvG

    I cleared my cache and re-submitted my API key via SDK. Still not working.

    Any other ideas?

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    Hi,
    Which field are you looking for?
    Perhaps the field type is not mappable? What’s the field type in Infusionsoft?
    Also, are you on the most recent plugin version?

    Thread Starter taylormarketer

    (@taylormarketer)

    Hi! Thanks for your quick response.

    Field Name: “Number of Background Checks Done Annually (Radio)”
    Field Type: Radio (is that mappable?)
    Plugin Version: 2.2.3 – Is that the latest version?

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    Yes, radio is mappable.
    What am I missing? That field is in the list according to that screenshot?
    However, I do see those duplicate standard fields. That’s another issue. I’m not sure how that is happening.
    Is there a direct link to that GF page?
    If not, are you willing to export the form and send it to me? I’d like to see its definition

    Thread Starter taylormarketer

    (@taylormarketer)

    It finally showed up. Must have been delayed somehow.

    We have two custom fields in Infusionosoft with almost the same name. The one you were seeing is a text field. The new radio field I’m trying to map ends with “(radio)”.

    I’d be interested to know about the duplicate standard fields, too. Here’s a direct link to the form: https://peopletrail.com/request-quote-now/

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    We think that the issue of duplicate standard fields was related to corrupt cache. The issue should be resolved in the 2.3.1 release.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘New Custom Field Not Available’ is closed to new replies.