3

I was a created a Document Library all fields creating with no issues.

only problem with Restricted field name.

I was created a Restricted field as choice field but it was coming as lookup field.(see the attachement.)

this was happening only in 2016 site. (Note: If i create the column manually with same name it was creating. but i want to create by list definition) enter image description here

  • Is there a Site Column named 'Restricted'? – Trevor Seward Jun 9 '17 at 14:46
  • With column name Restricted No site columns are present in site – elina Jun 12 '17 at 9:54
  • Yep. Got caught out by this today. Legacy code that referenced a column by internal name 'Restricted'. We just changed it to 'IsRestricted' and modified our legacy code and all was swell. – davewasthere Jun 26 '19 at 7:09
1

Yes, this is a rather annoying "feature" in 2016. "Restricted" seems to be a new reserved keyword of some sort which causes issues due to naming conflicts. We just went through a large migration process which resulted in numerous apps failing because we were querying based on "Restricted" and specifying that field as viewfields and select parameters.. Now, the fields are all named Restricted0, cf00_Restricted, and other strange things.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.