Managed property for Image type column not getting created automatically

[vishalshitole]

What type of issue is this?

Question

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

other (enter in the "Additional environment details" area below)

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

No response

Issue description

Hello everyone!

I want to use Image column in one of my list. For that, I created a site column of type 'Image', added it to the site content type, applied that content type to the list, and added few items in the list with Image type column having some value.

I don't see the managed property for this site column created automatically. Is this how it works? Do I need to create it manually?

Note: I have waited for more than 72 hours after creating this column. Also re-indexed the list and the site. Still no luck.

Any inputs will be greatly appreciated. Thanks!

[mkm17]

HI @vishalshitole, I can observe the same effect on my tenant. I looked for some information and found that, according to @ganesh-sanap, this type of column does not have a crawled property yet. https://techcommunity.microsoft.com/t5/sharepoint/sharepoint-online-not-crawling-image-columns/m-p/2449025

@ganesh-sanap have you observed any change in this matter maybe?

[vishalshitole]

@mkm17 Thank you for your response.

I confirm that the Image type column does not have a crawled property created for it yet. As a result I could not create a managed property, and use it in Search.

@VesaJuvonen Curious to know if this is correct, and in the roadmap.

[Amey-MSFT]

Hello @vishalshitole,
Thank you for bringing this issue to our attention. Could you please confirm if the issue still persists for you?

[Amey-MSFT]

We are closing this issue for now. If the problem persists, feel free to reopen it or open a new one.