You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For every feature a new GUID should be defined (SharePoint#1713)
It is too tempting to copy and paste the code in her resulting that ever SPFx solution that deploys assets uses the same GUID :D
Just to make things clear :D
"id": "523fe887-ced5-4036-b564-8dad5c6c6e24",// <-- Update 'id' with a new GUID
251
251
"version": "1.0.0.0",
252
252
"assets": {
253
253
"elementManifests": [
@@ -267,6 +267,8 @@ Now we have created the needed structures for provisioning SharePoint assets aut
267
267
268
268
Note the following about the added json definitions:
269
269
270
+
* Make sure you define a **unique GUID** for the id property inside the feature section
271
+
270
272
* You can technically have multiple features in the package because **features** is a collection; however, this is not recommended.
271
273
272
274
***elements.xml** is referenced under elementManifests so that it's packaged properly for the actual feature XML structure as an element manifest file.
0 commit comments