Skip to content

API "RenderListDataAsStream" returns Element #10187

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
2 of 9 tasks
LordPalpatine opened this issue Apr 9, 2025 · 4 comments
Open
2 of 9 tasks

API "RenderListDataAsStream" returns Element #10187

LordPalpatine opened this issue Apr 9, 2025 · 4 comments
Assignees
Labels
Needs: Author Feedback Awaiting response from the original poster of the issue. Marked as stale if no activity for 7 days.

Comments

@LordPalpatine
Copy link

What type of issue is this?

Question

What SharePoint development model, framework, SDK or API is this about?

SharePoint REST API

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)

Additional environment details

Issue description

For some users the API call of "RenderListDataAsStream" with RenderOptions=64 returns "ClientForms.New.Element" and for others "ClientForms.New.Item".
Why is this so?

@Amey-MSFT
Copy link

Hello @LordPalpatine ,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

@Amey-MSFT
Copy link

Amey-MSFT commented Apr 10, 2025

Hello @LordPalpatine ,
This behavior might be due to user-specific form settings and permissions. The RenderListDataAsStream API with RenderOptions=64 returns ClientForms.New.Element or ClientForms.New.Item based on how the NewForm.aspx is customized for the list and the user context.

If the form is customized using Power Apps or InfoPath, or if users have different default form settings, the response differs. Also, certain permissions can cause fallback to default rendering.

Microsoft Docs Reference:
RenderListDataAsStream

To resolve or unify the behavior:

  • Ensure form customizations are consistent across users.

  • Check if the list has Power Apps or InfoPath customization.

  • Confirm users have equivalent permissions on the list.

Let me if further help is required on the same.
Thanks!!

@ChetanSharma-msft ChetanSharma-msft added the Needs: Author Feedback Awaiting response from the original poster of the issue. Marked as stale if no activity for 7 days. label Apr 11, 2025
@LordPalpatine
Copy link
Author

LordPalpatine commented Apr 11, 2025

Thanks for the reply!

- Ensure form customizations are consistent across users.
We use a "Form Customizer extension" (SPFx) for this list. So this should be consistent across all users.
"../_layouts/15/SPListForm.aspx?PageType=8&List=61938eb3-d79a-403b-aad6-3d0b64adf2ca" instead of NewForm.aspx is used.

- Check if the list has Power Apps or InfoPath customization.
No Power Apps or InfoPath.

- Confirm users have equivalent permissions on the list.
All users are in the same group, no exclusive permissions.

Sadly I cannnot replicate this behavior with my test-users (permissions). I could not find any differences between the affected users and my test-user-account.

@Amey-MSFT
Copy link

Hello @LordPalpatine ,
As you asked why for some users the API call of "RenderListDataAsStream" with RenderOptions=64 returns "ClientForms.New.Element" and for others "ClientForms.New.Item".
Are you satisfied with why this behaviour might be be happeneing response?

Let me if further help is required on the same.
Thanks!!

@Amey-MSFT Amey-MSFT self-assigned this Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Author Feedback Awaiting response from the original poster of the issue. Marked as stale if no activity for 7 days.
Projects
None yet
Development

No branches or pull requests

3 participants