BUG: "NoComponentId" serverside error when parameter "List=GUID" in URL to ClientSidePage! Why?

[frevds]

Category

• Question
• Bug
• Enhancement

Expected or Desired Behavior

Supplying the "List" URL parameter should not cause a serverside error saying "NoComponentId".

Observed Behavior

Supplying the "List" URL parameter (with a correctly formatted GUID as value) causes a serverside error saying "NoComponentId".

Steps to Reproduce

1. Create a new Site Page.
2. Open it - this works.
3. Open it again with the URL the parameter ?List=00000000-0000-0000-0000-000000000001 appended - this fails.

It does not matter whether the list exists or not, the error occurs if the value is a valid GUID (and not empty).

This issue causes a big problem for our solution. Please let me know what I can do to circumvent it, or where and why it occurs. I do need a list context there and the name of the parameter cannot be changed.

Update: I discovered that the error does not occur if the GUID supplied is the ID of the SitePages library (i.e. the list where the ClientSidePage is hosted). So I assume the framework somehow uses this "List" parameter to encode the location of the page itself. However, this is very inconvenient, it should not use standard SharePoint parameters and fail if they have unexpected values!

Update2: The framework apparently looks into the list with the specified GUID and at the item specified by the ID parameter and determines the ClientSideApplicationId field. If that is filled with an identifier that is registered as a component (whereever that may be), the page opens, otherwise some related error like "ComponentIdNotFound" or "No item exists" happens.

[msft-github-bot]

This issue is being closed as part of an issue list cleanup project. Issues with no activity in the past 6 months that aren't tracked by engineering as bugs were closed as part of this inititive. If this is still an issue, please follow the steps outlined to re-open the issue.