Unfortunately, "Random" field types are not supported in our installation at this time. Perhaps an alternative may be to use the CMS template API to generate random numbers and insert this into G2 search as an "int" field instead. You can then sort on that "int" field to give you a static random order. Static meaning that the order won't change on successive queries to search unlike with the "Random" field type where you can use different seeds in your query to change the order. The order here (eg. random number) would be generated at publish time via the CMS template API and won't change until the next publish. Hope this helps!
This approach won't produce a random order on every query...
This approach won't produce a random order on every query so won't have the effect that most customers want.
The closest that we were able to get to a random sort order was to do two queries: the first query brings back no rows (rows=0) but does give us a search result count. We then generate a random number on the client between 0 and the result count less the number of required results; then re-query asking for rows=required_count and start=random_start.
Is there a way to preserve the random sort order while paging? As it stands, the results get re-randomized with this solution every time you fetch a new page of results, even when using the same sort seed value. This is obviously undesirable.