3 Replies Latest reply on May 29, 2014 10:59 AM by Ramesh Reddy

    Sharepoint list xml, No columns defined error

    lightsail pro Newbie

      I am trying to import a local xml file (see below) from a SharePoint 2010 list. When I select a node  (m:property) as root, I got the "No columns defined error". It does not allow me to add d:name. Does anyone know what this means and if there is any workaround? I am not familiar with xml. It seems m: and d: means name space. Thanks


      <?xml version="1.0" encoding="utf-8" standalone="yes"?>
      <feed xml:base="https://intranet.hq.overdrive.com/_vti_bin/listdata.svc/"


      xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns="http://www.w3.org/2005/Atom">

          <content type="application/xml">


      Import From XML File Source_sharepoint list.png

        • 1. Re: Sharepoint list xml, No columns defined error
          Ramesh Reddy Master

          I have seen that error too while working on demo couple weeks back, I failed to capture the steps then. I can not seem to recreate it with JBDS 7.1.1.GA + Designer 8.3.2 or latest Designer with your XML now. Can you go over the steps exactly that can recreate issue? Also which version of Windows and JDK you are running under?

          • 2. Re: Sharepoint list xml, No columns defined error
            Barry LaFond Master

            This importer is designed to help construct a viable SQL statement containing an XMLTABLE() function call that will return relational table data. The requirement is that at least ONE column must be defined/mapped to an XML/schema element.  The validation kicks in once you start editing, so setting the ROOT will end up with an ERROR since no columns are defined.


            Simple double click one or more elements (i.e. d:Photo, d:Name, d:Title, etc...) will create corresponding Column entries and they will show up in the Generated SQL Statement.

            • 3. Re: Sharepoint list xml, No columns defined error
              Ramesh Reddy Master

              Barry, what I encountered was, the XML was there but, you could not select element, or right click on the element root to set as root. I know this does not happen all the time, but in certain scenario it does happen. Next time I am sure to capture the details