Bug report: Cannot create a new SharePoint list using example command with schemaXml option #2906

danwatford · 2021-12-29T15:58:16Z

Description

Attempts to create a new list on an existing SharePoint online team site fails with 'Error: Invalid list template.'

Unfortunately there is no information provided in the error response from SharePoint to help determine the issue with the schemaXml.

The same issue occurs if using the schemaXml example from the documentation page, https://pnp.github.io/cli-microsoft365/cmd/spo/list/list-add/

Steps to reproduce

At an ubuntu terminal, running under wsl:

Install using 'npm install -g @pnp/cli-microsoft365'
Login to SP site using 'm365 login'
Run the following command, copied from the example given in documentation page https://pnp.github.io/cli-microsoft365/cmd/spo/list/list-add/, changing the --webUrl argument to refer to an existing site:

m365 spo list add --title Announcements --baseTemplate Announcements --webUrl https://watconsdev.sharepoint.com/sites/bfwvendors --schemaXml '<List xmlns:ows="Microsoft SharePoint" Title="List1" FolderCreation="FALSE" Direction="$Resources:Direction;" Url="Lists/List1" BaseType="0" xmlns="http://schemas.microsoft.com/sharepoint/"><MetaData><ContentTypes><ContentTypeRef ID="0x01"><Folder TargetName="Item" /></ContentTypeRef><ContentTypeRef ID="0x0120" /></ContentTypes><Fields><Field ID="{fa564e0f-0c70-4ab9-b863-0177e6ddd247}" Type="Text" Name="Title" DisplayName="$Resources:core,Title;" Required="TRUE" SourceID="http://schemas.microsoft.com/sharepoint/v3" StaticName="Title" MaxLength="255" /></Fields><Views><View BaseViewID="0" Type="HTML" MobileView="TRUE" TabularView="FALSE"><Toolbar Type="Standard" /><XslLink Default="TRUE">main.xsl</XslLink><RowLimit Paged="TRUE">30</RowLimit><ViewFields><FieldRef Name="LinkTitleNoMenu"></FieldRef></ViewFields><Query><OrderBy><FieldRef Name="Modified" Ascending="FALSE"></FieldRef></OrderBy></Query><ParameterBindings><ParameterBinding Name="AddNewAnnouncement" Location="Resource(wss,addnewitem)" /><ParameterBinding Name="NoAnnouncements" Location="Resource(wss,noXinviewofY_LIST)" /><ParameterBinding Name="NoAnnouncementsHowTo" Location="Resource(wss,noXinviewofY_ONET_HOME)" /></ParameterBindings></View><View BaseViewID="1" Type="HTML" WebPartZoneID="Main" DisplayName="$Resources:core,objectiv_schema_mwsidcamlidC24;" DefaultView="TRUE" MobileView="TRUE" MobileDefaultView="TRUE" SetupPath="pages\viewpage.aspx" ImageUrl="/_layouts/15/images/generic.png?rev=23" Url="AllItems.aspx"><Toolbar Type="Standard" /><XslLink Default="TRUE">main.xsl</XslLink><JSLink>clienttemplates.js</JSLink><RowLimit Paged="TRUE">30</RowLimit><ViewFields><FieldRef Name="LinkTitle"></FieldRef></ViewFields><Query><OrderBy><FieldRef Name="ID"></FieldRef></OrderBy></Query><ParameterBindings><ParameterBinding Name="NoAnnouncements" Location="Resource(wss,noXinviewofY_LIST)" /><ParameterBinding Name="NoAnnouncementsHowTo" Location="Resource(wss,noXinviewofY_DEFAULT)" /></ParameterBindings></View></Views><Forms><Form Type="DisplayForm" Url="DispForm.aspx" SetupPath="pages\form.aspx" WebPartZoneID="Main" /><Form Type="EditForm" Url="EditForm.aspx" SetupPath="pages\form.aspx" WebPartZoneID="Main" /><Form Type="NewForm" Url="NewForm.aspx" SetupPath="pages\form.aspx" WebPartZoneID="Main" /></Forms></MetaData></List>'

Expected results

A new SharePoint list called Announcements is created.

Actual results

An error result is given by m365:
Error: Invalid list template.

Diagnostics

Executing command spo list add with options {"options":{"debug":true,"title":"Announcements","baseTemplate":"Announcements","webUrl":"https://watconsdev.sharepoint.com/sites/bfwvendors","schemaXml":"<List xmlns:ows=\"Microsoft SharePoint\" Title=\"List1\" FolderCreation=\"FALSE\" Direction=\"$Resources:Direction;\" Url=\"Lists/List1\" BaseType=\"0\" xmlns=\"http://schemas.microsoft.com/sharepoint/\"><MetaData><ContentTypes><ContentTypeRef ID=\"0x01\"><Folder TargetName=\"Item\" /></ContentTypeRef><ContentTypeRef ID=\"0x0120\" /></ContentTypes><Fields><Field ID=\"{fa564e0f-0c70-4ab9-b863-0177e6ddd247}\" Type=\"Text\" Name=\"Title\" DisplayName=\"$Resources:core,Title;\" Required=\"TRUE\" SourceID=\"http://schemas.microsoft.com/sharepoint/v3\" StaticName=\"Title\" MaxLength=\"255\" /></Fields><Views><View BaseViewID=\"0\" Type=\"HTML\" MobileView=\"TRUE\" TabularView=\"FALSE\"><Toolbar Type=\"Standard\" /><XslLink Default=\"TRUE\">main.xsl</XslLink><RowLimit Paged=\"TRUE\">30</RowLimit><ViewFields><FieldRef Name=\"LinkTitleNoMenu\"></FieldRef></ViewFields><Query><OrderBy><FieldRef Name=\"Modified\" Ascending=\"FALSE\"></FieldRef></OrderBy></Query><ParameterBindings><ParameterBinding Name=\"AddNewAnnouncement\" Location=\"Resource(wss,addnewitem)\" /><ParameterBinding Name=\"NoAnnouncements\" Location=\"Resource(wss,noXinviewofY_LIST)\" /><ParameterBinding Name=\"NoAnnouncementsHowTo\" Location=\"Resource(wss,noXinviewofY_ONET_HOME)\" /></ParameterBindings></View><View BaseViewID=\"1\" Type=\"HTML\" WebPartZoneID=\"Main\" DisplayName=\"$Resources:core,objectiv_schema_mwsidcamlidC24;\" DefaultView=\"TRUE\" MobileView=\"TRUE\" MobileDefaultView=\"TRUE\" SetupPath=\"pages\\viewpage.aspx\" ImageUrl=\"/_layouts/15/images/generic.png?rev=23\" Url=\"AllItems.aspx\"><Toolbar Type=\"Standard\" /><XslLink Default=\"TRUE\">main.xsl</XslLink><JSLink>clienttemplates.js</JSLink><RowLimit Paged=\"TRUE\">30</RowLimit><ViewFields><FieldRef Name=\"LinkTitle\"></FieldRef></ViewFields><Query><OrderBy><FieldRef Name=\"ID\"></FieldRef></OrderBy></Query><ParameterBindings><ParameterBinding Name=\"NoAnnouncements\" Location=\"Resource(wss,noXinviewofY_LIST)\" /><ParameterBinding Name=\"NoAnnouncementsHowTo\" Location=\"Resource(wss,noXinviewofY_DEFAULT)\" /></ParameterBindings></View></Views><Forms><Form Type=\"DisplayForm\" Url=\"DispForm.aspx\" SetupPath=\"pages\\form.aspx\" WebPartZoneID=\"Main\" /><Form Type=\"EditForm\" Url=\"EditForm.aspx\" SetupPath=\"pages\\form.aspx\" WebPartZoneID=\"Main\" /><Form Type=\"NewForm\" Url=\"NewForm.aspx\" SetupPath=\"pages\\form.aspx\" WebPartZoneID=\"Main\" /></Forms></MetaData></List>"}}
Creating list in site at https://watconsdev.sharepoint.com/sites/bfwvendors...
Existing access token eyXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX still valid. Returning...
Request:
{
  "headers": {
    "common": {
      "Accept": "application/json, text/plain, */*"
    },
    "delete": {},
    "get": {},
    "head": {},
    "post": {
      "Content-Type": "application/x-www-form-urlencoded"
    },
    "put": {
      "Content-Type": "application/x-www-form-urlencoded"
    },
    "patch": {
      "Content-Type": "application/x-www-form-urlencoded"
    },
    "user-agent": "NONISV|SharePointPnP|CLIMicrosoft365/4.2.0",
    "accept-encoding": "gzip, deflate",
    "accept": "application/json;odata=nometadata",
    "authorization": "Bearer eyXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
  },
  "decompress": true,
  "responseType": "json",
  "url": "https://watconsdev.sharepoint.com/sites/bfwvendors/_api/web/lists",
  "method": "post",
  "data": {
    "Title": "Announcements",
    "BaseTemplate": 104,
    "SchemaXml": "<List xmlns:ows=\\\"Microsoft SharePoint\" Title=\"List1\" FolderCreation=\"FALSE\" Direction=\"$Resources:Direction;\" Url=\"Lists/List1\" BaseType=\"0\" xmlns=\"http://schemas.microsoft.com/sharepoint/\"><MetaData><ContentTypes><ContentTypeRef ID=\"0x01\"><Folder TargetName=\"Item\" /></ContentTypeRef><ContentTypeRef ID=\"0x0120\" /></ContentTypes><Fields><Field ID=\"{fa564e0f-0c70-4ab9-b863-0177e6ddd247}\" Type=\"Text\" Name=\"Title\" DisplayName=\"$Resources:core,Title;\" Required=\"TRUE\" SourceID=\"http://schemas.microsoft.com/sharepoint/v3\" StaticName=\"Title\" MaxLength=\"255\" /></Fields><Views><View BaseViewID=\"0\" Type=\"HTML\" MobileView=\"TRUE\" TabularView=\"FALSE\"><Toolbar Type=\"Standard\" /><XslLink Default=\"TRUE\">main.xsl</XslLink><RowLimit Paged=\"TRUE\">30</RowLimit><ViewFields><FieldRef Name=\"LinkTitleNoMenu\"></FieldRef></ViewFields><Query><OrderBy><FieldRef Name=\"Modified\" Ascending=\"FALSE\"></FieldRef></OrderBy></Query><ParameterBindings><ParameterBinding Name=\"AddNewAnnouncement\" Location=\"Resource(wss,addnewitem)\" /><ParameterBinding Name=\"NoAnnouncements\" Location=\"Resource(wss,noXinviewofY_LIST)\" /><ParameterBinding Name=\"NoAnnouncementsHowTo\" Location=\"Resource(wss,noXinviewofY_ONET_HOME)\" /></ParameterBindings></View><View BaseViewID=\"1\" Type=\"HTML\" WebPartZoneID=\"Main\" DisplayName=\"$Resources:core,objectiv_schema_mwsidcamlidC24;\" DefaultView=\"TRUE\" MobileView=\"TRUE\" MobileDefaultView=\"TRUE\" SetupPath=\"pages\\\\viewpage.aspx\" ImageUrl=\"/_layouts/15/images/generic.png?rev=23\" Url=\"AllItems.aspx\"><Toolbar Type=\"Standard\" /><XslLink Default=\"TRUE\">main.xsl</XslLink><JSLink>clienttemplates.js</JSLink><RowLimit Paged=\"TRUE\">30</RowLimit><ViewFields><FieldRef Name=\"LinkTitle\"></FieldRef></ViewFields><Query><OrderBy><FieldRef Name=\"ID\"></FieldRef></OrderBy></Query><ParameterBindings><ParameterBinding Name=\"NoAnnouncements\" Location=\"Resource(wss,noXinviewofY_LIST)\" /><ParameterBinding Name=\"NoAnnouncementsHowTo\" Location=\"Resource(wss,noXinviewofY_DEFAULT)\" /></ParameterBindings></View></Views><Forms><Form Type=\"DisplayForm\" Url=\"DispForm.aspx\" SetupPath=\"pages\\form.aspx\" WebPartZoneID=\"Main\" /><Form Type=\"EditForm\" Url=\"EditForm.aspx\" SetupPath=\"pages\\form.aspx\" WebPartZoneID=\"Main\" /><Form Type=\"NewForm\" Url=\"NewForm.aspx\" SetupPath=\"pages\\form.aspx\" WebPartZoneID=\"Main\" /></Forms></MetaData></List>"
  }
}
Request error:
{
  "status": 500,
  "statusText": "Internal Server Error",
  "headers": {
    "cache-control": "private, max-age=0",
    "transfer-encoding": "chunked",
    "content-type": "application/json;odata=nometadata;streaming=true;charset=utf-8",
    "expires": "Tue, 14 Dec 2021 15:53:53 GMT",
    "last-modified": "Wed, 29 Dec 2021 15:53:53 GMT",
    "vary": "Origin",
    "p3p": "CP=\"ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI\"",
    "x-sharepointhealthscore": "1",
    "x-sp-serverstate": "ReadOnly=0",
    "dataserviceversion": "3.0",
    "spclientservicerequestduration": "205",
    "x-aspnet-version": "4.0.30319",
    "sprequestguid": "2a9111a0-b0f8-3000-90b9-ae1a7e4271fa",
    "request-id": "2a9111a0-b0f8-3000-90b9-ae1a7e4271fa",
    "ms-cv": "oBGRKviwADCQua4afkJx+g.0",
    "strict-transport-security": "max-age=31536000",
    "x-frame-options": "SAMEORIGIN",
    "content-security-policy": "frame-ancestors 'self' teams.microsoft.com *.teams.microsoft.com *.skype.com *.teams.microsoft.us local.teams.office.com *.powerapps.com *.yammer.com *.officeapps.live.com *.office.com *.stream.azure-test.net *.microsoftstream.com *.dynamics.com;",
    "x-powered-by": "ASP.NET",
    "microsoftsharepointteamservices": "16.0.0.22001",
    "x-content-type-options": "nosniff",
    "x-ms-invokeapp": "1; RequireReadOnly",
    "x-cache": "CONFIG_NOCACHE",
    "x-msedge-ref": "Ref A: A1AAF8DC9199485AA1ED4C5DF026677F Ref B: LON21EDGE1318 Ref C: 2021-12-29T15:53:53Z",
    "date": "Wed, 29 Dec 2021 15:53:52 GMT",
    "connection": "close"
  },
  "error": {
    "odata.error": {
      "code": "-2130575237, Microsoft.SharePoint.SPException",
      "message": {
        "lang": "en-US",
        "value": "Invalid list template."
      }
    }
  }
}
Error: Invalid list template.

CLI for Microsoft 365 version

v4.2.0

nodejs version

v14.17.0

Operating system (environment)

Windows

Shell

bash

cli doctor

{ "os": { "platform": "linux", "version": "#1 SMP Tue Jun 23 12:58:10 UTC 2020", "release": "4.19.128-microsoft-standard" }, "cliVersion": "4.2.0", "nodeVersion": "v14.17.0", "cliAadAppId": "31359c7f-bd7e-475c-86db-fdb8c937548e", "cliAadAppTenant": "common", "authMode": "DeviceCode", "cliEnvironment": "", "roles": [], "scopes": [ "AllSites.FullControl", "AppCatalog.ReadWrite.All", "ChannelMember.ReadWrite.All", "ChannelMessage.Send", "ChannelSettings.ReadWrite.All", "Directory.AccessAsUser.All", "Directory.ReadWrite.All", "Group.ReadWrite.All", "IdentityProvider.ReadWrite.All", "Mail.ReadWrite", "Mail.Send", "Reports.Read.All", "Tasks.ReadWrite", "Team.Create", "TeamMember.ReadWrite.All", "TeamsApp.ReadWrite.All", "TeamsAppInstallation.ReadWriteForUser", "TeamSettings.ReadWrite.All", "TeamsTab.ReadWrite.All", "TermStore.ReadWrite.All", "User.Invite.All", "User.ReadWrite.All", "profile", "openid", "email", "AllSites.FullControl", "AppCatalog.ReadWrite.All", "ChannelMember.ReadWrite.All", "ChannelMessage.Send", "ChannelSettings.ReadWrite.All", "Directory.AccessAsUser.All", "Directory.ReadWrite.All", "Group.ReadWrite.All", "IdentityProvider.ReadWrite.All", "Mail.ReadWrite", "Mail.Send", "Reports.Read.All", "Tasks.ReadWrite", "Team.Create", "TeamMember.ReadWrite.All", "TeamsApp.ReadWrite.All", "TeamsAppInstallation.ReadWriteForUser", "TeamSettings.ReadWrite.All", "TeamsTab.ReadWrite.All", "TermStore.ReadWrite.All", "User.Invite.All", "User.ReadWrite.All" ] }

Additional Info

No response

The text was updated successfully, but these errors were encountered:

waldekmastykarz · 2021-12-29T18:38:59Z

Hey @danwatford, sorry for the trouble and thank you for taking the time to submit the issue. Let us have a look at it and get back to you as soon as we know more.

danwatford · 2021-12-29T22:22:19Z

I tried using the same schemaXml to create a SP list with pnpjs (code below).
A similar error suggesting there was an error with the list template was given: Invalid list template.

I expect the problem is really down to the content of the schema, but I haven't been successful in constructing any list schemas of my own so was hoping the example would have been a good starting point.

import * as fs from "fs";
import * as path from "path";
import "dotenv/config";
import { SPFetchClient } from "@pnp/nodejs-commonjs";
import { sp } from "@pnp/sp-commonjs";
import "@pnp/odata-commonjs/debug";
import "@pnp/sp-commonjs/webs";
import "@pnp/sp-commonjs/lists";
import validateEnv from "./utils/validateEnv";

validateEnv();

sp.setup({
  sp: {
    fetchClientFactory: () => {
      const fc = new SPFetchClient(
        process.env["SITE_URL"],
        process.env["CLIENT_ID"],
        process.env["CLIENT_SECRET"]
      );

      return {
        fetch: (url, options) => {
          console.log("FETCHING", url, JSON.stringify(options));
          console.log("BODY", options.body);
          return fc.fetch(url, options);
        },
      };
    },
  },
});

async function createList() {
  const schemaBuffer = fs.readFileSync(
    path.join(__dirname, "..", "ApplicationsListSchema.xml")
  );

  try {
    const addListResult = await sp.web.lists.add(
      "DLW Test 1",
      "First attempt at adding list",
      100,
      false,
      {
        SchemaXml: schemaBuffer.toString("utf-8"),
      }
    );

    console.log(addListResult);
  } catch (err) {
    console.error(JSON.stringify(err));
  }
}

createList();

danwatford · 2021-12-30T11:23:05Z

One area to look at might be how double-quotes in the schema xml are being escaped for inclusion in the JSON body of the request sent to spo.

From the output of --debug, notice that only the first double-quote in xmlns:ows="Microsoft SharePoint" is escaped.

"data": {
"Title": "Announcements",
"BaseTemplate": 104,
"SchemaXml": "<List xmlns:ows=\"Microsoft SharePoint" Title="List1" FolderCreation="FALSE" Direction="$Resources:Direction;" Url="Lists/List1" BaseType="0"

danwatford · 2021-12-30T11:35:46Z

Actually, ignore my previous comment, some backslashes were getting dropped in rendering my first post to this issue. Now fixed.

Instead it looks like the first double-quote in the schema xml is getting double escaped (note the 3 backslashes after xmlns:ows):

"SchemaXml": "<List xmlns:ows=\\\"Microsoft SharePoint\" Title=\"List1\"

waldekmastykarz · 2021-12-30T18:38:00Z

@danwatford thank you for the additional information and also comparing the functionality with PnPjs. If you have a List Schema that works with the RAW rest API or any other method (PnPjs, PnP PowerShell, CSOM) then it would be a great starting point for us to check if everything's working as intended.

waldekmastykarz · 2021-12-30T18:53:17Z

FWIW, I can reproduce the issue you mentioned using the sample from our docs. I also tried to use a different list schema and it's failing with the same error as well. If we can reproduce the issue with schemas that we're pretty sure used to work in the past, then it could indicate that something's changed in the SharePoint API that we're using.

danwatford · 2021-12-30T18:57:37Z

@danwatford thank you for the additional information and also comparing the functionality with PnPjs. If you have a List Schema that works with the RAW rest API or any other method (PnPjs, PnP PowerShell, CSOM) then it would be a great starting point for us to check if everything's working as intended.

Hi @waldekmastykarz , unfortunately I haven't been able to get any schemaXml content working for list creation. I haven't got as far as using the raw rest-api yet.

danwatford · 2021-12-30T19:01:27Z

FWIW, I can reproduce the issue you mentioned using the sample from our docs. I also tried to use a different list schema and it's failing with the same error as well. If we can reproduce the issue with schemas that we're pretty sure used to work in the past, then it could indicate that something's changed in the SharePoint API that we're using.

@waldekmastykarz , that's good news (about reproducing the issue).

I did see something in how the schemaXml command line was being processed before making REST request to SPO:

    if (options.schemaXml) {
      requestBody.SchemaXml = options.schemaXml.replace('\\', '\\\\').replace('"', '\\"');
    }

In the calls to the replace methods, only the first occurrence of the pattern will be replaced, hence the differences in escaping of the double quotes in my earlier comments.

To replace all occurrences we need to use regular expressions (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/replace):

replace(/\\/g, '\\\\').replace(/"/g, '\\"')

But I'm not sure what these replacements are trying to achieve and couldn't find any information on how the SPO API expects SchemaXml to be encoded.

waldekmastykarz · 2021-12-31T11:33:27Z

Thank you for the extra information @danwatford. It could be indeed the case that our replacement logic is faulty. If I recall correctly, this used to work as intended and I even used it in the past myself, but it could be that something has changed. Let's try to find a working list schema first, so that we have a reliable sample to test the API and then the CLI with.

appieschot · 2022-02-05T17:25:21Z

Will have a look upcoming days; this might be a bigger problem with our current implementation. I had similar issues when creating new list columns from XML, updating an existing view, and sending adaptive cards.

It might be related to Windows vs Linux as the commands for creating columns seems to be working on Unix. But haven't investigated to much so will spend some time checking a few more commands that work with complex XML before diving into a solution.

waldekmastykarz · 2022-02-05T19:13:28Z

Will have a look upcoming days; this might be a bigger problem with our current implementation.

If this is the issue, then it's coming from the underlying shell that requires a specific sequence for escaping quotes and it's nothing that we could do about. One workaround for such cases is to store the payload in a file and pass the argument from a file using @. That way you don't need to worry about escaping quotes.

appieschot · 2022-05-25T08:13:31Z

So for the list view and list columns all work properly, turns out I just made a typo in escaping a column name resulting in an error. Same for adaptive cards. they are just really complex to get the escaped json correct. Looks like it still goes wrong on schemaXml though.

waldekmastykarz · 2022-05-28T17:47:24Z

Looks like it still goes wrong on schemaXml though.

Even when you pass contents from a file?

waldekmastykarz · 2022-08-29T18:00:39Z

Hey @appieschot, are you still looking into this?

waldekmastykarz · 2022-09-05T17:34:14Z

Resetting as available for picking due to lack of response

MathijsVerbeeck · 2022-12-28T12:26:25Z

I should be able to have a look at this

Jwaegebaert · 2022-12-28T12:43:59Z

Strong work @MathijsVerbeeck!

MathijsVerbeeck · 2023-01-02T17:20:39Z

After doing some research, I've noticed that this is a common issue. I've also had a look at different PnP repositories, and none of these support creating a list by using the SchemaXML option.

I have found one example of a user which will 'parse' the XML from the SchemaXML and will set all the possible list options upon creation. The example can be found below: https://reshmeeauckloo.wordpress.com/2016/10/22/create-lists-libraries-from-schema-as-xml-using-csom/

Also when testing this using CSOM in a simple console application the same error is thrown, even while using the most simple SchemaXML that you can imagine. I have read examples of users for whom this works, but that was on very old environments (SP2010/SP2013), and while using SSOM code. Can't imagine that it has ever worked unfortunately.

Any other thoughts?

waldekmastykarz · 2023-01-02T19:09:53Z

@jansenbe, @patrick-rodgers do you happen to know if it still should be possible to create a SharePoint List from SchemaXml? It seems that all our attempts and samples that we can find are failing. I wonder if anything has changed or if this method shouldn't have been used in the first place. We'd appreciate your help.

patrick-rodgers · 2023-01-03T12:50:55Z

I am not aware that it doesn't work but haven't tried it in many years.

Looking at the source the Create REST method still accepts a custom schemaXML and doesn't appear to have changed. Have you tried with a super basic schemaXML?

waldekmastykarz · 2023-01-03T14:10:45Z

Thanks for your reply, @patrick-rodgers. I think @MathijsVerbeeck tried a basic schema XML. @MathijsVerbeeck, would you mind sharing what you tried here?

MathijsVerbeeck · 2023-01-03T17:44:42Z

I did indeed @waldekmastykarz. I've tried using the following Schema:
<List Title='CustomList' BaseType='0'></List>
Which is the most basic I suppose. I also tried adding the property Type to specify the list template, but that didn't help either.

MathijsVerbeeck · 2023-01-16T12:30:05Z

@waldekmastykarz Any idea on how we continue with this issue? Should we stop supporting the option --schemaXml?

waldekmastykarz · 2023-01-16T18:42:57Z

If we can't get it to work for any case, let's update the docs and mark the option as deprecated, and to be removed in the next major version of the CLI.

waldekmastykarz added bug help wanted labels Dec 29, 2021

appieschot added the needs research label Feb 5, 2022

appieschot self-assigned this Feb 5, 2022

waldekmastykarz added waiting on response and removed help wanted labels Aug 29, 2022

waldekmastykarz unassigned appieschot Sep 5, 2022

waldekmastykarz added help wanted and removed waiting on response labels Sep 5, 2022

Jwaegebaert assigned MathijsVerbeeck Dec 28, 2022

Jwaegebaert added work in progress and removed help wanted labels Dec 28, 2022

This was referenced Jan 17, 2023

Mark option schemaXml as deprecated on spo list add and spo list set #4369

Closed

Remove option schemaXml from spo list add and spo list set #4370

Closed

milanholemans closed this as completed in 271a88f Jan 21, 2023

milanholemans added this to the v6.2 milestone Jan 21, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bug report: Cannot create a new SharePoint list using example command with schemaXml option #2906

Bug report: Cannot create a new SharePoint list using example command with schemaXml option #2906

danwatford commented Dec 29, 2021 •

edited

waldekmastykarz commented Dec 29, 2021

danwatford commented Dec 29, 2021

danwatford commented Dec 30, 2021

danwatford commented Dec 30, 2021

waldekmastykarz commented Dec 30, 2021

waldekmastykarz commented Dec 30, 2021

danwatford commented Dec 30, 2021

danwatford commented Dec 30, 2021 •

edited

waldekmastykarz commented Dec 31, 2021

appieschot commented Feb 5, 2022

waldekmastykarz commented Feb 5, 2022

appieschot commented May 25, 2022

waldekmastykarz commented May 28, 2022

waldekmastykarz commented Aug 29, 2022

waldekmastykarz commented Sep 5, 2022

MathijsVerbeeck commented Dec 28, 2022

Jwaegebaert commented Dec 28, 2022

MathijsVerbeeck commented Jan 2, 2023 •

edited

waldekmastykarz commented Jan 2, 2023

patrick-rodgers commented Jan 3, 2023

waldekmastykarz commented Jan 3, 2023

MathijsVerbeeck commented Jan 3, 2023

MathijsVerbeeck commented Jan 16, 2023

waldekmastykarz commented Jan 16, 2023

Bug report: Cannot create a new SharePoint list using example command with schemaXml option #2906

Bug report: Cannot create a new SharePoint list using example command with schemaXml option #2906

Comments

danwatford commented Dec 29, 2021 • edited

Description

Steps to reproduce

Expected results

Actual results

Diagnostics

CLI for Microsoft 365 version

nodejs version

Operating system (environment)

Shell

cli doctor

Additional Info

waldekmastykarz commented Dec 29, 2021

danwatford commented Dec 29, 2021

danwatford commented Dec 30, 2021

danwatford commented Dec 30, 2021

waldekmastykarz commented Dec 30, 2021

waldekmastykarz commented Dec 30, 2021

danwatford commented Dec 30, 2021

danwatford commented Dec 30, 2021 • edited

waldekmastykarz commented Dec 31, 2021

appieschot commented Feb 5, 2022

waldekmastykarz commented Feb 5, 2022

appieschot commented May 25, 2022

waldekmastykarz commented May 28, 2022

waldekmastykarz commented Aug 29, 2022

waldekmastykarz commented Sep 5, 2022

MathijsVerbeeck commented Dec 28, 2022

Jwaegebaert commented Dec 28, 2022

MathijsVerbeeck commented Jan 2, 2023 • edited

waldekmastykarz commented Jan 2, 2023

patrick-rodgers commented Jan 3, 2023

waldekmastykarz commented Jan 3, 2023

MathijsVerbeeck commented Jan 3, 2023

MathijsVerbeeck commented Jan 16, 2023

waldekmastykarz commented Jan 16, 2023

danwatford commented Dec 29, 2021 •

edited

danwatford commented Dec 30, 2021 •

edited

MathijsVerbeeck commented Jan 2, 2023 •

edited