Search the Community

Hi all, i'm trying to convert a very basic spreadsheet into Caspio but I'm really disappointed to learn that there is no alternative to INDEX/MATCH. Caspio seems incapable of working with arrays, there is no INDEX function nor MATCH function, calculated fields allow SQL but SQL queries do not allow for select * so I'm faced with a technical constraint it seems. What I'm trying to overcome (what Excel does effortlessly on the fly) is do some calculations to come to a measure, then this measure is compared to each user's custom model settings (using values in the user table) to tell the user which model to use. With an INDEX MATCH in Excel I'm able to do this 2 dimensionally with one formula. After struggling with Caspio, I found as only way to do this is with virtual fields as calculated value using CASE OK a lot of lines of code to write but hey, the result would be there ... or wouldn't it ? The result get's into place but ... it takes about 15 seconds to calculate. Does anyone have any other way to achieve this or am I bound to start looking for another platform ? Kind regards

Hello! Is there any performance benefit to filtering results in the View vs. Data Page? Thanks

Hello; Do views and tables have different performance characteristics? Or, is their only purpose to provide multi-table data sets? Consider these two scenarios: tbl_1 -> fld_1 | fld_2 | fld_3 | fld_4 | fld_5 | fld_6 frm_1 -> tbl_1.fld_3 | tbl_1.fld_5 Will the following View save me data usage or speed up the call? (or do anything else) view_1 -> tbl_1.fld_3 | tbl_1.fld_5 ---------------------------------------------------------------------------- frm_2 - tbl_1.fld_1 | tbl_1.fld_2 | tbl_1.fld_3 | tbl_1.fld_4 | tbl_1.fld_5 | tbl_1.fld_6 Will the following View slow down the call? (or do anything else) view_2 - tbl_1.fld_1 | tbl_1.fld_2 | tbl_1.fld_3 | tbl_1.fld_4 | tbl_1.fld_5 | tbl_1.fld_6 THANKS

I have a View based on about 6 related tables. One of these tables has about 60,000 records that span the last 20 years, which is by far the largest table. I really only need the last 5 years of data from this table for Caspio purposes, so I'm wondering if it might be worth it to archive any data in that table that's older as a means of improving performance. That said-- unless there's a huge performance boost, my preference would be to create a View that filters out all years from prior what I need.

Hi, I'd like to share a performance tweak I discovered this morning. Filter your data at the Data Page, not the View. In a View, I filtered out values based on the criteria of time-stamped values from the last 30-days. The Data Page that used this view took ~9 seconds to load. I switched to Filtering a DataPage, and now it loads in <1 second. Think Easy CHAD