SiteID now is SiteId ??????????

[MagtheRag]

Category

• Question
• Typo
• Bug
• Additional article idea

Expected or Desired Behavior

When search through the rest api as in '/_api/search' then I expect that the properties of each search row object is presented in the same way and not change casing suddenly so that the code that we have IN PRODUCTION breaks as we do not find the property we are looking for.

Observed Behavior

In Target release tenant the response has changed when selecting the SiteID to SiteId.

Steps to Reproduce

Do a search in a target release tenant
[tentant]/_api/search/query?querytext=%27*%27&selectproperties=%27SiteID%27

Submission Guidelines

Thanks for your contribution! Sharing is caring.

[msft-github-bot]

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

[andrewconnell]

I'm not clear... what are you seeing that's different? I ran the same query in two tenants, one SR & one TR and the results are the same...

[CPritch]

I can confirm repro following @MagtheRag repro steps. The response from a developer tenant is that 'SiteID' has now become 'SiteId'. A tenancy not on first-release responds with the key 'SiteID' for the request as described.

[andrewconnell]

I'm still not clear... sorry, maybe I'm a little dense on this one, but I don't see the difference or what the "error" is as when I run the same query for the same two properties, SiteID or SiteId on an SR & TR tenant, I'm getting the same response back for both.

I wasn't familiar with the property being SiteID previously, but when I query for SiteID or SiteId, I'm getting the same response... so the casing isn't changing an issue.

So... what exactly is the issue?

[CPritch]

Yes the casing is changing. I can get more details on the affected tenants if you need that. SiteID was being returned for our UK production tenants from when I last tested this.

[andrewconnell]

You're missing the point of my comment: what is the exact problem. The OP provides an API to get a property. When you change the query to either of the values, you get the same result.

So, my impression is that the OP is calling out you get different results based on the casing used. My point: that's not what I'm seeing & thus, can't repro any issue. Thus my "not clear" comment & label on the issue.

If that's not the correct problem, it needs to be restated / explicitly stated.

[MagtheRag]

The problem is when you have an app that reads from the properties and assume that the property should be SiteID then it does not exist and you will not find that property on the object that is returned. It is not that we are trying to query for the site id. We want to fetch it.

[andrewconnell]

This helps @MagtheRag, thanks. I thought the issue was related to the query you were running.