Limiting fields that can be exported by privilege set?

[txrobnla]

Does anyone know if there is a way to allow exports, but to limit what fields can be exports for different privilege sets?

I'm creating a runtime solution and I would like to give my users the ability export some of the data to excel. But in any given table, I have some data that is used for authentication that don't want users to ever be able to get access too or I'm compromising security.

I'm using FileMaker Pro 11.

Best,

Rob

[doughemi]

Script the exports

If(Get(PrivilegeSetName) = "FirstPrivSet")

	 Perform Script ["Export First Record Set"]

End If

If(Get(PrivilegeSetName) = "SecondPrivSet")

	 Perform Script ["Export Second Record Set"]

End If

Each subscript would have its own export order.

[comment]

See:

http://fmforums.com/forum/topic/70348-disable-layout-creation/

and also (new in version 11):

http://www.filemaker.com/11help/html/passwords.13.32.html#1043154

[Steven H. Blackwell]

Does anyone know if there is a way to allow exports, but to limit what fields can be exports for different privilege sets?

If a field is marked as <<No Access>> in the Custom Field Privileges definition in the Privilege Set, it will not export.

Further:

I have some data that is used for authentication

I don't know what you've done here, but this sounds as if you've likely introduced a vulnerability here. As a general rule, keep the security schema out of the data layer. When using Record Level Access however you must protect any fields in the table that are part of the RLA tests.

Steven