ACLs and Views - having trouble getting specific fields to show in ESS view

[Mickey_Cegon]

We have just recently started using the ESS homepage for our clients to be able to view their own Incidents and Requests. Currently, when they launch a record from their homepage, the Incident form is locked down. I would like to be able to allow clients to add Comments from the form, and see their comments in the Activity log as well. But, I can't seem to get the field to show up. All I get is the label. I added ACL for read/write/create and set the condition: caller_id = javascript:gs.getUserID()

But, when I impersonate an ESS user, I still can't see or edit the Additional Comments field. What am I missing? Is there something else, like the view that is locking the form down, so that I can't overwrite that with ACLs? We're still on June 11 version, not on Aspen yet. I know that the ACL stuff is changing, so maybe I should just wait until we upgrade, and then revisit this if I'm going to end up having to change it then.

[treycarroll]

I have the same issue with a table that is extended from task:

I have blown the read ACLs wide open by changing them to answer = true; throughout the table/read hierarchy (script exclusively ) on task down to my derived table, but these fields will not appear on the form.

[treycarroll]

I finally found my issue after many hours of painful work.

For the benefit of others... here is what I found:

One of the scenarios which can produce these behavior occurs when you extend the task table and you add a user role to the table.   Even if you search for ACL scripts or ACL roles that contain that role, and those ACLs have been altered to no longer contain any trace of the table-level role...   A use who lacks this role will be unable to see the fields at all.

Trey Carroll