How can we improve WHMCS?

Share, discuss and vote for what you would like to see added to WHMCS

Ability to set a default for custom fields

  • Shawn Ort shared this idea 4 years ago
  • Order Forms
  • 4 Comments


It should be possible to set a default for custom fields including the check box field type.

For example and in particular, we have a customer field of "Assign public IP address" when using Hosting Controller integration. This is a checkbox and the default is UNCHECKED.

Ideally we could set the default in the product for this field to be CHECKED or UNCHECKED.

In this case we would have this set to CHECKED by default because everyone ordering a VPS is going to want a public IP address and the field is required by the integration or it won't assign a public IP address.

4 Comments

Login to post a comment.

Je suis d'accord, mais j'ajouterais que le problème devient critique précisément pour les formulaires avec un grand nombre de champs, ce qui est souvent nécessaire dans le secteur du casino. Sur des sites comme onlinecasinosausland.ch, où des données d'enregistrement spéciales sont requises, les valeurs par défaut économiseraient environ 15-20% du temps de traitement des commandes. Pour référence, sur https://casinoetrangerenligne.ch/ j'ai observé comment des plateformes similaires résolvent cette tâche via des modèles prédéfinis, ce qui est bien plus efficace que la saisie manuelle de chaque champ. Sans cette fonctionnalité, maintenir des valeurs cohérentes entre les différents formulaires d'ordre reste un processus manuel et sujet aux erreurs.
Adding the ability to set default values for custom fields like checkboxes would streamline product setup—especially for cases like “Assign public IP address,” where having it checked by default avoids errors and https://www.leewaytoll.com matches typical VPS requirements.
I agree, default custom fields would streamline things! Think about setting up a VPS, configuring "Assign public IP address" is crucial. It's like booting up Snow Rider, you want the perfect conditions from the start. Having that checkbox pre-selected saves time and prevents accidental omissions. A default value truly enhances the user experience and overall workflow, especially with required integrations. https://snowridergame.io
Agreed, we should be able to set a default value for any custom field. I have several fields I use when calculating custom usage and some that are Yes/No values. It's silly that there's no automatic way to populate these values to defaults.