Member Question: What kind of custom fields and types do you use Jermaine?

Questions by Edward Rodriguez. For WHERE to position all the custom fields created to be used with your plugins, do you suggest to create a particular tab, or divide them in 2 tabs, or 3? Do you have an already predefined list of all the custom fields that are used for your plugins so we sit down and do them all on one sitting? OR... could you provide a screenshot of the name and order of the tab you have so I can re-created it?

This is an excerpt. You do not have sufficient rights to view the full content.

Leave A Reply (6 comments so far)


  1. Zeyad
    6 years ago

    Hey Jermaine,

    I\'m working on these custom headers now and as I was looking at the prospect info tab, one question that came to mind was in relation to the questions underneath the free videos or the polls, why would we opt to store that data in a custom header rather than just tagging them when they pick a particular radio button through a webform?


    • J Griggs
      6 years ago

      Zeyad, this is a good point.

      As long as you remove any other tags, resulting in them only having ONE tag per question, you\'ll be fine. It hasn\'t always been easy to tag based on checkboxes and radio buttons. If running out of custom fields were an issue, not making them actual custom fields and simply tagging people based on their response can definitely work. Heck, it may be what I end up doing as time progresses (keep in mind, I created many of my processes in 2008 and things change over time).

      Thanks,
      JG


  2. Dave
    6 years ago

    This is the jackpot (literally) - jonathan


    • J Griggs
      6 years ago

      🙂


  3. Yusuf Mullan
    5 years ago

    Hi Jermaine,

    For the rating related fields, above you mentioned WHOLE NUMBER.

    Shouldn\'t they be (or could they be) drop downs, like:

    5
    4
    3
    2
    1


    • J Griggs
      5 years ago

      No, because that\'s the same thing as them being A, B, C, D, E. You wouldn\'t be able to do greater than, less than, greater or equal, less than or equal, which saves you a lot of time when wanting to do ranges like ratings of 3 and below... or 3 or above. Or do averages when you add to dashboard stats widgets. There are a number of reasons but whole number field type is VERY important. Plus drop down would require the answers all prepopulated (not a problem when doing \"1-5\" rating but definitely in other internal data situations) , therefore putting a cap on the field. Whole number can keep counting forever (in the case of counters, total spent, and other internal data). Leaving fields open-ended can never go wrong.

      You can always take a whole number field and convert it to a drop down by googling html code for drop down menu. This is covered in module 2 and Q&A sessions.

      All the best,
      JG