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

$web.AvailableFields return "The request use too many resource" error #10092

Open
1 of 9 tasks
frank1983 opened this issue Jan 27, 2025 · 0 comments
Open
1 of 9 tasks
Labels
type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.

Comments

@frank1983
Copy link

Target SharePoint environment

SharePoint Online

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

SharePoint CSOM

Developer environment

Windows

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

client api
powershell

Describe the bug / error

I have a Japanese modern communication site collection and with an English (modern team site) sub site. then I want to use client API
$fields=$web.AvailableFields
$context.Load($fields)
$context.ExecuteQuery()
to get the fields of the sub site.
if the login user who's preferred language is English I will got the error "The request use too many resource.", but if the login user preferred language is Japanese. it works fine.

Steps to reproduce

  1. Create a modern communication site collection, the default language is Japanese.
  2. in that site collection create a sub site. which default language is English and the template is no Microsoft 365 group.
  3. write a power shell to get the fields of the sub site.
    $fields=$web.AvailableFields
    $context.Load($fields)
    $context.ExecuteQuery()
    4, use the user1 to test the script, user1 preferred language is English. not same as the site collection default language then get the error.
    5, use the user2 to test the script, user2 preferred language is Japanese. same as the site collection default language. it works well

Expected behavior

no matter which user I used I think all the case should work well

@frank1983 frank1983 added the type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs. label Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Projects
None yet
Development

No branches or pull requests

1 participant