Application extends the task table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2017 10:04 AM
I have created an application where the table associate to it , it extends the Task table..... I have created a form with two fields that comes from the extended table (Description and Priority) are gray-out when I switch to a non-admin account. I noticed in the access properties for these two variables the following
Priority
Description
What I did wrong when I created the table to makes these inherent fields to be gray-out? or do I need to add a user role ? I dont think so, that will defeat the purpose of inheritance!
The other question if may I ask? For the attachment option to be present in form, do you only need to configure it in the related list
I just don't see it when the form loads.
thanks for the help!!
- Labels:
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2017 11:32 AM
Ohh ok I forgot about that.... let me give it a try.... i will let you know.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2017 12:00 PM
Ok creating the ACL is not a problem..... how you add the role to the APPS?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2017 03:02 PM
Im sorry can someone please explain me what I need to do..... to make a column writeable in the child table.
This is the access of the table
Just dont understand why I need to create an acl for this field.... if I am allow to modified the properties of the field such as the label.
Why when I load the form these fields which are inherent from Task are not writable in the child table?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2017 10:20 AM
I got it to work..... I added the ITIL role to the group user where the user resides...... and that makes the field from the base table writable..... is there a better way?