The CreatorCon Call for Content is officially open! Get started here.

Unable to edit reference fields from Now Platform

Carlos Camacho
Mega Sage
Mega Sage

I've a table that extends the Task and has many reference fields. 
IE: ref. for other internal tables, ref. for Country (core_country), ref. for Group, ref. for User, ref. for Company, ref. for sys_choice and so on. 
When trying to edit a record within the Now platform, I can only delete an existing option but I'm unable to unlock the field and add more items. Have you seen this issue before?
Thank you.

2 ACCEPTED SOLUTIONS

Hi Carlos,

 

It seems odd to me that if all custom fields on the child table are defined as 'read-only', but only those that are reference fields can't be edited, while the fields defined different can be edited. There is more going on here and you may want to create a Support Case.

 

Enabling "Debug Security" and reproducing will show you ACL activity.

View solution in original post

Carlos Camacho
Mega Sage
Mega Sage

Info: 

I saw the $j( ) is not a function error in the console when trying to edit the fields.
It was the root cause. 

 

View solution in original post

4 REPLIES 4

Bert_c1
Kilo Patron

Hi Carlos,

 

Your problem may be due to ACLs defined on the table and/or field.  There are also Data Policies, UI Policies, plus other means that can make a field 'Read-only'.

 

If you provide specific details, you may receive better assistance here. I suspect your table is a custom table, and if the field in question is inherited from task or defined on the child table.

Hi Bert_c1,

It is a custom table and all fields read-only are defined in this child table.
The fields are all of type reference, and fields of other types (text, choice, true/false) can be edited.
I didn't think of Data Policies and I'll check ACLs/Scripts inherited from the Task table.
Thanks.

Hi Carlos,

 

It seems odd to me that if all custom fields on the child table are defined as 'read-only', but only those that are reference fields can't be edited, while the fields defined different can be edited. There is more going on here and you may want to create a Support Case.

 

Enabling "Debug Security" and reproducing will show you ACL activity.

Carlos Camacho
Mega Sage
Mega Sage

Info: 

I saw the $j( ) is not a function error in the console when trying to edit the fields.
It was the root cause.