Link to home
Start Free TrialLog in
Avatar of maggieball
maggieball

asked on

Very basic controlled access section issue

This is almost too embarrasingly simple to ask, but it's driving me crazy.  I've created a controlled access section limited to a field.  It looks like it's working (when you doubleclick on it it is showing the correct user names based on the field), but the section's fields remain inaccessible to everyone, even those who have access.  The access formula is computed, and contains the field name, which is a computed field based on an @If Formula that gives canonicalised names.  If my name is listed, I still don't have access (though it is showing up when I double click on the section).  Any ideas?  Thanks!  
Avatar of CRAK
CRAK
Flag of Netherlands image

Are the fields editable?
It drove me crazy as well one day, untill a collegue noticed I only had computed fields in the section.
(I'm still trying to forget I did that!)

What about editable fields outside the section? Are those ok? If you don't have edit rights on doc-level.....
Avatar of marilyng
marilyng

access formula is computed<< try computed for display.  :)
Should that matter? I always use either computed or comp. when composed.

But another possibility has come to my mind: this field.... is it multi value?!
CRAK.. it does matter if the field it is referencing changes.  So the computed field that the section references might change on open or edit.  Therefore the Access section needs to be able to change on the fly.  Else it will be set on the open and not change until the save and reopen.
Ok... perhaps, but the field already showed the right name and still the section didn't work as expected. I'd try "controlled" valued first!
And, when moving towards CfD fields, maggieball will have to make sure there's value left/stored in the document (FIELD theFieldName:=@Unavailable), or the stored value will overrule the CfD value!
Avatar of maggieball

ASKER

Hi everyone.  I tried computed when composed but it didn't help.  I have designer access to the database and all fields on the form are editable except the ones in the section (which are editable).  There is just on (editable) field in the section which *is* a multi value field - a dialog list which uses the address book for choices.  There's also a button with a simple mail send action in it.  That's it.  Both are working exactly as I'd expect (field not visible and button greyed out) except that they don't become available when my name is listed in the field that is supposed to provide access.  Sorry to be (as usual!) a dolt, but CRAK, what do you mean by a "controlled" value?  
Interestingly, when I test it locally, I have access even if my name isn't in the access field.  When I test it on the server (a development server rather than a production one), I don't have access even if my name is in the access field and being listed as the editor of the field.  I'm wondering if this is an admin, rather than a development problem.  Anyone else experienced this kind of thing?  I haven't worked much with controlled access sections.  Do they not work locally?  Thanks!  Maggie
ASKER CERTIFIED SOLUTION
Avatar of marilyng
marilyng

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Sorry, I mean to say Computed for Display (I did try that), and of course this time it worked :-).  Once more I was caught out (you'd think I'd learn!) by the need to close and reopen before the section access took effect.  That will work.  Thanks again Marylyn - your careful and patient explanations are a standout.  Maggie
Not a problem, it can be really frustrating when trying to figure out why stuff doesn't work.  I think the first time I did controlled access sections, I was at it for hours, spitting nails.  I probably would have ripped off anyone's face if they walked into the office to say, Hello!

Sorry, about the bold letters, wanted to be sure you saw that. :)