| No, you’ll only get “someprefix1”, and about 14 similar variants. What you need to do is either prepare a reasonable prefix valid for all (or at least most) users, or have the documentation to be dynamically prepared for each user, with a dynamically generated appropriate prefix for each user. Alternatively, you’ll have to teach users what kinds of prefixes would be appropriate, with an example which is obviosly not appropriate for any of your actual user. This will take some length of text to explain, and many users will not read it, and may instead abandon your service. Relatedly, I’ve always disliked when programs force me to name N number of things without adequately explaining • What the names are (Is this some kind of group name? Instance name?) • How the name will be shown. (Should I prefix the name with the company name myself, or will that always be visible? Will this name be shown together with numerous other names which are all UPPER CASE? Will the name be automatically converted to lower case?) • If any of these names will be publicly visible. • If any of the names can be changed later, and how hard it is. • What characters are allowed (Are spaces, underscores, or dashes allowed? How about Unicode? Emojis? What is the normal naming scheme?) • How long is the name allowed to be? (Will it be silently truncated at 8 or 16 characters (or grapheme clusters)?) |