This cloned descendant element is read-only, Click here to open editable first element (cmdb_ci.operational_status) in a new window.

[Siva Panja]

Hello,

My instance was upgraded to Kingstone and we are facing below issue.

This cloned descendant element is read-only, Click here to open editable first element (cmdb_ci.operational_status) in a new window.
I want to make this form editable, please help

[Marques1]

I fix this issue (in my case the Used For field, choice list was empty for extended tables) by editing the cmdb_ci_appl table through design form -> added the used_for field to the view and save it -> remove it back from the view and save it.

Once done it I was able to view the choice options in all extended tables. 

[Ricky S Larsson]

I have this issue as well. There seems to be no information about this in the Docs and I can't find any answer on how to work around this.

[Frank1975]

Hi all , 

this happend to us as well. Once upon a time, we have modified the cmdb_ci_appl table and added custom fields and made them mandatory. 
When Service Now decided to split all the Applications (tomcat, oracle and so in) in different tables, the cmdb_ci_appl table has been extened.

Now i have all the mandatory fields on these extended tables as well , which is causing the discovery to fail. 

The only workaround i found so far is, to go to the parent table (in my case cmdb_ci_appl) and make an dictionary overwrite for the mandatory fields but i would hate to do that for 214 extended tables 

Any suggestions very welcome

Frank

[freda92]

We had the same issue.  SteveM found a solution.  It is an ACL that is explicit to the reference field.

For example:

Table A has a reference field to the core_company table.

Go to ACL and elevate your rights

Create an ACL for Table A (write and read) to the Company field.

Using an asterisk will not work.

The ACL should look like in the name:

u_table_a.company

That made the reference field in Table A - accessible and available to the users.

Hope this helps