ViewsLifeTime not available under manged properties

[IrCheema]

Hi,
I am trying to show the total number of views for modern news pagesin my search results. However ViewsLifeTime properties are not available. I tried to manually add this property but it return null. However in OOTB News web part one can display number of views. Is their any way to get this fix in search results.
Does any body knows how to implement (ms graph toolkit) for Get itemAnalytics in Search results web part.
Thanks in advance.

[FredrikEkstroem]

Did you add ViewsLifeTime to both Layout Slots and Selected Properties on the first webpart settings panel? And then call it from the template like

{{slot item @root.slots.ViewsLifeTime}}

that works for me

[IrCheema]

Thanks Fredrik for your response. There is actually an issues that i am facing in the webpart as ViewsLifeTime is no longer available in the list of managed properties. So as per your suggestion i added the property manually in the Layout Slots and Selected Properties. I updated one of the card fields to show views, but still no success. In the debug mode i noticed that value for ViewsLifeTime is null for every result. While same results under OOTB news web part displaying number of views.

[wobba]

Can you explain your screenshot on what L37-38 are? I think you are affected by a bug which is fixed in v4.4 where when you enter a prop it's stored as the comma separated string - not as individual props. So the request is then wrong.

[IrCheema]

Thanks @wobba & @FredrikEkstroem , after updating to version v4.4 and implementing the solution suggested by Fredrik i am now able to get ViewsLifeTime for most of the news pages. While comparing with OOTB News web part i have noticed that there is a missmatch between number of views and for one of the news pages ViewsLifeTime is null. But i guess OOTB News web part is displaying views via itemAnalytics (Get itemAnalytics - graph api).
@wobba : Is there any way we can use itemAnalytics instead of ViewsLifeTime?

PnP Search V4 (4.4)

News Web Part

BR

[wobba]

If you implement a custom web component to run the API call needed you can do what you want. Also look at the other "views*" properties and see if you find the one matching the count you see on a page itself. They should be the same, or close, as there is some data sync in place.