Home → How Do I... →

restrictions in data definitions

• Edit

jim.lorenz

05 Apr, 2016 08:26 PM

Consider the following data definition design:

  A repeating group called Level-1
    a field
    another repeating group called Level-2
       a field
       another repeating group called Level-3
          a field

I would like the site manager to be able to + - and edit Levels 1, 2, & 3
I would like the site content manager to be able to + - and edit Levels 2 & 3

If I define Level-1 with a restrict-to-groups for the site manager then the content manager cannot see anything.
If I remove that restriction and move it to the Level-1 field then the content manager can see Level-1 (but not the field) and is able to + - and edit Levels 2 & 3. However, the + - controls are still functional for Level 1; that's a deal breaker.

any Ideas? thanks

1. 1 Posted by Ryan Griffith on 06 Apr, 2016 06:24 PM

   

   Hi Jim,

   Unfortunately, this is not currently possible using group/field restrictions, because they are not very robust. Specifically, you can't restrict the multiple controls while leaving the group itself visible.

   My best suggestion would be to consider reworking your data definition. Perhaps avoiding the nesting or multiple groups? Or maybe you can figure out a way to use Smart Fields depending on the use case.

   Please let me know if you have any questions.

   Thanks!

   • Edit

2. 2 Posted by jim.lorenz on 07 Apr, 2016 12:30 PM

   

   Hi Ryan, thanks for your consideration and reply. I’ll come at the problem from a different angle.

   Cheers

   Jim

   Jim Lorenz
   Michigan State University
   Health Information Technology
   A536 East Fee Hall
   Michigan State University
   East Lansing, Michigan 48824
   517-355-2855

   • Edit

3. 3 Posted by Ryan Griffith on 07 Apr, 2016 01:42 PM

   

   Not a problem at all, Jim. My apologies for not being able to provide you with a solid workaround, but hopefully you are able to rework the setup to accomplish what you need.

   One idea that came to mind is splitting this page/block out into multiple assets. A couple of ways to accomplish this:

   • Create a folder hierarchy for each "level" and give access to those who need it. You can re-use the same data definition for the page/blocks at each level (since it's essentially the same thing). Then you would use an Index Block to render this hierarchy how you need
   • Similar to above, but instead of using an Index Block, add page or block choosers to the "main page" where you select the pages or blocks at each level.

   I'm going to go ahead and close this discussion, please feel free to comment or reply to re-open if you have any additional questions.

   Have a great day!

   • Edit

4. Ryan Griffith closed this discussion on 07 Apr, 2016 01:42 PM.

5. jim.lorenz re-opened this discussion on 07 Apr, 2016 05:52 PM

6. 4 Posted by jim.lorenz on 07 Apr, 2016 05:52 PM

   

   Thanks again Ryan

   Regards

   jim

   • Edit

7. Tim closed this discussion on 27 Apr, 2016 08:42 PM.