I have commented on this previously and agree it would be an extremely useful feature for all, particularly when updating large or complex tables. It is a standard feature in other cloud database applications, but maybe they use different technology on the backend...? It would be nice if Caspio could address this idea even if it an explanation of why it can't or shouldn't be done.

I am still confused as to why this hasn't taken place yet. It would make some many things easier for me.. Serious, you can't update on import. You can't update with a scheduled task import. Your at the mercy of appending or replacing. So then I think, no problem, lets just import to a seperate table called UPDATE_TABLE. I would import all records that need updated here and then use a query_update function to update from here to the master list. Basically easy to do with a view and select just the files you want to update to the existing table. OH NO, can't us a Datapage or View to update overwright records in a table either. I am at a loss.

I also agree 100%. This is a standard feature available on phpMyadmin. When we have just a dozen of 100,000+ records to replace, we have to either manually update these in table format (and this is time-consuming and error prone as we have several fields in each record that may need updating) or re-upload the ENTIRE table.

I am surprised that this has not happen yet? There seems to be a function when importing that allows for "Update Design" however it doesn't really seem to work. For this to work and be most powerful it should be allowed when setting up a scheduled task. Admin, please let us know if this is on its way. Thanks, Matt

I agree 100%. Yes, the import should give an option for update. As Caspio Admin mentioned, the wizard should basically compare records based on a unique field and update all other fields included in the record. In my opinion, if there is a records that exists in the import that isn't in the existing table, you should be able to set an option to either ignore or add the record. This would allow for a lot more functionality in my opinion.

For some reason, I was thinking this had been implemented -- is that not true?

This is a great feature that I have used on many other cloud platforms. Basically, the data goes in like a regular import, but in addition to the options for Replace and Append, there would be an option to "Replace Matching". When that option is selected, the field to match is then selected and the file is imported to match against that unique field. The same options for mapping fields would be available so only select fields would be changed if desired. This is an extremely useful tool that allows quick updates for new data of selected records and fields.

I am also very interested to have this update. I just want to add that if the record/unique ID is not found a new record should be appended. This whole function is very important to us, so the sooner the better! Thanks!

To the Admin - that is EXACTLY what I was thinking. You would have to select a Unique ID field to match up and then you can select the field/s that you would like to make the updates w/o making changes to ALL the fields within the records.

This is an interesting idea and I can see the utility of it.

I suppose the import wizard should be aware of the unique ID field of the record, and the field(s) that should receive the updated data. Is this inline with your idea? If not, please elaborate.