Caspio Bridge
Welcome to Caspio Bridge Ideabox. We love to hear your improvement ideas.
149 results found
-
Add SQL capability when creating a new View.
Add SQL capability when creating a new View. I believe this would be very useful to generate aggregate totals like:"Max(), Sum(), Exists" and concatenation of values. This view should also be available for scheduled downloads .
15 votes -
Ability to have calculated fields on a view.
In SQL I can create calculated fields for a view it would be nice to be able to do that same thing in Caspio view.
139 votesThank you for this idea. We are looking into adding this feature in future product updates.
-
Create a JSON output feed from views or tables
What would really make Caspio powerful is to have a way to create a JSON and/or XML view of data that could be accessed dynamically by web applications. I want more flexibility in how I present data, and I'm willing to develop that myself, but I could still use Caspio as a back end to enter and manage and store data, without having to build that infrastructure myself every time.
19 votes -
Date format in table
It is a good feature if the Date format can be changed in the table level. Currently, the date values are stored in the tables in the format MM/DD/YYYY.
22 votes -
add a semicolumn as separation character for importing ,csv files
self-eplanatory, I think
1 vote -
Need to access password field in triggered action to filter if blank/not blank
You make it impossible for us to determine if a customer activates his/her registration. Cannot filter on unblank password fields in triggered actions. Can't set a yes/no hidden field in password reset datapage (see other suggestion just added). Need these fields opened up!
1 vote -
Caspio must support "group by" and Calculations in views, not only in datapages.
This option will allow us to create views that groups the records of a big table based on some distinct criteria. Also it is necessary to make simple calculations such us sum, or count in our tables without the need of datapages.
106 votes -
drop and recreate the triggers
Triggers in database should be dropped and recreated while performing migration from one instance to another, right now it is creating duplicate trigger each time we migrate schema
1 vote -
Use views in triggers
You can currently only reference tables when building a trigger. Adding the ability to reference Views from triggers would be very helpful, rather than having to rebuild a view's functionality in the Trigger.
0 votes -
Default table fields
How about having a global option to set default field names and types so everytime I create a new table, all these fields are automatically created.
For example, I always use ID(autonumber), Createdon(Timestamp), Createdby(Text), etc.. in all my tables but I need to create them all or have an empty copy of the table and duplicate it, it would be nice to have a default table fields location to define "common" fields.
3 votes -
Export photos
I want to scheduled a daily task to export all new files which were uploaded that day. Currently I receive a daily file of the data in my tables, but not files. For my business, I really need an incremental file with files (in my case photos) for Caspio to be more efficient.
2 votes -
Attach Object
There is a way to detach an object from a specific App but there isn't a way to attach it to a specific App. You can Share the object but sometimes you simply want to move something to a specific App as part of house keeping.
3 votes -
Add the ability to perform "star" ratings for reviewing a table entry.
Today the user has the ability to rate a table entry using numbers, but how about what is common today for rating (like hotels, travel suggestions, etc.) is a 5 star rating.
1 vote -
All Assets - Additional Columns and Filter
When looking at the All Assets view it would be helpful to have a column for DataPage. This way you could quickly see what is being used and if you have any orphan objects.
Also there should be a way to filter objects by name and DataPage. This is helpful if you have large numbers of objects (either Shared or App specific).
1 vote -
Pivot Tables Details and Sorting
The new Pivot Table feature to view details is helpful, but when the details have thousands of records, it beats the purpose of a Pivot Table.
Pivot Table Details should be able to be summarized just like it's parent pivot table so when we want to see details, we can see a few hundred rows rather than be stuck with the whole data table results.
also a sorting feature that can sort values A-Z even when there is a grouping on the table would be great. Pivot tables can be sorted by values ONLY if there aren't any groupings. This…
6 votes -
Editable e-mail fields for scheduled task exports
If I set up a scheduled task to e-mail a table or view, I have no way to edit the From, Subject, or Body fields. So I can't distinguish between different reports when they arrive in my inbox, and I can't provide instructions to the recipients about what to do with the attached files.
2 votes -
Revision history
It would be great if it was possible to have a revision history for a given datafield together with a date and user stamp
3 votes -
Pre-populating the labels from an Excel import
When I import a table from Excel, the first row is generally the field names. I should be able to tell Caspio that the cells in the second row are the field labels.
3 votes -
Ability to mark fields required when creating data tables (Same as NULL and NOT NULL at MS SQLServer Level)
The front end has the ability to mark fields required from data page. Need the same at the table level. If the field is a required field at the table level should automatically be required in the data page.
3 votes -
Lock fields instead of entire tables when custom programming uses a table.
Currently, if professional service does any custom work (i.e. triggered action, etc) the entire table is locked and the user cannot do any further development using that table (i.e. cannot add fields, etc.). This causes users to have to submit tickets just to have a new field added. That can take from hours to days to get done through that process. This directly contradicts the use-case for Caspio which should allow users to develop their own apps.
Previously users may have changed a field used in custom programming which would break the programming. A support ticket would then go in…
3 votes
- Don't see your idea?