Jump to content


Caspio Guru
  • Posts

  • Joined

  • Last visited

  • Days Won


NiceDuck last won the day on March 26

NiceDuck had the most liked content!


Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

NiceDuck's Achievements

  1. Okay, It turns out that if the update on password originates from a DataPage (ex, Single Record Update form), the trigger activates. However, if you update the password directly to the Caspio Table, it bypass the trigger.
  2. Is it possible to make a trigger run when a password field is updated?
  3. As I check, we can atleast use the list string field on Rules. But aside from that, Id rather rely on a CSV on a text field.
  4. I'm not sure if that is intended but you are using both #inserted.Store_No with your join conditions. This trigger will update all of your record on the 'Table_2' with whatever the values you have on your #inserted. Unless its intentional, it is going to create a mess. Make sure to backup your tables.
  5. If I got your inquiry correct, you want to pass a parameter inside a datapage that you have deployed on your details page as am Iframe. If the parameter you wanted to pass is existing on the details page as a field or even as an external paramter, you can try simply adding it on the URL of the datapage you have deployed on the details page via Query string. kind of like on this: <iframe name="checkboxes or logic" title="checkboxes or logic" src="<dp URL>?RID=[@rid]">Sorry, but your browser does not support frames.</iframe> replace [@rid] with [@field:rid] if the RID is a field value and not an external parameter.
  6. As a follow up to @GoodBoy, Just remember that Virtual fields are only available on FORM type of Datapages such as the submission form, single record update or the report details page. They are also available on search forms but I'm not that familiar for what their use there.
  7. You can also use the same concept if your goal is to collect a sum of records from table a and save it on table b during inserts/updates on table a
  8. I just figured it out, turns out I have to add quotation to the 55555 https://c6ffn328.caspio.com/rest/v2/tables/demo_table1/records?q.select=Las_Name%2CGender%2Ctest_val&q.where=Test_pin%3D'55555' Weird, it was working as expected before even without the quotation.
  9. Hello I am having this error on my swagger. This is my query https://c6------.caspio.com/rest/v2/tables/demo_table1/records?q.select=Las_Name%2CGender%2Ctest_val&q.where=Test_pin%3D55555 All of the fields mentioned there is text255. Where did it get the Int?
  10. If you are interested on checking the status of the your site, you may go to http://status.caspio.com/ instead. And to know which site your account belongs, you can actually find it on help>about Caspio Bridge
  11. I have tried pinging my account ex. But it is just being timed out. As per the Caspio Support, it is because the as ping command is locked inside AWS. Therefore, we cannot use it to check the latency.
  12. You can also try calling the calcfield from the header then hide entire calculated field column using this forum post: if you called the calculated field from the header, it should only show the first one there. However, the problem is... its on the header...
  13. depending on what datapage you are using, you can also seperate the calculated field to the actual link. for example, on your html block, you have this <a href='https://nameofyoursite.html?testparam=[@calcfield1]'>Link2</a> then on your calculated filed, create a basic conditional statement case when [@field:FieldName] = '1' then 1 end On this case, the parameter will only has a value if the conditions are correct.
  14. Note: The workaround I have provided above will only works if you have less than 10k records to import since task can only process up to 10k records. If you have more than that, that'll be another issue to check in
  15. As mentioned on the previous responses, Import bypasses the triggered action, thus they wont react to your imported records. If you really need to make the imported records go through to your triggered action, what I can suggest is to import them to an extra table. Then use a an application task to insert or update the main table base on what is the content of that task. Triggered action should now work from that.
  • Create New...