Caspio Bridge
Welcome to Caspio Bridge Ideabox. We love to hear your improvement ideas.
391 results found
-
Allow keyword parsing in a Search Field to be turned off
When using the "Contains" comparison type in a Search Field the basic behavior is useful in many cases, but it can also be problematic. It would be nice to be able to choose whether or not what was entered would taken as a single Literal rather than Parsed.
Here is the issue in more detail.
Contains | Does Not Contain
Keyword is searched within a text field or a file name field. If multiple keywords are entered in the search field, AND operator is assumed between them. User can also provide a desired operator by entering it in ALL CAPS
(reference: …3 votes -
Allow the Rules for fields in a Search Form to have the "Required" Action in the same way they do for a Submit Form.
In a Submit Form when you create a Rule it can have an Action to make a Field either Hidden, Disabled, or Required. On a Search Form the Required option is not available, but it would be nice to have. The option exists to directly set a Field to "Required" in both a Search or Submit Forms. It is just the functionality to so so dynamically via a Rule for a Field in a Search Form which is missing.
3 votes -
Allow for custom link to be entered and displayed next to download button in gallery report
Allow for custom link to be entered and displayed next to download and search buttons in gallery report
0 votes -
should add a bulk file upload function similar to social networks like Facebook
for example in a real estate application when a property owner needs to upload up to ten files of his advertized property and he wants to do it all at once...
8 votes -
Allow a horizontal gap between header and first row of data in tables
For style reasons it would be great to be able to have a blank separator between the bottom of the header row and the top of the first row of data in tables. Presently, CSS margin code has no effect, and while padding in the header helps, it does not solve the problem - particularly if the header is a contrasting block of color to the rest of the table. Thanks
1 vote -
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 -
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 -
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 -
"Limit to List" Option similar to Access
When typing a table/lookup view to a field, there is no way to force the user to ONLY select the options listed. In Access, this was really easy, you attached the "lookup table", and on the form page select limit to list. This forced the user to only to pick from the list available to them. This helps maintain data integerity. We get you can accomplish this in a dropdown, but need it in all other options, "autocomplete", "Cascading autocomplete". The reason we do not like the dropdown is you lose the contain feature, but by gaining the contain feature…
1 vote -
Add Custom Sorting for DataPages Other Than Alphabetical
It is a common requirement where lists would need to be sorted by criteria other than the first letter. I often need to sort by the day of the week, or by the month, or by something else where the correct order is not alphabetical. There is no way to sort by anything but display on DataPages. There is only a choice for field and A-Z or Z-A. I don't get to choose, so my days of the week start with Friday and end with Wednesday.
2 votes -
provide parameter translation for data pages without forcing whole-app migration
As it stands, only whole-app migration (export and import) brings parameters across as parameters. This is essential when using parameters to store page-keys, which is essential for page-to-page movement based on user actions and button clicks etc.
If we export selected pages only, then the parameters get resolved into static values, and that too the values as relevant to the source instance, which renders pointless the whole purpose of parameters because they are all wrong in the destination instance.
2 votes -
Hide html blocks using rules
It would be nice that HTML Blocks inside Datapages could be hidden by using rules.
For example, I use "<a href="#">My Link</a>" in the HTML Block but I want it to show only when cretain fields are not blank or any other criteria I might need.
0 votes -
App Parameters in the Custom Values in Dropdown field
It would be useful if we could use App Parameters in the Custom Values when 'Lookup and custom values' is set for a drop-down menu input field
3 votes -
Hide doublets, by selecting fields in wiews or datapages would be nice.
If i want to find some unique fields in a table or a wiew I have to export
to excel, take away doublets and import again.1 vote -
In Logic tab there should be dynamic comparison at right hand site
In Search and Report wizard or in creating views at right hand site there is option of putting values which happens to be fixed. But like other database there should be option of selecting value dynamically either by query from tables or by variables as right hand side value for comparison. Also there should be option for "in" or similar operator to match all or any value from the list
1 vote -
Ability to require at least one checkbox from a group
We've had requests from our business partners to have groups of checkboxes where the user needs to select at least one option. (A "please select all which apply" situation).
We can't have each checkbox itself be required because not all apply to each user. Radio buttons don't work because some users will need to select multiple options.
Being able to create a checkbox group with an overall "at least one" requirement would be great. Right now the only option is to use custom JavaScript to validate it.
Thanks.
3 votes
- Don't see your idea?