Anonymous
My feedback
2 results found
-
19 votes
An error occurred while saving the comment -
164 votes
An error occurred while saving the comment Anonymous
commented
I've needed this, and have had to work around this limitation, many times since we signed up as a customer. It's been planned since August of 2014? Wow, implementation turnaround times must be really slow with Caspio. Either scrap it, or do it....
I've built one in caspio...it's pretty clunky though. I would like to see a better example of one in caspio. Caspio's model, unlike Quickbase, is to give you just a few basic templates that do nothing more than show you limited functionality.... a good inventory system in Caspio would require quite a bit of SQL programming and javascript. Unlike building an inventory system in MS Access (backed up to a SQL server), you don't have server-side programming capabilities with Caspio (unless you pay for them to do it), so you the best you can do is use SQL statements to summarize data in a datapage and javascript to control form functions, etc...
So much of what you would need an inventory system to do, requires a lot of work arounds until Caspio creates more dynamic field options and cross tabulation capabilities.
My workaround was getting rid of many of my relational tables and creating one flat file table for most of the inventory transactions (which is very ugly looking with a lot of null fields)...I still use separate tables for locations, skus, vendors, etc.... but all my transactions from receiving to movements to fulfillment are all recorded in the same table.
I hope that I can eventually parse the information back into relational tables, but it was such a struggle to work with them that way with the way Caspio is designed, that I'll have to wait until Caspio creates more dynamic cross tabulation capabilities, on the client-side (and more robust client-site capabilities in general), before I go that route.