Jump to content

NiceDuck

Caspio Guru
  • Content Count

    188
  • Joined

  • Last visited

  • Days Won

    11

Everything posted by NiceDuck

  1. The last one is this, it uses list string fields. First, ofcourse, create a list string field on the data table. Import list values from the user table and make sure to use the ID field. Then just do the same setup mentioned on the previous response: just this time, use the list string field instead. Cons of this setup: everytime you have a new user, you will have to manually add their ID on the list string field used on the data table. Also, you cant use list string on triggers and such
  2. Another workaround is instead of using RLS, create a hidden search field on the search form. On the data table, what we will need there is a field that contains a comma separated values of the User IDs that are allowed to see the data. Cons of this workflow, its a big hassle on configuring who can access the records. I mean, it is easy to just concatenate additional user_Ids, but the hassle will start if you want to remove them or replace them. Since you will have to manually do that on the comma separated values .
  3. The quick answer is no, but there are few workarounds. The first one is by the use of Data Grouping. Instead of marking the records with the ID of individual users, create a group of for your users and mark the records to which group they belongs On this case, if we use demo_table1 on a report datapage with RLS, we will use the test_1 field from the authentication field and the test_val field from the demo_table 1 Cons of this workflow: If a user needs to access the a record that belongs to another group, then we are back on the same problem
  4. Is there a way to assign a record to multiple Users via Record Level Security?
  5. This may be a common sense by now but it will only work on authenticated DataPage. Even if you are currently logged in, if the datapage where you currently at is not authenticated, this will not work at all.
  6. Pie chart will only based on a single field. Since the whole of the chart will always be equal to 100%, it aggregate all of the values on that single field then divide the chart depends on what are the different values on that field. Now, if the values that you want to put on that pie chart is on different fields, We can still proceed with the workflow of using a different table. No need to make a seperate table per user, just mark the record to which user it belongs. What we will need here is a Task that will compile those values on a single field From this: to this:
  7. What I can suggest for this is using a view to inner join the table to itself. The idea is, you will need an extra field and use it to have the id of the record that has the file that you want for the current record. Then, using view, use that extra field to join the table to itself. Then only fetch an extra file field. You will then have 2 file fields on your view, the one is the original file field for the current record and the other one is the one from the record the extra field matches. You wont exactly copy it but will be accessible. I hope you get the idea.
  8. What I could suggest for this is to create a different table and use task or trigger to compile the values you need there then use it to create a chart since as far as I know, we cannot use complex operations on the chart. If you could provide us some of your objects and sample, (ex, a photo or current chart and the intended chart) perhaps we can provide more input to this.
  9. I would also suggest that instead of using a 'Yes/No' field, I would use a text 255 instead and write a word indicator there to identify where the update came from. The only advantages on this one, is just in case that you have multiple source for the update, you can simply create multiple indicators and and use different trigger blocks for each of them
  10. As a follow up to what stated above, the trick here is to create an indicator for the triggered action that is the update is coming from the specific datapage. On the case above, what they did there is a hidden yes/no field that if its marked as check, then it means that it comes from the desired single record update.
  11. Regarding about your timestamp and deviceID issue, if your device ID is an autonumber, then the order arrangement of them should be the same
  12. What I can suggest on this one is to make use of the 'Group' function then aggregate your date field to only get the maximum. We can later on set a condition that the record will only be included if their maximum date is 1 month or more. By the way, in regards about this month ago, do you mean like, 30 days before?
  13. If you need some live values from authentication table, try using select statements from calculated fields then call that calculated fields to your header. Not doable on HTML datapages though.
  14. Regarding about logging out. If you do not have a loggout link yet, you can force logout your application by using your logout link directly on the URL. Logout links/URL are found on the properties of the authentication and is the same for all of the authentications you have on your account.
  15. You may want to double check your redirections and if you are already login. If you have already logged in on the same browser (even on preview) few moment before you access you actual page. It will not show the login screen but automatically captures the last login since the last login are still saved on your browsers cache. I suggest that you either logout first or clear your cache.
  16. You may want to check on Orphan file Cleanup for objects that are no longer used in any table. https://howto.caspio.com/files-and-images/orphan-file-cleanup/#:~:text=The Orphan File Cleanup process,like manual or automatic cleanup.
  17. What I can suggest here is to try to refresh the trigger and double check if the table being used there really exist. I think if you have a PS project, they also lock the tables and other objects they made. You may also want to try using a different table and see if the issue persisted. Or contact Support...
  18. such kind of error will normally not occur if you only have an email block inside your trigger. As mentioned by @CoopperBackpack, do yuo happend to have a unique field on table? You may also want to check on other tables where that is being mentioned or referenced by your current trigger.
  19. You may not need it now but you can also create one for delete action. Please note that there can only be 1 triggered action enabled per action. So if you have two triggered action for insert action, enabling 1 of them will automatically disable the another.
  20. We can indeed do this via Triggered Action. If I got it correct, you want to get the average value from specific field, starting from the total value of all the records on the table as well as the value of the newly inserted. Then save the computed average to another field on the newly inserted. If that is the case, you can normally use a trigger like this:
  21. As I know, the formula comes first before the trigger since it automatically produce value once the record is created even though they are still on the #inserted. As for why your workflow does not work, may you please give me a screenshot of trigger as well as the formula you are using?
  22. You may want to check our discussion here as well:
×
×
  • Create New...