Invoke-SiteSwap breaks File Viewer web parts

%3CLINGO-SUB%20id%3D%22lingo-sub-1523393%22%20slang%3D%22en-US%22%3EInvoke-SiteSwap%20breaks%20File%20Viewer%20web%20parts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1523393%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20everyone%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20did%20a%20site%20swap%20of%20our%20root%20URL%20using%20%3CEM%3EInvoke-SiteSwap%3C%2FEM%3E%2C%20and%20it%20worked%20perfectly.%20That%20is%2C%20until%20I%20was%20going%20through%20the%20site%20pages%20and%20realized%20that%20none%20of%20the%20File%20Viewer%20web%20parts%20were%20correctly%20implemented.%20I%20don't%20have%20a%20screenshot%2C%20but%20it%20said%20the%20file%20could%20have%20been%20temporarily%20moved%2Fdiscarded%2Fsomething%20like%20that.%20I%20checked%20and%20saw%20the%20File%20Viewer%20web%20part%20was%20looking%20at%20the%20old%20root%20URL%20path.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20had%201x%20.docx%2C%204x%20.mp4%2C%20and%20the%20rest%20.pdf%20files.%20The%20.docx%20and%201%20of%20the%20.mp4%20were%20fine%2C%20but%20the%20rest%20were%20broken%20links.%20Our%20SharePoint%20site%20is%20relatively%20small%20compared%20to%20other%20tenants%2C%20so%20I%20just%20manually%20fixed%20all%20the%20File%20Viewer%20web%20parts%20that%20we%20had.%20I%20also%20didn't%20wait%20too%20long%20because%20I%20got%20impatient.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EShould%20I%20have%20given%20it%20more%20time%20before%20jumping%20the%20gun%20to%20fix%20it%20myself%3F%20Would%20the%20File%20Viewer%20web%20part%20have%20fixed%20itself%20after%20sometime%3F%20Did%20anyone%20else%20have%20this%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1523393%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Efile%20viewer%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Einvoke-siteswap%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esite%20swap%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eweb%20part%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

Hey everyone,

 

We did a site swap of our root URL using Invoke-SiteSwap, and it worked perfectly. That is, until I was going through the site pages and realized that none of the File Viewer web parts were correctly implemented. I don't have a screenshot, but it said the file could have been temporarily moved/discarded/something like that. I checked and saw the File Viewer web part was looking at the old root URL path.

 

We had 1x .docx, 4x .mp4, and the rest .pdf files. The .docx and 1 of the .mp4 were fine, but the rest were broken links. Our SharePoint site is relatively small compared to other tenants, so I just manually fixed all the File Viewer web parts that we had. I also didn't wait too long because I got impatient.

 

Should I have given it more time before jumping the gun to fix it myself? Would the File Viewer web part have fixed itself after sometime? Did anyone else have this issue?

 

Thanks in advance!

0 Replies