Jump to content

NiceDuck

Caspio Guru
  • Content Count

    121
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by NiceDuck

  1. @Nuke354, yes that is for the task Now, the idea is try to use the same on the trigger. Take note though, on this kind of workflow, there is a very high chance that you encounter a cascading limit error since we can only cascade up to 2 triggers.
  2. Depending on How complicated the trigger is, if its a very simple workflow where the only challenge or issue is the exceeding records, perhaps we can actually use the task workaround and trigger it via cascading trigger. For example, on main table, you have a trigger that will copy delete all values from table c and insert all records from table b there. Table b however has 15k records. What we can do is kindof like this, first block is the delete block for table c 2nd block is for inserting all records from table b where autnumber is less than 9k 3rd block is where we insert a s
  3. Additional Note: The workflow I mentioned above will only work with calculated fields and It should also work with formula fields. However, it would not work with Calculated Values. Anyway, if you have calculated values on your DAtaPage, there should probably a 'rules' feature there. I suggest that you use that instead.
  4. There is actually a tricky workflow for this one. If you need to move your pictures to another table for 1 time use only, you may try the following: 1) Convert the field for handling the files into a text255. With that, the file it has will be converted into a directoty. 2) Use task to copy that directory to another table. The receiver should be a text 255 as well. 3) Convert those text255 fields into file data type again. If you will be needing to pass them time to time, I suggest that you try this one. 1) On your main table, take the ID of record which has the desired imag
  5. You can actually use @Nuke354 workflow on report datapages with calculated field to make it work conditionally. For example, on your results page , you only want to hide the value of those fields depending on a value from another field, you may try this kind of workflow, 1) at the very bottom of the page, create 2 html blocks. Set them up as described on Nuke's workflow. 2) Create a calculated field there and use a case when formula like this: Case when [@field:indicator] = 1 then 'none' else 'block' end 3) Encapsulate the actual fields you wanted to hide on html blocks. On the
  6. Base on my expirience, you need to add the prefix 'InsertRecord' on the parameter name on the receiving end for every parameter that is being passed by this method: However, If you want to avoid all of this confusion, just use the manual redirect on the end of the datapage via url and pass the parameter as querry string: with this, you can simply catch it like a normal parameter.
  7. Just an additional detail for this. Triggered action can modify a record but it cannot modify a table design. Thus the destination table has to be manually created. Same on the task as well.
  8. I cant see the whole trigger so I cant provide a sample but it would more optimal if you just use the where conditions of the Function blocks instead of the using the if then statement.
  9. After this, you may want to try making a triggered action for saving the fields history/ previous value to another table. If you are interested, please see this thread
  10. You may also want to try converting the time used on the trigger depending on the timezone of the user (if you have something that we can use as a reference for the current user's timezone). Then we may use this workflow here to adjust the time to their timezone:
  11. If I got your inquiry correct, what you wanted to do is to capture the actual timezone (or time) of the user instead of relying on the trigger. The trigger wont be able to know that since it is on the backend. If you are using a datapage (preferably a form type such as submission form or Details page) to insert or update the data, perhaps you can add a date/time field and use that on your form as a calculated value. Once it is now a calculated value, the sql SysDateTime() should now work and be included on the records where you can no use them on the trigger.
  12. Normally, I would rather use the not exist operator to check if the record does not exist yet. Just like this. I try using "Not in" before but I encounter some errors so I prefer using this more
  13. I Also want to suggest ths workflow, I made this one before but I kindof forgot the details. I hope this helps Email Authentication.docx
  14. My idea is, create a submission form that will automatically submit this data to a separate table. 1) create a table with the following field: ID (any id field, just for normalization), DP name (text 255) Visitor (text 255) 2)Then create a submission form that will use the table above as its data source, include all the the fields and set them up to load default values from parameter. 3) Use an auto submit JS to make this form... auto submit. 4) Now, Embed this as an iframe to all of your DataPage (preferably on footer). On the URL of your embed code, make sure that you inc
  15. Your intended workflow appears to be doable. If I got it correctly, our overall intentions here is to apply the changes made on table A to table B. On this case, you will need an update trigger on table a that will then also update the table b. This is the basic: This will only work ofcourse if your tables have optimal relation between each other but I can say much since I do not know the exact design of your tables. I hope it helps
  16. I noticed that one as well. For now, what I did is I made a dummy datapage to host that image for me, then from there, right click on the image then select the 'get image address'. You will then have a URL which you may now use for the image on authentication instead of pulling it from app parameter itself. image on authentication.docx
  17. I think we dont need the whoe "if Then block" if you place the conditional statement on the join field itself: The join also acts as a condition statement and using an if then block on your case appears to be a kind of redundant filtering. I hope this helps
  18. You may also want to check your view filtering. please see this article as well: https://howto.caspio.com/tables-and-views/what-are-views/creating-a-view-to-filter-data/
  19. What I could suggest does not have a dropdown, but 5 yes no fields (one for each option), then we can make a triggered action to make seperate entries per selected options on a different table. Basically, first table will just be a dummy table for intaking records but the actual records will be created and saved on different table via triggered action.
  20. Uhmmm I have a suggestions, since you are using the same criteria on the join and the where, you can remove those at the 'Where' clause. I think the filtering is getting redundant since the Join kindof acts as a filter as well.
  21. HMMMM I suggest that we use a seperate table then use a task/triggered action to copy values there that has second records... Then use that table as the datasource of this chart instead. We can also add a single field on your table and use task/trigger to mark records that has a second. Then on your filtering for the DataPage, filter it to only include those that are marked
  22. If you no longer need the list string field and you just wanted to salvage its content or you just need to do this for 1 time only, I suggest that you convert it to text255. The list string contents of it will become a comma separated values instead. Once you are done transferring, you can change it back to list string again.
  23. @peewee It is indeed a current Caspio Limitation, what I could suggest at the moment is instead of using list data types, just create multiple yes-no fields. It may be difficult to set up properly on forms but it would help us properly for the automation using triggered action and task
  24. If I got your inquiry correct, you want to limit the values the user can search depending on your parameter. Is that the case? If yes, I could suggest using a cascading elements. What we will need to do is set a virtual field and set it to hidden and make it load default value from parameter. Then, set your proper search fields as cascading elements using the virtual field as its parent. This workflow will require a custom lookup table where you will need to set which record is related to your parameters and which value shall appear only on your search field. I hope you got the
  25. @BertM If the creation of child records will originate from creating parent record as well, you can use this trigger on the parent table. If you dont have an update trigger on the parent table, this should work properly with @AtayBalunbalunan's trigger. Otherwise, you would have an cascading error. @AtayBalunbalunan, thank you for the tip about getting the count, I did not know that you can get the count of records with just the 'expression field', I thought that a group function is required for that.
×
×
  • Create New...