Caspio Bridge
Welcome to Caspio Bridge Ideabox. We love to hear your improvement ideas.
1134 results found
-
Convert submission data to Plain Text
Currently, submission data is not converted to Plain Text, which can cause text errors in the Table where the submission data is stored.
For example, if somebody goes into Microsoft Word, and copies quotation symbols “” or bullet points •, pastes it into a Caspio Submission form, and presses submit, the data is not converted into plain text, and the result is a � symbol or "�" in the table data.
However, if the text were converted to Plain Text during the submission process, the quotations would be converted from “” to "" and the bullet point • would be…
3 votes -
Add cascading option in result page
This is really an essential feature when making a report. For example, based on "class name", the "class room" from another table should be able to be displayed in the result page.
1 vote -
Field populated from a list should be available as a parameter in a calculated field.
A field should be able to populated from a list and be used as a parameter in a calculated field as well. This is a basic expectation, but is not possible due to a Caspio limitation.
1 vote -
1 vote
-
servant
App which visitors can select food on at restaurant and appear the order in a kitchen screen
1 vote -
Scheduled Tasks Have an Option Type: E-mail
I notice when doing a scheduled task, there is no option type: E-mail. Having this option will be nice when scheduling a task from desk or Jira. So users don't have to pull it from a website or create a server or have third party. That way we can transfer a data excel from email to caspio during a schedule time.
4 votes -
Allow vertical size of tables to be smaller
Allow the table sizes in the relationship view to be smaller. Right now there is a limit on how short you can make the box and that makes it more difficult to see all the relationship connections. It would be nice if small tables didn't use up as much vertical real estate in the ERD.
2 votes -
Allow single edit records in list type report like it is in tabular report. Right now the only option is bulk edit.
Allow single edit records in list type report like it is in tabular report. Right now the only option is bulk edit.
4 votes -
Search form input feature needs more capabilities
The data search form has a feature that provides a capability to input data in top row, that matchs the output fields.
Currently only the auto number data field is uneditable and auto populates, the rest of the fields we either have to populate or make the blank.Desired feature:
If from a search result there are 10 fields that are output, we may have 3 fields that are constantly the same and we want those to auto populate from a table with display field, we need that capability.Example:we have a project and we use a search form:
We…1 vote -
lightbox for Details Page
It would be nice to be able to open the details page in a lightbox. This is especially interesting for the calendar because you cannot make any changes in the result page so every time you have to open the detailspage in a new Browser-Tab. Have you ever thought about it?
1 vote -
4 votes
-
Add a SUM field as a data type to perform cross-table tabulation
I chose Caspio over a newer competitor of Caspio because I could have a LITTLE more latitude using Caspio....however, I nearly went with the competitor because they had a SUM field option, that I could set up in a separate table and sum amounts in another table based on criteria determined in my current table.
This functionality is sorely missing. It was the basis of my first support ticket with Caspio. I was told "if you are looking to have a table value updated based on some action or value changed in a different table, this may require a trigger…
0 votes -
Custom prefix/suffix for tables, views, and datapages when copying an app
It would be super helpful to be able to specify a custom prefix or suffix for all copied elements (connections, auths, tables, datapages, etc...) when an app is copied so that they can be more easily kept separate when creating development versions or upgraded versions of apps.
1 vote -
Add a "Show" action under the Rules tab
The current Rules tab features only four (4) possible actions: Hide, Disable, Display Only, and Required. Some customers have workflows that require the "Show" action, but were unable to do so because this option is not available. It's also because the Rule actions, just like other features like table views, are built on NEGATIVE logic, which is sometimes hard to grasp.
The current workaround, which I find tedious and error-prone, is to use the Hide action to implement the NEGATIVE/opposite logic of the required "Show" criterion. For instance, if you want to SHOW a text field named FirstName if…
3 votes -
Copy/Paste Logic Elements
Allow copy and paste field value logic elements to speed creation of large logic blocks.
3 votes -
Enable rules on tabular reports
It would be very helpful to be able to set rules on tabular reports so we can set restrictions based on user auth fields.
5 votes -
1 vote
-
1 vote
-
Apply SQL 'AND' clause when creating a view
This would be helpful for restricting tables before doing the join when creating a view. A possible workaround would be giving the option to link a view with a view. This is very valuable for historical type tables.
For example:
I have 2 tables, I need to filter table 1 before joining with table 2.
Customer table:
Customer | State
A | S
B | V
C | LEntry table
Customer | Entry | Category
A | 123 | D
A | 325 | C
A | 496 | D
A | 3874 | M
B | 3478 |…3 votes -
1 vote
- Don't see your idea?