We have some custom fields that are collecting the same information but they have - and require - use case specific help text. I would like to be able to assess the effect of creating these semi-redundant custom fields. Aside from conflicts with tags in drop-downs; should I be concerned about creating cruft on the backend?
Best practices on when to create semi-redundant custom fields
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
If these fields have different names/descriptions and is only visible to your agents I don't see any possible issues that can happen aside from what you have mentioned that it is indeed redundant.