Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Record Level Access - extending to other tables...

Featured Replies

OK, I have a calculation that allows/disallows access to records in Table A of File A.

 

Table B in File B has a relationship to Table A.

 

Based on the criteria being used in Table A of File A, how can I extend the Record Level Access protection to Table B in File B - because they can't see the values in Table A due to Record Level Access protection.

 

Is there a way to say 'If you can't see the related Record(s) in Table A, no access"??

The RLA should be dependent on the user's account and privilege set.

 

It's interesting to note that RLA only restricts access to view the data in the records, not the records themselves. That is, even if a user has no view access they can still "see" that the table has n records in it.

 

Try the IsValid function, maybe IsValid( TableA::primary key ) and see how the result varies if the record allows view access or not.

  • Author

Thanks Vaughan.

 

This is partly based on their Account - but also on specific data in Table A (If Field = Value, do not show)

 

What if there are no related records in File A?

So you're in Table B looking at records from B, and the RLA depends on related record in table A. Is that right?

 

If there is no record in table A? Then I guess that's a business decision. AFAIK there is no technical limitation in FMP from controlling the access to either allow or disallow view privileges.

 

The RLA calc in B might be something like this to allow view if no record in A exists:

 

IsEmpty( tableA::field ) or tableA::field = "someValue"

  • Author

Yep, that's the scenario.

 

More fully, I have a File that contains Courses that students take. For business reasons, some of these records are not allowed to be viewed by a specific privilege set, if one field in the record has a particular value.

 

No problems applying RLA to this File and Table.

 

Moreover, if that is the case, then the parent Student record in another File cannot be viewed by the same privilege set, based on whether *any* of the child Course records have that field set.

 

But I've now disallowed access to the child Course records, so can't test for the value of the field, as the record is no longer able to be viewed.

 

Apart from the rather kludgy and non-normalised setting of a flag in the parent Student record where this is the case, how can I test in order to apply RLA?

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.