Professional SPFx Solutions: Superb solution packages

[utterances-bot]

Professional SPFx Solutions: Superb solution packages

SharePoint Framework (SPFx) is an extensibility model for Microsoft 365 enabling developers to build different kinds of extensibility for Microsoft Viva, Microsoft Teams, Outlook, Microsoft 365 app (Office), and SharePoint.

https://pnp.github.io/blog/post/spfx-21-professional-solutions-superb-solution-packages/

[Disc0veryX]

Great article! Very detailed and interesting. Thank you!

[LuiseFreese]

@hugoabernier 👏

[PolnikR]

hi , is there posibility to updata publisher column ?

[anisiaalexandra]

hi, very complete article! Which metadata should be updated in order to update the Appear as, Solution type and Legal details? thanks

[hugoabernier]

Thank you @anisiaalexandra ! Unfortunately, some of the details come from a separate manifest used by the App Source, and you'll only get access to change them by publishing your app (which is probably not ideal for your case. Another example of this is how the description is supposed to support rich-text, but it doesn't allow rich-text through the SPFx manifest, yet apps on App Source have rich-text in them.

I hope this helps?

[anisiaalexandra]

@hugoabernier thank you for your response. It is of help. Indeed in our case we cannot publish the app, but we will manage this aspects in a different way so that we can have at least the Legal details on it 👍 .

Have a bright day!

[Haiqi-Wu]

Hi Guys， What is the best practice regarding the version number within the package-solution.json? After the SPFx package update version number is uploaded, the update is sometimes displayed within the site without clicking the get prior version button. If there are many sites with the same SPFx app installed, how can one give updates to the app within each site after that app has been updated with a new version (it's impractical to do this manually for each site), PowerShell script might be an option, but it doesn't seem to be a sensible one either!