InfoPath form library rendering .xml

%3CLINGO-SUB%20id%3D%22lingo-sub-162222%22%20slang%3D%22en-US%22%3EInfoPath%20form%20library%20rendering%20.xml%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-162222%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20user%20who%20is%20reporting%20some%20odd%20behavior%20in%20the%20%22modern%22%20SharePoint%20library%20UI.%20She%20has%20an%20InfoPath%20form%20library%2C%20and%20when%20clicking%20on%20the%20document%20link%20to%20open%20it%2C%20all%20she%20sees%20is%20the%20.xml).%20If%20she%20switches%20back%20to%20the%20%22classic%22%20UI%20and%20clicks%20on%20the%20document%20title%2C%20the%20form%20opens%20up.%20Is%20this%20normal%3F%20I%20mean%2C%20I%20know%20InfoPath%20is%20going%20away%2C%20but%20MS%20is%20supposed%20to%20be%20supporting%20it%20until%202026.%20I%20have%20share%20a%20couple%20workarounds%20with%20her%2C%20including%20switching%20back%20to%20classic%20view%2C%20but%20has%20anyone%20else%20experienced%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-162222%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-177055%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20form%20library%20rendering%20.xml%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177055%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20to%20know.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-177030%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20form%20library%20rendering%20.xml%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177030%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20654px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F31123iA4CA2D01B9E1ED3C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22xml%20doc%20lib.JPG%22%20title%3D%22xml%20doc%20lib.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EChoose%20Classic%20Experience%20for%20all%20form%20libraries%20with%20InfoPath%20forms.%20That%20should%20fix%20the%20issue%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170647%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20form%20library%20rendering%20.xml%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170647%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20want%20to%20add%20an%20update%20to%20this..%20Today%2C%20ALL%20my%20Infopath%20forms%20NOW%20work%20in%20%22Modern%20View%22%20.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170616%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20form%20library%20rendering%20.xml%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170616%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20dean%20for%20the%20helpful%20link!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20would%20be%20helpful%20to%20allow%20users%20to%20open%20and%20view%20Infopath%20forms%20in%20%22Modern%20View%22.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20work%20for%20a%20corporation%20with%201000%20%2B%20employees%20and%20have%20to%20tell%20people%20daily%20that%20they%20need%20to%20click%3A%20%22Return%20to%20classic%20View%22%20to%20use%20the%20Infopath%20forms.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMy%20Infopath%20forms%20used%20to%20work%20in%20%22modern%20view%22%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20anyone%20else%20is%20having%20similar%20issues%20and%20would%20like%20for%20Microsoft%20to%20work%20on%20a%20solution%2C%20give%20this%20post%20a%20reply%20so%20it%20can%20get%20some%20attention.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170583%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20form%20library%20rendering%20.xml%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170583%22%20slang%3D%22en-US%22%3E%3CP%3Ethis%20is%20expected%20behavior%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22lf-text-block%20lf-block%22%20data-lf-anchor-id%3D%22d45d690044469cf3f985880e07bd76c5%3A0%22%3Ethese%20customizations%20are%20currently%20not%20supported%20for%20%22modern%22%20lists%20and%20libraries%3A%3C%2FP%3E%0A%3CUL%20class%3D%22lf-text-block%20lf-block%22%20data-lf-anchor-id%3D%22abc354c07840646957689293f0092743%3A0%22%3E%0A%3CLI%3EJSLink-based%20field%20customizations%20(see%20Note%20on%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3ESharePoint%20Framework%20Extensions%3C%2FEM%3E)%3C%2FLI%3E%0A%3CLI%3EJSLink-based%20view%20customizations%20(see%20Note%20on%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3ESharePoint%20Framework%20Extensions%3C%2FEM%3E)%3C%2FLI%3E%0A%3CLI%3ECustom%20CSS%20via%20AlternateCSSUrl%20web%20property%3C%2FLI%3E%0A%3CLI%3ECustom%20JavaScript%20embedded%20via%20user%20custom%20actions%20(see%20Note%20on%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3ESharePoint%20Framework%20Extensions%3C%2FEM%3E)%3C%2FLI%3E%0A%3CLI%3ECustom%20master%20pages%20(more%20extensive%20branding%20will%20be%20supported%20later%20using%20alternative%20options)%3C%2FLI%3E%0A%3CLI%3ECustomization%20via%20InfoPath%3C%2FLI%3E%0A%3CLI%3EMinimal%20Download%20Strategy%20(MDS)%3C%2FLI%3E%0A%3CLI%3ESharePoint%20server%20publishing%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3Esee%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsharepoint%2Fdev%2Fsolution-guidance%2Fmodern-experience-customizations-customize-lists-and-libraries%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsharepoint%2Fdev%2Fsolution-guidance%2Fmodern-experience-customizations-customize-lists-and-libraries%3C%2FA%3E%20for%20more%20details%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170576%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20form%20library%20rendering%20.xml%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170576%22%20slang%3D%22en-US%22%3EI%20am%20having%20the%20same%20issue!%3C%2FLINGO-BODY%3E
Highlighted
Deleted
Not applicable

I have a user who is reporting some odd behavior in the "modern" SharePoint library UI. She has an InfoPath form library, and when clicking on the document link to open it, all she sees is the .xml). If she switches back to the "classic" UI and clicks on the document title, the form opens up. Is this normal? I mean, I know InfoPath is going away, but MS is supposed to be supporting it until 2026. I have share a couple workarounds with her, including switching back to classic view, but has anyone else experienced this?

6 Replies
Highlighted
I am having the same issue!
Highlighted

this is expected behavior

 

these customizations are currently not supported for "modern" lists and libraries:

  • JSLink-based field customizations (see Note on SharePoint Framework Extensions)
  • JSLink-based view customizations (see Note on SharePoint Framework Extensions)
  • Custom CSS via AlternateCSSUrl web property
  • Custom JavaScript embedded via user custom actions (see Note on SharePoint Framework Extensions)
  • Custom master pages (more extensive branding will be supported later using alternative options)
  • Customization via InfoPath
  • Minimal Download Strategy (MDS)
  • SharePoint server publishing

see https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/modern-experience-customizations-c... for more details

Highlighted

Thanks dean for the helpful link!

 

It would be helpful to allow users to open and view Infopath forms in "Modern View". 

 

I work for a corporation with 1000 + employees and have to tell people daily that they need to click: "Return to classic View" to use the Infopath forms. 

 

My Infopath forms used to work in "modern view" 

 

If anyone else is having similar issues and would like for Microsoft to work on a solution, give this post a reply so it can get some attention. 

 

 

Highlighted

Just want to add an update to this.. Today, ALL my Infopath forms NOW work in "Modern View" . 

 

 

 

 

 

Highlighted

xml doc lib.JPG

Choose Classic Experience for all form libraries with InfoPath forms. That should fix the issue

Highlighted

Good to know. 

 

Thanks