<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: xml mapper in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/xml-mapper/m-p/592131#M34768</link>
    <description>&lt;P&gt;XML Mapper (and XML engine) works fine in EG.&amp;nbsp; I think the issue might be that the O: drive isn't visible to your SAS server.&amp;nbsp; If that's a drive you have mapped on your PC, you might need to express the file path as a UNC path (as you did with the XML data source) or copy the XML map file to a location on your server.&amp;nbsp; (You can manage that with the Copy Files task in EG.)&lt;/P&gt;</description>
    <pubDate>Fri, 27 Sep 2019 11:36:16 GMT</pubDate>
    <dc:creator>ChrisHemedinger</dc:creator>
    <dc:date>2019-09-27T11:36:16Z</dc:date>
    <item>
      <title>xml mapper</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/xml-mapper/m-p/592127#M34767</link>
      <description>&lt;P&gt;Hi is the sas xml mapper&amp;nbsp; XMLv2 compatable with EG 7 version ,we are trying to import an xml document and its not reading the xmle map file created&amp;nbsp; by the mapper&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;libname NHL&amp;nbsp;&amp;nbsp; '\\jdgsasappsvr\CVM\BI and BA Reporting\RTDM Testing\Map test';&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;filename MAP 'O:\CVM\BI and BA Reporting\RTDM Testing\Map test\map.map';&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;libname NHL xml xmlmap=MAP;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;libname NHL xml&amp;nbsp; xmlmap=MAP;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;proc&lt;/STRONG&gt; &lt;STRONG&gt;print&lt;/STRONG&gt; data=NHL.Request_map;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;run&lt;/STRONG&gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;23&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; GOPTIONS ACCESSIBLE;&lt;/P&gt;&lt;P&gt;24&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; libname NHL xml&amp;nbsp; xmlmap=MAP;&lt;/P&gt;&lt;P&gt;NOTE: Libref NHL was successfully assigned as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Engine:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; XML&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Physical Name: NHL&lt;/P&gt;&lt;P&gt;25&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;26&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; proc print data=NHL.Request_map;&lt;/P&gt;&lt;P&gt;ERROR: Physical file does not exist, O:\CVM\BI and BA Reporting\RTDM Testing\Map test\map.map.&lt;/P&gt;&lt;P&gt;ERROR: Encountered during XMLMap parsing at or near line 1, column 1.&lt;/P&gt;&lt;P&gt;ERROR: XML describe error: Internal processing error.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Sep 2019 11:15:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/xml-mapper/m-p/592127#M34767</guid>
      <dc:creator>Chammag_</dc:creator>
      <dc:date>2019-09-27T11:15:22Z</dc:date>
    </item>
    <item>
      <title>Re: xml mapper</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/xml-mapper/m-p/592131#M34768</link>
      <description>&lt;P&gt;XML Mapper (and XML engine) works fine in EG.&amp;nbsp; I think the issue might be that the O: drive isn't visible to your SAS server.&amp;nbsp; If that's a drive you have mapped on your PC, you might need to express the file path as a UNC path (as you did with the XML data source) or copy the XML map file to a location on your server.&amp;nbsp; (You can manage that with the Copy Files task in EG.)&lt;/P&gt;</description>
      <pubDate>Fri, 27 Sep 2019 11:36:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/xml-mapper/m-p/592131#M34768</guid>
      <dc:creator>ChrisHemedinger</dc:creator>
      <dc:date>2019-09-27T11:36:16Z</dc:date>
    </item>
    <item>
      <title>Re: xml mapper</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/xml-mapper/m-p/592132#M34769</link>
      <description>&lt;P&gt;Thank you, will try this&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Sep 2019 11:38:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/xml-mapper/m-p/592132#M34769</guid>
      <dc:creator>Chammag_</dc:creator>
      <dc:date>2019-09-27T11:38:32Z</dc:date>
    </item>
    <item>
      <title>Re: xml mapper</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/xml-mapper/m-p/592135#M34771</link>
      <description>&lt;P&gt;is it compatible with SAS EG 7.1, this is the version we are using.&lt;/P&gt;&lt;P&gt;And, O drive is the sas server&lt;/P&gt;</description>
      <pubDate>Fri, 27 Sep 2019 11:43:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/xml-mapper/m-p/592135#M34771</guid>
      <dc:creator>Chammag_</dc:creator>
      <dc:date>2019-09-27T11:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: xml mapper</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/xml-mapper/m-p/592137#M34773</link>
      <description>&lt;P&gt;Hey, I'm not by any means an expert on reading XML, but I did look at the doc:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://go.documentation.sas.com/?cdcId=pgmsascdc&amp;amp;cdcVersion=9.4_3.4&amp;amp;docsetId=engxml&amp;amp;docsetTarget=p0b4dnu019ycsxn11k3savd51h6k.htm" target="_blank"&gt;https://go.documentation.sas.com/?cdcId=pgmsascdc&amp;amp;cdcVersion=9.4_3.4&amp;amp;docsetId=engxml&amp;amp;docsetTarget=p0b4dnu019ycsxn11k3savd51h6k.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The example has two filename statements, one to the xml file and one to the map. Looks like your first libname statement needs to be replaced with a&amp;nbsp; filename statement that identifies the xml file.&amp;nbsp; Also, try the xmlv2 engine in the libname statement.&lt;/P&gt;
&lt;P&gt;I ran this example from the doc successfully using EG 7.13. Hope this helps.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV id="app" class="app h-full ng-scope" aria-hidden="false"&gt;
&lt;DIV class="app-wrapper ng-scope"&gt;
&lt;DIV id="app-bottom-wrapper" class="app-b-wrapper"&gt;
&lt;DIV id="document-panel" class="pos-r h-full" aria-hidden="false"&gt;
&lt;DIV class="overflow-h ng-scope"&gt;
&lt;DIV id="document" class="document scrollable ng-scope" role="main"&gt;
&lt;DIV id="pageContent" class="document-body wrapper" lang="en" tabindex="0" aria-live="polite"&gt;
&lt;DIV class="xis-eDocBody ng-scope"&gt;
&lt;DIV id="p0b4dnu019ycsxn11k3savd51h6k" class="xis-topic"&gt;
&lt;DIV id="n0jxyxb2k61sesn0zwivchgru1m5" class="xis-topicContent"&gt;
&lt;DIV id="p1uf271755sepbn183qbpni9yaka" class="xis-codeBlock"&gt;
&lt;PRE class="xis-code"&gt;filename nhl 'C:\Example\Nhl.xml'; /*&lt;SPAN class="xis-calloutAnchor"&gt;1&lt;/SPAN&gt;*/
filename map 'C:\Example\Nhl.map'; /*&lt;SPAN class="xis-calloutAnchor"&gt;2&lt;/SPAN&gt;*/

libname nhl xmlv2 xmlmap=map; /*&lt;SPAN class="xis-calloutAnchor"&gt;3&lt;/SPAN&gt;*/

proc print data=nhl.teams; /*&lt;SPAN class="xis-calloutAnchor"&gt;4&lt;/SPAN&gt;*/
run;&lt;BR /&gt;&lt;BR /&gt;&lt;/PRE&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 27 Sep 2019 11:44:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/xml-mapper/m-p/592137#M34773</guid>
      <dc:creator>elizD</dc:creator>
      <dc:date>2019-09-27T11:44:43Z</dc:date>
    </item>
  </channel>
</rss>

