I use lots of "dictionary" tables for lookups on drop downs these occur in multiple column in reports so need to be included as a different alias for each said column. Starts to add up pretty quick and I've already met the 16 table limit.

Ability to create a datapage for App users to import data into tables without using a scheduled task or having to log into caspio. App users can add data manually; why not have the ability for admin level users to import directly into the tables?

For having printout and system documentation , a table structure is mandatory. I wonder what such a simple option is not in the system,
The user should be able to print the table design/structure simply, and directly from Caspio , not by exporting to Excel first.

and also allow "full SQL" definition of views - set unions, set differences etc.; plus creation of combination / concatenation fields in views; would be great in itself but also provide solutions to some of the front end limitations like drop downs can't be sorted on some other field etc.

For example. I would like to be able to create a view by comparing two separate fields.

1. Field1 Equal to Field2...
   
2. Field1, Greater Than or Equal to Field2..
3. [Sale_Price] - [Cost] < "500"
4. [LastImportDate] = Max of [LastImportDate]
   

Examples, COST vs SALE PRICE. Create a filter that allows me to show

I move data around a lot between Excel spreadsheets with copy/paste. I'd like to put some of these spreadsheets online with Caspio, but the inability to copy/paste from Excel to a Caspio table is a serious obstacle.

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 .

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.

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.

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.

self-eplanatory, I think

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!

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.

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

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.

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.

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.