Skip to content

DynamicForm issue with fields that are not part of #1986

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

Open
mrtnbrst opened this issue Apr 30, 2025 · 1 comment
Open

DynamicForm issue with fields that are not part of #1986

mrtnbrst opened this issue Apr 30, 2025 · 1 comment
Assignees
Labels
status:working-on-it Known issue / feature being addressed. Will use other "status:*" labels & comments for more detail. type:bug

Comments

@mrtnbrst
Copy link

mrtnbrst commented Apr 30, 2025

Thank you for reporting an issue, suggesting an enhancement, or asking a question. We appreciate your feedback - to help the team understand your
needs please complete the below template to ensure we have the details to help. Thanks!

Please check out the documentation to see if your question is already addressed there. This will help us ensure our documentation is up to date.

Category

[x] Bug

Version

Please specify what version of the library you are using: [ 3.20.0 ]

If you are not using the latest release, please update and see if the issue is resolved before submitting an issue.

Expected / Desired Behavior / Question

Like default SharePoint form, it should ignore fields in a section that do not exist (anymore).

Observed Behavior

DynamicForm crashes

Steps to Reproduce

Create section with default SharePoint form and add a column to a group that does not exist

Solution:
Add filter additional condition fieldCollection.includes(bsf)

.filter(bs => bs.fields.filter(bsf => hiddenByFormula.indexOf(bsf) < 0).length > 0)

@ValerasNarbutas
Copy link
Contributor

@michaelmaillot
cann you assign this to me as i am looking at dynamic form anyway?

@michaelmaillot michaelmaillot added status:working-on-it Known issue / feature being addressed. Will use other "status:*" labels & comments for more detail. type:bug labels May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:working-on-it Known issue / feature being addressed. Will use other "status:*" labels & comments for more detail. type:bug
Projects
None yet
Development

No branches or pull requests

3 participants