Skip to content

Commit cef7d8a

Browse files
RichardPriddyVesaJuvonen
authored andcommitted
Update provision-sp-assets-from-package.md (SharePoint#1992)
* Update provision-sp-assets-from-package.md When defining the ListInstance XML for elements.xml, the FeatureId must be 00bfea71-de22-43b2-a848-c05709900100 * Update provision-sp-assets-from-package.md
1 parent 775e5a7 commit cef7d8a

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,7 @@ In the following steps, we define the needed structure to be provisioned.
159159
* Definitions use standard Feature Framework schema, which is well known to SharePoint developers.
160160
* Custom fields are being referenced in the introduced content type.
161161
* We use the **CustomSchema** attribute in the **ListInstance** element to define a provisioning time schema.xml file for the list. This way the list is still based on the out-of-the-box list template (normal custom list '100' in this case), but we can define an alternative provisioning definition during initial provisioning.
162+
* When provisioning list instances using Features you must provide the ID of the Feature associated with the particular list definition. Using the FeatureId attribute you are supposed to provide the ID of the Feature which contains the List Definition. As an example: if you’re provisioning an instance of a custom list the FeatureId attribute should be set to {00bfea71-de22-43b2-a848-c05709900100}.
162163

163164
More details about the used schema structures can be found at [Using Features in SharePoint Foundation](https://msdn.microsoft.com/en-us/library/office/ms460318(v=office.14).aspx) on MSDN.
164165

0 commit comments

Comments
 (0)