Jump to content


Caspio Ninja
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by NiceDuck

  1. If you only have small amount of records, it is easier to remove those unwanted addresses. However, as your record grows vast, it will start become troublesome locating and deleting those unwanted addresses. This workflow will surely be helpful.
  2. Yes, you just have to concatenate with a semicolon in between. Kinda like this one: This one is on task, but I am sure you can easily have it converted to trigger.
  3. NiceDuck


    I'm not adept when it comes to CSS and styling so I dont know if it can be done with the email. However, what I'll do is I'm gonna send them an email with a URL to a datapage downloadable as PDF. That datapage has the details and the barcode. I'm not sure if its readable by the barcode readers, I dont have one here But I highly hope so.
  4. NiceDuck


    As for the QR code, I don't know. Their PS team can probably do it.
  5. NiceDuck


    Hello Caspio can use fonts on google web fonts for their datapages. They have a barcode font there which you can use to convert values to a barcode. You may like to check the following URL's for more details https://howto.caspio.com/styles/using-google-web-fonts/ https://fonts.google.com/specimen/Libre+Barcode+39 hope it helps, quack
  6. probably some cookie or cache issue. Try clearing it up, using another browser or even other device. If issue persisted, contact the support.
  7. You may also want to try this one Quack
  8. Hello, are you really on a submission form? As I check, you can only have Calculated values on a submission form and they real time responsive. As for the calculated fields, I think they perform their calculation during on load and if you refer a field from it, it will gather those information directly from the table datasource thus it will not response/change value unless the changed values on the fields are saved on the tables first. You may want to try calculated values. You can set a field to became a calculated value on its form element. I hope it helps
  9. Just an update. As for the workflow I provided above, you are not collecting the values that are being used for searching since we are only using a dummy submission form filled with virtual fields. However, if would also be nice if we will collect those values so we can generate later what are the most search records on your reports. Anyway, if you happened to collect them, you can simply turn the field you are using on the step#5 to "Required" then use this formula instead. Case when [@field:payer] = 1 then *URL of your report datapage plust the other fields as a parameter* when [@virtual1] < 3 then *URL of your report datapage plus the other fields as a parameter* end. for this case, if all conditions is falls, the field will remain as blank. however, since it is a unique field. it will not accept blank values this is will prevent submission. You'll just have to change the error message on the localization. hope it helps, quack
  10. You may also want to refer on this another forum post.
  11. The timestamp is for making sure that the values will be submitted will never be similar to those previously submitted records. You may want to add some strings to it which is relevant to the Data you are submitting. You may refer to this one: CONVERT(VARCHAR(10), SysUTCDateTime()) + 'test' Quack
  12. Hello Shiro, For this case, what I suggest is create another field on your data source table (preferably text 255) and check the unique checkbox. Then on your submission form, set it to calculated value and make an SQL statement like this: Case When '[field:aaa]' = 'yes' then SysUTCDateTime() When '[field:bbb]' = 'yes' then SysUTCDateTime() When '[field:ccc]' = 'yes' then SysUTCDateTime() end BAsically, what it does is it checks all the mentioned fields. if none of them is equal to 'yes', the value of this field will be null. However, since blank values are unacceptable on unique fields, it will prevent the submission. You just have to change the error message on the localization Hope it helps Quack
  13. You may also mix that workflow with this one for overall cover:
  14. hmmmmm I guess you can use a calculated field/value then use conditional statement. put them on the same line with the dropdown by checking the "Place next element on the same line". As for the dropdown, set it to "No label" With that, the calculated field/value will be your label. Again, its just a suggestion. quack
  15. This is how I did it by a triggered action. Note, with this workflow, you would be able to keep the previous value of a field, it will not save the value of newly inserted record. first, duplicate the table which you want to have a history record. go to its table design and change its ID field to a text 255 and rename it "parent_id" or any name you want. Your call, as long as it indicates that it is the records former ID. also, make sure that this field is not set to unique. Add an Id field and name it "History_Id" this will be the records actual ID on its current table. this is not actually a necessity but just for... best practices I guess. Now, on your main table, create a triggered action that will copy the previous value of the updated fields to the history field. You may refer to this picture: There you have it. That is only the basics though. As mentioned above, you may also want to create a timestamp field to record when a value is updated or transferred on the history field. If you have authentication, it will also helpful if you will have a dedicated field for capturing the ID of the user who made the changes. Hope it helps, Quack
  16. Halo, I know that you mentioned "simple" on the post but you may want to check this post also if you want to create a log for knowing who deleted what : I hope this helps quack
  17. Hello @BretSparkman, I do have an idea for this, however, you will need the following. authentication dummy submission form report datapage set to search by predefined values from parameters. ****************************** we will need to the authentication to determine if the current user is paid user or paid user. make sure that the datapages that will be used on this work are authenticated. On your Users table, set a field for determining if a user is paid or not and set another field for counting the number of search. create a dummy submission form. A dummy submission form is a submission form with only virtual fields. with this, it will not save any data to the selected data source upon submission. Make all this virtual fields pass their value as a parameter on exit. The purpose of this dummy is this will be the search form of your user. Use virtual field as a calculated value and create condition statement that will check if the current user is a paid user or not and if not, check if its number of searches havent reach the limit yet. If good, it shall return the URL of the report datapage, If not, redirect it to somewhere else. Make sure that the report datapage are catching the right parameter for their searches. This is the whole Idea of this workflow. Feel free to ask if you need more details. quack
  18. Im not sure if I understand your workflow perfectly but as I understand, You do have a date field. this datefield is sometimes pre-populated and sometimes not. If this is pre- populated, the user shall not be able to edit those. However, if it is not pre-populated, then the user should be able to set a value. If this is the case, I think it can be done by using the rules feature and a virtual field. You are going to make the virtual field and the date field load the pre-defined value you wanted. Then, envelope the virtual field with HTML block containing html script for hiding: see instructions here: https://howto.caspio.com/tech-tips-and-articles/common-customizations/how-to-hide-fields-in-datapages/ Then, make a rule that if the virtual field is not blank, it will hide the date field. with this, the date field will only appear if it has no pre-defined value. I hope this helps.
  19. If you are not fond of multiple records display on your screen, I can also suggest that you create a dummy table and task triggers to calculate those values for you. Therefore, you will have a table which has the summary report of your transactions table.
  20. I quite...dont understand your problem. As I checked, you can actually make a virtual field catch an external parameter. However, virtual fields which are set to calculated value's cannot load values from parameter because they are meant to have their own value depending on the formula/calculation declared on them. If you need an external parameter on your calculated value, use a seperate virtual field to catch the parameter for you then call that virtual field on your calculated value
  21. @Shasha Further elaboration would really help...
  22. Hello, This is a possible worflow for that objective. first, both payers and non payers should be authenticated before search so we can track if the current user is a payer or not. I suggest that on the table which hold the user info, set a checkbox field there to differentiate them. second, we will have to separate the search form to the results page of your data-page, you may refer to this article on how to. : https://howto.caspio.com/tech-tips-and-articles/tech-parameters/how-to-separate-search-page-and-results-page-into-two-different-webpages/ However, we will not fully copy that step, we will modify it for a bit. I suggest that you do the the following instead. 1) duplicate your table which you use as a data source for this report datapage. name the duplicate whatever you like. 2) add some extra fields to your fields on the duplicate. a timestamp field upon insert and a field which is compatible to hold the id of the current user. (probably a text 255) 3) create a submission form using the duplicate table, Make sure to include the field for holding the Id. set this field to hidden with the id of the current user as a default value. 4) create a virtual field on the submission form to. set it to calculated value after that, we will use an SQL code to check how many records are submited by the current user by the current date. select count ([@field:IDfield]) from duplicate_table_ where DateDiff(day, SysUTCDateTime(), [@field:date]) =0; * note that [@field:IDfield] and [@field:date] shall be replace with the ID field and timestamp you just added on the duplicate table 5) create another virtual field and set it again to calculated value. this time, we are going to create a condition statement if the user shall be allowed to search or not. Case when [@field:payer] = 1 then *URL of your report datapage plust the other fields as a parameter* when targer.[@virtual1] < 3 then *URL of your report datapage plust the other fields as a parameter* Else www.somewhereelse.com end. 6) Set your submission form to redirect to another website upon submit. use the URL your virtual field 2 as the source for its URL 7) last, you just have to set your report datapage to be filterd by external parameters. The codes may not work but I hope you get the idea.
  23. We cannot have a triggered action into a view. It is only available on tables. I suggest that you just make a triggered action on the table which are involve on your views. You can only edit one table in a view anyway. If you need the other tables record on your triggered action, you may call upon them by using the *select from block or by using the join feature. If you will provide more information on what you are trying to achieve, perhaps we can suggest a work around. Hope it helps. quack
  • Create New...