Dave
My feedback
11 results found
-
33 votesDave supported this idea ·
-
6 votesDave supported this idea ·
An error occurred while saving the comment -
4 votes
An error occurred while saving the comment Dave commentedJust a thought - you could add a sort order column to your table.
-
7 votesDave supported this idea ·
-
44 votesDave supported this idea ·
-
7 votes
An error occurred while saving the comment Dave commentedThis is a good enhancement request... and the converse would also be useful. For example - I have a lot of calculated fields that are custom SQL. Caspio permits me to write custom SQL but ignores it when - for example - table or field names change. You've clearly got the capability to do this, and by not recognizing the sql you make it easier to break things.
-
3 votesDave supported this idea ·
An error occurred while saving the comment Dave commentedThis would be HUGE. My app parameters vary across Dev/Test/Production. If I could set one or two "Top Level" app parameters and have them cascade down to other app parameters my releases would be far easier and FAR LESS RISKY.
-
2 votes
An error occurred while saving the comment Dave commentedGood suggestion. We implemented this custom with an outside vendor. It was one of the more costly elements of my Caspio solution. Happy to discuss.
-
10 votesDave supported this idea ·
An error occurred while saving the comment Dave commented100% agree - there are some basics of formatting and validation that would eliminate a TON of custom code (and risk) from my "no code" application. Field masking, formatting and validation - phone numbers, ssn, email, numeric only,
-
195 votesDave supported this idea ·
-
1 voteDave shared this idea ·
This is absolutely huge. A systemwide parameter would reduce release management risk by about 75%. Manually editing app parameters - especially long ones is messy.