<?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: why SAS PROC IMPORT twisted the values in EXCEL 2013 file? in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/why-SAS-PROC-IMPORT-twisted-the-values-in-EXCEL-2013-file/m-p/416985#M26844</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/159891"&gt;@fankaiqing&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a known issue with the XLSX engine, reported to R&amp;amp;D.&lt;/P&gt;
&lt;P&gt;If you can't use&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13879"&gt;@Reeza&lt;/a&gt;&amp;nbsp;'s solution for now, a couple of other workarounds are:&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - Use the EXCELCS engine. You may have to &lt;A href="http://go.documentation.sas.com/?docsetId=pcfsicg&amp;amp;docsetTarget=n1qhkerbd4k9qun1oome59qr7f5y.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=fr" target="_self"&gt;install SAS PC Files Server&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - Use the XLS engine (after you save your file to&amp;nbsp;&lt;EM&gt;LOBOR_Map_samples.xls&lt;/EM&gt;).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope that helps.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;BR /&gt;Damo&lt;/P&gt;</description>
    <pubDate>Wed, 29 Nov 2017 08:32:40 GMT</pubDate>
    <dc:creator>Damo</dc:creator>
    <dc:date>2017-11-29T08:32:40Z</dc:date>
    <item>
      <title>why SAS PROC IMPORT twisted the values in EXCEL 2013 file?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/why-SAS-PROC-IMPORT-twisted-the-values-in-EXCEL-2013-file/m-p/416866#M26834</link>
      <description>&lt;P&gt;why SAS PROC IMPORT twisted the values in EXCEL 2013 file?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have EXCEL 2013 file with values such as C&amp;amp;IB, but after reading my PROC IMPORT, the results are C&amp;amp;amp;IB.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Changed From&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; C&amp;amp;IB &amp;nbsp;&amp;nbsp; to&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;C&amp;amp;amp;IB&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here is the code;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;&lt;FONT color="#000080" face="Courier New"&gt;&lt;STRONG&gt;proc&lt;/STRONG&gt;&lt;/FONT&gt; &lt;STRONG&gt;&lt;FONT color="#000080" face="Courier New"&gt;import&lt;/FONT&gt;&lt;/STRONG&gt; &lt;FONT color="#0000ff" face="Courier New"&gt;datafile&lt;/FONT&gt;&lt;FONT face="Courier New"&gt;=&lt;/FONT&gt;&lt;FONT color="#800080" face="Courier New"&gt;"&amp;amp;Maps./LOBOR_Map_samples.xlsx"&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;&lt;FONT color="#0000ff" face="Courier New"&gt;out&lt;/FONT&gt;&lt;FONT face="Courier New"&gt;=map&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;&lt;FONT color="#0000ff" face="Courier New"&gt;dbms&lt;/FONT&gt;&lt;FONT face="Courier New"&gt;=xlsx &lt;/FONT&gt;&lt;FONT color="#0000ff" face="Courier New"&gt;replace&lt;/FONT&gt;&lt;FONT face="Courier New"&gt;; &lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;&lt;FONT color="#0000ff" face="Courier New"&gt;getnames&lt;/FONT&gt;&lt;FONT face="Courier New"&gt;=YES;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;&lt;FONT color="#000080" face="Courier New"&gt;&lt;STRONG&gt;run&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT face="Courier New"&gt;;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;FONT face="Courier New" size="3"&gt;Who knows what is wrong?&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;FONT face="Courier New" size="3"&gt;Thanks a lot!&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2017 20:38:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/why-SAS-PROC-IMPORT-twisted-the-values-in-EXCEL-2013-file/m-p/416866#M26834</guid>
      <dc:creator>fankaiqing</dc:creator>
      <dc:date>2017-11-28T20:38:46Z</dc:date>
    </item>
    <item>
      <title>Re: why SAS PROC IMPORT twisted the values in EXCEL 2013 file?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/why-SAS-PROC-IMPORT-twisted-the-values-in-EXCEL-2013-file/m-p/416879#M26836</link>
      <description>I don’t know why it happens, but you can use HTMLDECODE to correct the variables in question. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Nov 2017 21:00:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/why-SAS-PROC-IMPORT-twisted-the-values-in-EXCEL-2013-file/m-p/416879#M26836</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2017-11-28T21:00:20Z</dc:date>
    </item>
    <item>
      <title>Re: why SAS PROC IMPORT twisted the values in EXCEL 2013 file?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/why-SAS-PROC-IMPORT-twisted-the-values-in-EXCEL-2013-file/m-p/416985#M26844</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/159891"&gt;@fankaiqing&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a known issue with the XLSX engine, reported to R&amp;amp;D.&lt;/P&gt;
&lt;P&gt;If you can't use&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13879"&gt;@Reeza&lt;/a&gt;&amp;nbsp;'s solution for now, a couple of other workarounds are:&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - Use the EXCELCS engine. You may have to &lt;A href="http://go.documentation.sas.com/?docsetId=pcfsicg&amp;amp;docsetTarget=n1qhkerbd4k9qun1oome59qr7f5y.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=fr" target="_self"&gt;install SAS PC Files Server&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - Use the XLS engine (after you save your file to&amp;nbsp;&lt;EM&gt;LOBOR_Map_samples.xls&lt;/EM&gt;).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope that helps.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;BR /&gt;Damo&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2017 08:32:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/why-SAS-PROC-IMPORT-twisted-the-values-in-EXCEL-2013-file/m-p/416985#M26844</guid>
      <dc:creator>Damo</dc:creator>
      <dc:date>2017-11-29T08:32:40Z</dc:date>
    </item>
    <item>
      <title>Re: why SAS PROC IMPORT twisted the values in EXCEL 2013 file?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/why-SAS-PROC-IMPORT-twisted-the-values-in-EXCEL-2013-file/m-p/416986#M26845</link>
      <description>&lt;P&gt;Open the .xlsx file with a ZIP program, and navigate to the \xl\worksheets folder within the file. Open sheet1.xml with a text editor.&lt;/P&gt;
&lt;P&gt;When you scroll far enough to the right of the second line, you'll find that your values are stored like that (HTML encoding) by Excel; it seems that proc import gives you that string.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you did the sensible thing and stored your table to a .csv file, and imported that, you would not have the problem.&lt;/P&gt;
&lt;P&gt;For the umpteenth time: DO NOT USE EXCEL FILES FOR DATA TRANSFER!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BTW: your Excel file is 18K in size, the .csv created from that is just 1K. I rest my case.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2017 08:43:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/why-SAS-PROC-IMPORT-twisted-the-values-in-EXCEL-2013-file/m-p/416986#M26845</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-11-29T08:43:56Z</dc:date>
    </item>
    <item>
      <title>Re: why SAS PROC IMPORT twisted the values in EXCEL 2013 file?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/why-SAS-PROC-IMPORT-twisted-the-values-in-EXCEL-2013-file/m-p/418190#M26925</link>
      <description>Yes.&lt;BR /&gt;&lt;BR /&gt;When I open the xlsx file, the value in the second column is with a formula relationship with the first column, For example, when you click the 3rd row cell of the second column, that is, B3 , the cell B3 will not show its value but "=A3". It means that this cell has relationship with the first column.&lt;BR /&gt;&lt;BR /&gt;The solution is that we copy all its values in this xlsx file into another one to discard the formula, keep original values as text.&lt;BR /&gt;&lt;BR /&gt;Thanks so much!</description>
      <pubDate>Mon, 04 Dec 2017 15:32:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/why-SAS-PROC-IMPORT-twisted-the-values-in-EXCEL-2013-file/m-p/418190#M26925</guid>
      <dc:creator>fankaiqing</dc:creator>
      <dc:date>2017-12-04T15:32:30Z</dc:date>
    </item>
  </channel>
</rss>

