@EcomGuy - this may not be exactly what you are commenting about across the various posts today, BUT it is not that difficult to create something like a random number generator on your own, as a workaround

here is a simple little form i put together to try and address the issue or at least to demonstrate how one could ask a simple question of the user and then create a random code. 

It’s not rocket science, at least according to the 7 other voices in my head, to create a work around to the issue - at least this one works for me. 

des

Since you replied the same on  my post, I will reply the same to each one of your replies... Having the end user make their own code is not going to cut it. Frankly, it is the best way for us to just throw our market research dollars out the window in the paid survey world.   Sadly too many folks come in to a paid survey to get quick $$ and give bogus answers.  We need to have survey taker accountability with trace back codes we generate.  This is how we remove bad data and reject/block bad actors.  Bad actors will game the system with your “workaround”.  Let’s move on from AOL 2.5 and get us a random codes generator so we can confirm and approve completed good work by our survey takers.  Thank you!

Hi @EcomGuy As Des mentioned, this isn't a feature we currently offer. While this isn't the most ideal solution, the workaround Des provided is one way to still generate unique codes within the forms. Of course, you certainly don't have to use this workaround, but I'd definitely suggest taking a peek at how he's set this up to see if this would work for you since we don't offer this feature natively in our forms.

The upside is that this workaround isn’t terribly hard to setup. You can see an example of the logics set below. If you haven’t already, I’d suggest giving it a try! 

Hi,

This should work for my use case but I’m not seeing how the random code generated by the calculations are passed through to the “results” page. Can you clarify that step?

Hi @smpomory Once you have this all setup, all you need to do is recall that variable on the ending page. 😀

So 3 years after this obvious, easy to implement feature was clearly needed . . . 

literally ignored by TF - which I’ve come to learn is exactly their attitude toward every single failure of the product: “it’s your fault for needing it, figure it out yourself”.

The provide “workaround” literally does not randomize. Many people will enter 11111, and every one of those will yield the same end number no matter how many times you manipulate it. 

At best you can say that all of those identical results “probably” went through your number machinator. 

Hi ​@bh2022 Thanks for stopping by and sharing your feedback. I definitely understand how us not implementing this feature appears as though we’re ignoring your requests. I promise, we’re not trying to! Our team has been working this last year on some other features with a few more requests, such as captcha and partial responses, which were much larger overhauls. 

That said, we do still have this feature in our list of features to consider. However, we provide workarounds for the time being to hopefully give you some ideas on how to work this out while we keep building features!