This insider video just went live today which gives us the first look at the new custom fields in action. Please comment below the video and tell everyone how you plan on utilizing the new fields coming!
[trafficplayer_youtube_video width=”560″ height=”315″ src=”http://www.youtube.com/embed/EmxPuXp-i6A?&autohide=0&autoplay=0&controls=1&hd=0&rel=0&showinfo=0″ ][/trafficplayer_youtube_video]
We have been waiting a long time for custom fields. This is going to be great. I plenty of ideas, but I want to wait until I get a chance to get in there and work on them first before posting here.
However, one thing I know we will do is use a another field for to confirm email. Last week we lost a last minute gig because of a typo. The client typed in .ocm instead of .com.
We didn’t catch it and responded to a bad email and lost out as they booked someone else.
Franc
Wondering if this might lift one of the previous limitations…
Could we use the per-order fields so that if someone fills out a form more than once (with the same email), or if we have multiple shows for the same client it doesn’t overwrite previous data?
Hey Jeff,
Thanks for your post. Since you have the additional fields now, you could create duplicate field names for the ones you don’t want to replace. You would still need to move that data to the secondary set of fields otherwise it would be replaced if they filled out the form again. There are tricks that we can impliment to do that so after a show was completed, you could “archive” it by hitting a button. It would duplicate that data into the secondary set of fields you’d have set up to match the originals. And there maybe other ways as well…