Hi,I have 3 questions
1-I want to prevent that users couldn’t be able to enter number(e.g. cellphone number) into a based on text field in a Form
2-when users want to enter a price into Number Entry,they could be able to view price with group separate during typing(e.g. $12,000)
3-My Users will be personal(they will use a gmail,yahoo,…)and not a firm.So in this case is the Maker Plan suitable for me?
Thank you for helping me
Yes. So which plan is your question directed towards? Through a paid plan, you can use a native form with CSS features or vice versa, you can only use a custom form to prevent it.
I only can upgrade to Maker Plan because of unlimited user number.My app will have more users(maybe +1K)
That should be enough. Have you read all the features? Using native forms will reduce your update usage.
I don’t emphasize enough that the number of updates in the maker plan is calculated if it is related to sync with other parties, for example g. sheets
1-I want to prevent that users couldn’t be able to enter number(e.g. cellphone number) into a based on text field in a Form
You can add a JavaScript column that returns True if text contains any digit and make, for example, continue button visible only when that column is False. In advance, add a hint to let user know to do not include numbers. Hope it will help
thank you that was very helpful but I don’t know Javascript 
Do you want to limit it to all numbers, only contain all alphabets or can it contain alpha numeric?
only numbers 0~9
FYI in the maker plan is unlimited updates when using glide tables. In the case of a custom form writing to a glide table it’s unlimited updates.
If I understand correctly the 500 updates are for external sources, webhooks, etc…
You write it in the javascript column, and for p1 point to your input column.
If you use a custom form, you should have a usc column. If not then this will still be input even though you already have this javascript column.
function containsNumeric(p1) {
const numericPattern = /\d/;
return numericPattern.test(p1);
}
return(containsNumeric(p1));
For this case, if you use a custom form, you can use the set column value action on the submit button, rather than asking the user to input the same thing and risk making mistakes.