Hero web parts that were PnP provisioned - images are flickering as of 1/22

Question

This issue needs to be escalated.&nbsp; I have opened a Microsoft Support ticket, I will post to GitHub if it is a PnP issue, which I think it is, please advise.&nbsp;If added manually, the Hero web part seems fine, however if PnP provisioning is used to add it to the page the web part was working just fine until recently about 1/22/2019. All of the Hero web parts we have installed via PnP are flickering due to endless checks back to a CDN for a thumbnail image?The only way to fix the problem is to delete the Hero web part, add it back to the page, and reconfigure the links and images.&nbsp; The problem persists even if you fix the Hero web part on an extraction site, extract the page, and use that XML to provision to another page.The checks back to the CDN are endless and it causes our tenant to be throttled if we have too many of these pages rendering.&nbsp;We have done some more testing on this problem and have found:&nbsp;[‎1/‎25/‎2019 9:21 AM]&nbsp; We replaced the flickering Hero web part on this page and did an extraction.&nbsp; The guidFile # below was cut off but it is the same as the one in the next hyperlink.https://tenant.sharepoint.com/sites/samplesite1/_layouts/15/getpreview.ashx?resolution=2&amp;guidSite=283d395d-7178-4df4-a160-cfa3b56f56e1&amp;guidWeb=b69286d4-19f8-45a3-95a2-4b1da9bf6bf7&amp;guidFile=7876c5db-39aa-43da-b050-430ca13d82f5&amp;clientType=modernWebPart &nbsp;&nbsp;[‎1/‎25/‎2019 9:21 AM] We used the extraction from the above site and page to provision the same page on this site but the problem persists.&nbsp; Note the guidFile # below was cut off but it is the same which we think maybe a problem because shouldn't it be different?https://tenant.sharepoint.com/sites/samplesite2/_layouts/15/getpreview.ashx?resolution=2&amp;guidSite=147a420f-c0c4-4a64-a3bd-c8c01d6eee92&amp;guidWeb=d6eabfab-a187-4dbc-bdad-d96bbdbd5615&amp;guidFile=7876c5db-39aa-43da-b050-430ca13d82f5&amp;clientType=modernWebPart

beau cameron · Answer

This is a little hard to debug without knowing what code you are using. Can you share the PnP Code you are using to set the hero web part? I'd gladly explore this.

kim cote · Answer

This has all been working for the last 6 months so I think the Hero part has been published recently and changed or there are CDN issues.

We build a sample page that looks just the way we want on source site A.
We extract the page to XML using this code: Get-PnPProvisioningTemplate -Out $($saveDir.Path + "\" + $pageTemplate) -Handlers PageContents
The resulting XML file is attached, and again, this has all been working for 6 months+/-
We make sure all resources are on the destination site B and then we provisioning the page using this code: Apply-PnPProvisioningTemplate -Path $Path

I attached the XML file, inserted an image of the console showing the repeating error, and included the details of the error from the console below.

SiteATemplate.zip3 KB

jon tereba · Answer

I am getting the same experience when applying a PnP template that contains a hero web part. When manually adding a new hero web part to a page, it looks like the JSONProperties property has a new object property called imageUrl: {"imageUrl": "https://eastus1-mediap.svc.ms/transform/thumbnail?provider...}. This property not included when creating the Hero webpart from the PnP template. Do you think the web part was updated to retrieve thumbnails?

kim cote · Answer

Here are my concerns . . . &nbsp; &nbsp;I have reported this to Microsoft Support who cannot do anything because they don't cover PnP and on GitHub where PnP issues are supposed to be. &nbsp;I am hoping someone will consider this important because we really can’t afford for the different Microsoft entities to be passing the buck on these problems.&nbsp;Just consider this, let’s say we deploy applications with Hero web parts by PnP with there being only 3 pages per client.&nbsp; If we have 20 clients, then someone needs to go and manually remove, add, and setup the Hero web parts 60 times.&nbsp; But each tile image and link setting needs to be noted and subsequently recreated because the interface does not store the Hero tile setting information in a list that can easily be managed. &nbsp;That is a potential of 300 individual Hero tiles needing to be preserved, and re-setup.&nbsp; That takes a long time using the current interface.&nbsp; &nbsp;This is not just a PnP problem, &nbsp;the Hero web part does not fail gracefully in the absence of this configuration element.&nbsp; The Hero web part has been out for more than a year and until this has been resolved, Hero web parts that are PnP provisioned will constantly loop to access a thumbnail that does not exist.&nbsp; This will in turn throttle your tenant if too many pages are opened that have this problem, and the web sites in the tenant become unavailable for a period of time.&nbsp;It seems that the Hero web part code has been updated to reference a thumbnail image for each Hero tile.&nbsp; There is a new JSON property for this thumbnail which is probably generated if the Hero part is added via the user interface.&nbsp; &nbsp;&nbsp;However PnP, which is the only way we have been given to automate installs, does not yet accommodate this property.&nbsp; My final comments are:&nbsp;Microsoft cannot allow web part enhancements to go out that do not have corresponding PnP to facilitate any changes required by the part.Even though PnP is an open source project, supposedly not part of Microsoft proper, the operation of existing installations requires some regression testing, timing and cooperation between the web part and PnP development. Microsoft must test their new web part code against pages that have had the parts installed by PnP to make sure the parts can accommodate a test case with missing properties.Microsoft partners and customers and cannot afford to break away from the important work they are doing to continuously respond to unexpected changes with band-aids and quick hacks every time this happens.Has Microsoft forgotten proper regression testing and software quality assurance practices?

deleted · Answer

Hi,&nbsp;&nbsp;We are seeing the same issue in our tenant,for multiple hero web parts.we logged a prem support call with MS, and they have pointed us to this thread......issue is we have not used PNP to provision anything in our tenant we added all the hero web parts manually. we are seeing the same issue with the Auseast error.&nbsp;investigation found that Chrome and Firefox had the flickering image but edge did not.&nbsp;Since receiving the last message fro MS saying it was the PNP provisioning system the issue is no longer an issue.&nbsp;Hope your issues are sorted too.

Forum Discussion

Hero web parts that were PnP provisioned - images are flickering as of 1/22

Share

Resources