Skip to content

Commit 21e3ad7

Browse files
StfBauerVesaJuvonen
authored andcommitted
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
1 parent 168ed7b commit 21e3ad7

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/spfx/web-parts/get-started/provision-sp-assets-from-package.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -247,7 +247,7 @@ Now we have created the needed structures for provisioning SharePoint assets aut
247247
"features": [{
248248
"title": "asset-deployment-webpart-client-side-solution",
249249
"description": "asset-deployment-webpart-client-side-solution",
250-
"id": "523fe887-ced5-4036-b564-8dad5c6c6e24",
250+
"id": "523fe887-ced5-4036-b564-8dad5c6c6e24", // <-- Update 'id' with a new GUID
251251
"version": "1.0.0.0",
252252
"assets": {
253253
"elementManifests": [
@@ -267,6 +267,8 @@ Now we have created the needed structures for provisioning SharePoint assets aut
267267

268268
Note the following about the added json definitions:
269269

270+
* Make sure you define a **unique GUID** for the id property inside the feature section
271+
270272
* You can technically have multiple features in the package because **features** is a collection; however, this is not recommended.
271273

272274
* **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

Comments
 (0)