Jump to content

DesiLogi

Caspio Guru
  • Content Count

    174
  • Joined

  • Last visited

  • Days Won

    12

DesiLogi last won the day on November 15 2018

DesiLogi had the most liked content!

1 Follower

About DesiLogi

  • Rank
    Advanced Member

Recent Profile Visitors

1,555 profile views
  1. Thanks DefinitelyNot3133- that's really helpful. I look forward to working this into the app.
  2. thanks- this will help when the auto-submit is worked out. Once I get that done I'll post the solution here as well.
  3. Thanks for the tip re triggers. The issue for me is the table involved has been locked by Caspio because they created backend triggers a few years ago. So I'm not able to use triggers built in the new feature, hence having to use datapages to do things like this. I've ended up changing the field to text and using "Yes" or "No" as text to do the update, that way it's not a null value that's put in but "No" written out.
  4. Does anyone know how to configure Bulk Edit to update a hidden check box to No or False? You can update a hidden checkbox to Yes but if you set the Default value to 'blank' it won't update the value to No/False- it just leaves it as is. I need to do this with a hidden checkbox so the user doesn't have to 'select' the checkbox field box in order to update to No/False. Any help would be great- thanks!
  5. Hi, Does anyone know how to put code in the footer of a Bulk Edit form so it auto-submits (so the user doesn't have to click the Update button)? This code: <script type="text/javascript"> if(document.getElementById("caspioform")) { document.getElementById("caspioform").style.display = 'none'; setTimeout('document.forms["caspioform"].submit()',1000); } </script> works only on a regular Update or Submission form. If you use it in Bulk Edit it just keeps refreshing the records over and over. So there must be some specific code for Bulk Edit. As well, if I can get Bulk Edit to auto-submit I'd like to remove he Update button so if anyone has code for that it'd be really great. Thanks!
  6. I figured out a workaround, if anyone needs a similar solution: A filtered View is used instead for the data source. This enables the auto-submit to run and when there are no more records to update (because the View filters out updated records) I use the Localization to redirect to a new url when there are no records (351 message). So basically, all the records in the recordset get cycled through on the Details datapage (set to go to 'Next Record' after update) and then when there are no further records (because the View datasource is empty) it redirects to a new url. A bit of a labyrinthine process but it gets the job done.
  7. I figured out a workaround, if anyone needs a similar solution. A filtered View is used for the data source. This enables the auto-submit to run and when there are no more records to update (because the View filters out updated records) I use the Localization to redirect to a new url when there are no records (351 message). So basically, all the records in the recordset get cycled through on the Details datapage (set to go to 'Next Record' after update) and then when there are no further records (because the View datasource is empty) it redirects to a new url. A bit of a labyrinthine process but it gets the job done.
  8. I figured out a workaround. Instead of a Virtual field calculating the remaining records in the filtered recordset, and then used in If/Else for auto-submitting when all records have been updated, a filtered View is used instead for the data source. This enables the auto-submit to run and when there are no more records to update (because the View filters out updated records) I use the Localization to redirect to a new url when there are no records (351 message). So basically, all the records in the recordset get cycled through on the Details datapage (set to go to 'Next Record' after update) and then when there are no further records (because the View datasource is empty) it redirects to a new url. A bit of a labyrinthine process but it gets the job done.
  9. I figured out a workaround. Instead of a Virtual field calculating the remaining records in the filtered recordset, and then used in If/Else for stopping auto-submitting when all records have been updated, a filtered View is used instead for the data source. This enables the auto-submit to run and when there are no more records to update (because the View filters out updated records) I use the Localization to redirect to a new url when there are no records (351 message). So basically, all the records in the recordset get cycled through on the Details datapage (set to go to 'Next Record' after update) and then when there are no further records (because the View datasource is empty) it redirects to a new url. A bit of a labyrinthine process but it gets the job done.
  10. Hi TsiBiRu, The datapage is a Details datapage (not a tabular datapage with this done in the Details view). The 'after Update' of the datapage (last step in the Wizard) is set to go to Next Record. This is so it cycles through related (filtered) records and updates each one. Normally, one would use triggers to do what I need to do but Caspio put custom triggers on a number of my tables, the one this deals with included, and they're locked- so I cannot create triggers on them. Therefore I have to use datapages to manipulate the data. Virtual2 is a calculated field that gets the total recordset (all the filtered, related records needed to be updated) and then subtracts the number of records that have actually been updated by this datapage, as they're updated. So Virtual2 counts down to 1 as the Auto Submit updates through the recordset. This works well and gives me the ability to 'know' when all the records in the filtered recordset have actually been updated, and therefore to stop the Auto Submit code from continuing to run. That's what the code above is supposed to do- look at Virtual 2's value, and when it reaches 1 stop going to AutoSubmit. NOTE: I don't think I need any 'next record' in the js code itself because the Details datapage is set to go to Next Record on Update. The Auto Submit code does cycle through all records (via Next Record) and updates them correctly. I just need to stop Auto Submit when Virtual 2 = 1. Hope this clarifies the issue and thanks for the hep-
  11. I accidentally posted this in the wrong forum (datapages) so I wanted to repost it here: I have some code I'm trying to get to work in the Footer on a Details form to halt AutoSubmit code when a value of 1 is reached in a Virtual field (calculated). The Details datapage is set to go to 'Next Record' on update so the Auto Submit cycles through the records. The problem is that when it gets to the last record it keeps auto submitting and I need it to stop AFTER submitting the last record. I found some code on this forum but can't get it to work- that code was older, before virtual fields could be calculated. If anyone knows how to adjust this code to get it to work that'd be really great. <script type="text/javascript"> if(document.getElementById("caspioform")) { if(document.getElementsByName("cbParamVirtual2")[0].value==1) { document.getElementById("caspioform").style.visibility = 'hidden'; document.write('<font face="arial" color=red size="5">No more Submissions!'); } else { setTimeout('document.forms["caspioform"].submit()',1000); } } </script>
  12. Hi, I have some code I'm trying to get to work in the Footer on a Details form to halt AutoSubmit code when a value of 1 is reached in a Virtual field (calculated). The Details datapage is set to go to 'Next Record' on update so the Auto Submit cycles through the records. The problem is that when it gets to the last record it keeps auto submitting and I need it to stop AFTER submitting the last record. I found some code on this forum but can't get it to work- that code was older, before virtual fields could be calculated. If anyone knows how to adjust this code to get it to work that'd be really great. <script type="text/javascript"> if(document.getElementById("caspioform")) { if(document.getElementsByName("cbParamVirtual2")[0].value==1) { document.getElementById("caspioform").style.visibility = 'hidden'; document.write('<font face="arial" color=red size="5">No more Submissions!'); } else { setTimeout('document.forms["caspioform"].submit()',1000); } } </script>
  13. I have a Details page that I'm using Auto Submit code to cycle through and update related records. However, when it gets to the last record (for example, 4 of 4) it keeps in the 'submit' cycle. I need the form to stop submitting once it's submitted the last record. Then, ideally, I need the form to go to another web page. But getting it to stop submitting after the last record update would be a good first step. Does anyone know how to adjust the Auto Submit code I'm using below? <script type="text/javascript"> if(document.getElementById("caspioform")) { document.getElementById("caspioform").style.display = 'none'; setTimeout('document.forms["caspioform"].submit()',1000); } </script>
  14. Hello, I have a Details datapage set up so when Update is clicked it goes to the next record. I need to figure out how to create a custom button (to put in either the Footer or an HTML block) to go to the Next Record (and a button for Previous, as well) so that the user can cycle through without clicking Update. The standard record navigation arrows at the bottom will not work for UI reasons (I need to make the custom 'Next Record' button relabeled and hidden in various scenarios). Does anyone know how to create a custom button for Next Record? As well, I also need to know how to hide that button (if it's in its own Section in an HTML block) when the Details form is at the 'last record' of the series (because there will be no 'Next Record' at that point). Any help would be greatly appreciated-
  15. Hello All, I have a Details datapage that I'm using to update a series of related records, one at a time. I've got code to run the update automatically (so the user doesn't have to click a button). The final setting is "Navigate to next/previous records" so it cycles through all the related records (filtered by a common ID number for each record). What I need it to do is, after the LAST records is updated, go to a new web page entirely. I don't know how to do BOTH "Navigate to next/previous records" AND THEN go to a new page after last record is updated. Does anyone know how to do this? Many thanks in advance!
×
×
  • Create New...