Caspio Bridge
Welcome to Caspio Bridge Ideabox. We love to hear your improvement ideas.
161 results found
-
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 -
Allow formula fields to be linked with other tables
Any formula field should be allowed to be used to join with other tables, of course, as long as all possible outputs of the function are of the same type (numeric value or text)
17 votes -
Provide a way to compact Tables to minimum size
Large Tables frequently take up more space than they should because some datapages, views, and relationships may have been deleted. Please provide a compaction feature
2 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 -
Table relationships layouts that are saved should be specific to the current App chosen and not sun across all apps
Then you select "Relationships" and display the visual relationship map of the tables, that layout should be specific to the current App being worked on and not run across all apps.
6 votes -
36 votes
-
Ability to add SQL to the table formula field for cross table calculations (like you can in a DataPage formula)
Triggered actions are a great feature on their own and work well for new projects. However, they do not replace an SQL statement and only work for new records/actions.
Someone else already commented this on a previous request (http://ideabox.caspio.com/forums/164206-caspio-bridge/suggestions/16414099-can-we-add-sql-to-the-table-formula-field-for-cros) that was marked "complete".
18 votes -
triggered actions "on update" fired on bulk edit/update.
triggered actions seems to be great idea.
but worthless if it is fired only on single update /for example through details page/9 votes -
Add an new Triggered Action selector
It would be nice to have the ability to run a Triggered Action on only a single field being Updated. In this case I have a table which has a field which can contain the ID number for another user. This field might start out blank and can later be edited. None of the current selectors (less than, blank, exists, etc..) can accommodate a random value that you don't have any idea in advance what it might be. Might it be possible to have "Changed, or Unchanged" meaning compare the new value to the old value or lack of and…
2 votes -
Copy/Move Triggered Actions
the ability to copy or move the Triggered Actions from testing table to live table, since Caspio team advise to run the Triggered Actions on a testing table first and sometimes the Triggered Actions is complicated and there is a possibility to rebuild the Triggered Actions with missing pieces or rule.
27 votes -
Add file type to email triggers
It would be beneficial to also have the "file" type field be sent as an attachment in the email triggers. This way, a user can essentially submit emails with an attachment.
9 votes -
include a text field which can support 64000k plus text
currently having a trigger for concatinating two fields but gives error of incompatible ntext.
my trigger is like this
SET a(64000) = concatenate a(64000) ';' b(255)
4 votes -
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 -
search column feature in table when in Datasheet mode
Sometimes, I have large tables with more than 50 fields and I need to scroll to the right until I get the desired column, I would like to have a search column field which should take me to the column directly or maybe a filter to display certain columns when needed.
It will be also useful in Views.
3 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 -
Add filter Criteria for Previous Day | Previous Week | Previous Month | Previous Year
It's not possible to create a view for a date range that has already past.
Current Year|Month|Week|Day are all nice, but not effective when looking back at data.
4 votes -
Make it easier to reorder View fields
For Views with many fields from many tables, it is very helpful to arrange the fields in a logical order, especially when adding a new column which by default goes to the end. At the moment, one has to use up and down arrows for this, which is very clunky and time-consuming for large Views. Please could you consider replacing the current fields control with one that allows the selected item to be dragged to a new position in the list.
8 votes -
Copying the record from parent table to the child table and triggered action run in child table.
Sometimes we need to split the tables in some sections by creating a new child tables. But when we insert records from parent tables to child tables it is not possible to trigger an action because of currently triggered actions are limited to a maximum of one nested level. This limitation causes the app builders to create complex applıcations. Caspio needs to raise of number nested level otherwıse it is pointless to subscribe to this system.
16 votes -
Allow editing across multiple Tables in View
Currently only one Table per View can be edited. This forces designers to create more DataPages then necessary to work around this shortfall. By allowing multiple Tables to be edited, designers could reduce the overall DataPage count.
39 votes
- Don't see your idea?