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".

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.

when a table has an email of a person in charge and due date for processing, I would request to equip the automatic email for a reminder for example 1 day before due date.

Thanks

Currently, I can only import new rows from a single csv file in a folder. It would be great if you could enable the task scheduler to import the newest file(s) in a folder and create a database record from each new file. I have a laboratory instrument that produces a new data file for each testing run. I need the results imported into a table in Caspio.

I've been trying to implement a trigger to estimate the min/max/average for all the records in my database. If I have four fields I want to estimate min/max/avg values for with a table of 1,000 records I get an error (e.g. 3 aggregations x 4 fields x 1,000 records = 12,000 which is above 10,000. This is very restrictive for doing aggregation calculations. I've also not noticed any performance issues. This limit can be lifted without any compromises for those who need it.

Create or offer API integration or plug-in which allows native mobile applications to store information into cache and upload into Caspio when mobile device is online.

triggered actions seems to be great idea.
but worthless if it is fired only on single update /for example through details page/

I think it would be great to have the ability to integrate the details entered into caspio table and automatically have those details integrated into outlook exchange nominated group email contacts.

Add RESTful API functions to generate PDF document.

The new triggered actions is great, but due to the new GDPR regulations, I would like the possibility to run an action as a sheduled action, and make it run once a day.
Maybe add a new time option to the triggered actions. (Insert, Update, Delete and TIME).

It is nice to have an option to add a condition for drop down. When displaying a drop down, the content is filtered by meeting a condition, either a text or the content in another field. Same for cascading drop down

Wordpress
The integration of datapages in wordpress is not a simple thing : the look and feel is really messed up ... border setting, lightbox, responsive gallerys are not displayed like setup in caspio ... Please make this integration smoother !

The aggregate feature in triggers is a really important feature. It would be great if you could use conditions within the aggregate calculation. For example, "count all the values that are below 10" etc. At the moment there is no way to add conditional statements into the aggregate calculation.

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.

When users are viewing the result page, give them the ability to hide/show certain columns dynamically.

Allow variables in To field of Email triggers. Just like in the subject and body so email/email list to can be pulled from a table and not be static. You can use variables in the To field of an email for the datapage and it should also be in the email trigger action.

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.

This will require transposing the table feature so that tables can be created where fields are rows. At the moment tables are created with fields as columns.