Vitalikssssss

@peewee hi, I guess this should help:

Just an update on this topic. There is a feature called "Show distinct records only" released by Caspio in R30 that can easily solve this use case scenario. This feature available in List/Gallery/Tabular reports. https://howto.caspio.com/release-notes/caspio-30-0/

Just an update on possible solution for this scenario. There is a feature called "Show distinct records only" available since R30 Caspio version. This feature available in List/Gallery/Tabular Reports. https://howto.caspio.com/release-notes/caspio-30-0/

Hi @Ed727, You can try using a feature from R30 content called "Show distinct records only" which is available in List/Gallery/Tabular Reports. https://howto.caspio.com/release-notes/caspio-30-0/

Hi everyone, There is a feature called "Show distinct records only" present since R30 Caspio version. It is available in List/Gallery/Tabular Reports. https://howto.caspio.com/release-notes/caspio-30-0/

@Ed727, Since R30 Caspio version, there is an option available for Reports (List/Gallery/Tabular) that allows to show only "distinct" records. I guess, this feature can easily resolve the case of topic starter. https://howto.caspio.com/release-notes/caspio-30-0/

Hello @dasigrist, If it is still something that you have not been able to resolve then I have a good news. Caspio has release DISTINCT filtering option for Tabular/List/Gallery reports in R30 version. https://howto.caspio.com/release-notes/caspio-30-0/

@GlennFL, @bbeshlian good news! Caspio has introduced DISTINCT criteria filtering in R30 version for Tabular/List/Gallery reports. https://howto.caspio.com/release-notes/caspio-30-0/

Hi All, Caspio has finally released a feature to show DISTINCT records on Reports (Tabular/List/Gallery). It is available in R30 version. https://howto.caspio.com/release-notes/caspio-30-0/

Hi @JMR21, This screenshot confuse me a bit because highlighted fields set to "Display only", however, in your screenshot they set as TextFields (inputs). I am not able to replicate the issue with the information provided. Perhaps, you can export the Datapage with dependencies (without data) and attach it to your response, so I could have a closer look. Regards, vitalikssssss

Hi @Jephta, I would recommend using standard Caspio features rather than custom code. You may consider approach of assigning default values described in this HowTo article: https://howto.caspio.com/datapages/datapage-components/setting-up-default-values/ Hope this helps. Regards, vitalikssssss

Actually, you can base your Triggered Action on the table that is used as data source for the Details Datapage on which you would like to incorporate the JavaScript snippet to click on the "Update" button. You can create a Triggered action that runs "on update" and inserts the data from one table to another. You would need to use "Single Record Update" Datapage to redirect the user after "Update" button clicked, since the record will be created by the Triggered Action and user just need to confirm/edit the values that was inserted by Triggered Action. Regards, Vitalikssssss

Not sure what did you mean by this... Anyway, you may use JS timeout() function to click on "Update" button instead of the user. <script> setTimeout(()=> { document.querySelector("input[id^='Mod0EditRecord']").click(); }, 2000) </script>

Hi @David17, You can use the following JavaScript snippet that does not allow input of negative numbers of letters into the field. Place below code into the Footer of Submission Form Datapage: <script> document.addEventListener('DataPageReady', checkNegative); function checkNegative(){ let input = document.getElementById('InsertRecordYOUR_FIELD_NAME'); //change this according to the name of your field input.type = "number"; input.onkeydown = function(e) { if(!((e.keyCode > 95 && e.keyCode < 106) || (e.keyCode > 47 && e.keyCode < 58) || e.keyCode == 8)) { return false; } } } </script> Make sure that you disable HTML editor prior inserting the code. Hope this helps. Regards, vitalikssssss

Hi @kcastagnaro, Well, Caspio has release some Triggered Action enhancement called "Loops" that could simplify the solution. As of now you would need to have two tables (i.e. three before). First table would hold event name and start and end date. The second table would hold each day of the event as a separate record. So the Triggered Action would look like the following: The package with tables and Triggered action here. Hope this helps. Regards, vitalikssssss