-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Field Customizer: Field Customizer can't be applied to Name column in Document Library #1207
Comments
@AJIXuMuK - This is by design as the name field is marked as a nocustomize field. If you believe you need the name field to have a field customizer on it please open up a new request in user voice to request this feature. |
@mcmynn83 it is so weird!
Why did you actually decide to do it noncustomizable? |
@JLRishe do you have some information on how you managed to get this working? |
It works for FileLeafRef works fine in debug mode though. |
Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues |
Category
Expected or Desired Behavior
Field Customizer can be applied to Name column in Document Library
Observed Behavior
Field Customizer can't be applied to Name column in Document Library
Steps to Reproduce
FileLeafRef
orLinkFilename
field in any document library with CSOM/JSOM/REST:Note: the customizer is applied if you use debug url to apply it.
The text was updated successfully, but these errors were encountered: