Skip to content
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

DynamicForm - Not showing the name field #1683

Closed
hdmal opened this issue Oct 19, 2023 · 3 comments · Fixed by #1912
Closed

DynamicForm - Not showing the name field #1683

hdmal opened this issue Oct 19, 2023 · 3 comments · Fixed by #1912
Assignees
Labels
status:fixed-next-drop Issue will be fixed in upcoming release. type:bug
Milestone

Comments

@hdmal
Copy link

hdmal commented Oct 19, 2023

Category

[ ] Bug

Version

Please specify what version of the library you are using: 3.15.0

Expected / Desired Behavior / Question

We have been using DynamicForm control in one of the SharePoint add-ins. Control works fine, except it's not displaying the Name (FileLeafRef) field. Users are expecting to modify custom fields, along with the file name.

When a user is inside a Document Library, and try to edit item properties, DynamicForm control should open the form with the "Name(FileLeafRef)" field for users to edit.

SharePoint edit properties form has this feature.

image

Observed Behavior

In a Document Library, DynamicForm opens without the "Name" field.

Configuration:
image

Output:
image

Steps to Reproduce

Create an SPFx project with DynamicForm control.
Open DynamicForm to edit a file properties.

Can you please help on this?

Thanks!

@ghost
Copy link

ghost commented Oct 19, 2023

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

@michaelmaillot
Copy link
Collaborator

Hi @hdmal,

The DynamicForm, by its design, is filtering list / library fields in order to display only the ones that can be "writable", I think that the initial query which gets all the fields could be updated to get the Name one (maybe something to update here.

Would you like to give a try on this one?

@michaelmaillot michaelmaillot added status:working-on-it Known issue / feature being addressed. Will use other "status:*" labels & comments for more detail. and removed help wanted labels Feb 10, 2024
martinlingstuyl added a commit to martinlingstuyl/sp-dev-fx-controls-react that referenced this issue Nov 13, 2024
@martinlingstuyl
Copy link
Contributor

Ok @michaelmaillot, I think I've got it. You can close the stale PR...

martinlingstuyl added a commit to martinlingstuyl/sp-dev-fx-controls-react that referenced this issue Nov 19, 2024
@michaelmaillot michaelmaillot added status:fixed-next-drop Issue will be fixed in upcoming release. and removed status:working-on-it Known issue / feature being addressed. Will use other "status:*" labels & comments for more detail. labels Nov 27, 2024
@michaelmaillot michaelmaillot added this to the 3.20.0 milestone Nov 27, 2024
@AJIXuMuK AJIXuMuK mentioned this issue Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:fixed-next-drop Issue will be fixed in upcoming release. type:bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants