Spencer Hargiss
My feedback
5 results found
-
4 votes
-
30 votes
-
14 votes
-
44 votes
An error occurred while saving the comment An error occurred while saving the comment I agree not being able to access list fields via tasks and actions means that if you use a lot of triggered actions you basically can't even use list fields for anything important.
-
7 votes
An error occurred while saving the comment The only existing method I've found is using many-to-many relationships, such as by using one table for products, one table for orders, and one table where each record connects a product with an order. This is what we did for our project, and the result was not hard to work with and user unfriendly. Unless a new feature is added, we are now ultimately planning on transitioning to other platforms which can handle this elegantly, such as bubble.
A good example of what's needed here is email programs, where each email is sent to a list of recipients. Once you start typing in a name or address to add to the list you get an autocomplete box, and once you click the autocomplete option that person is added as a recipient, and there is an X by their name so they can be removed from the list as well. This sort of multi-select autocomplete would be a very welcome new option when it comes to dealing with list strings. Any option which is not an option by default would be added automatically to the list string's list of valid options.
https://caspio.uservoice.com/forums/164206-caspio-bridge/suggestions/38032192-allow-list-strings-read-data-from-another-table
This is another feature which would be really useful. Bottom line, the lists on Caspio are too ersatz to lean on. They are really bitmasks rather than lists, they are hard to access via actions and they are only suitable in a small number of use cases.