<?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: importing xlsx files with difficult names in Microsoft Integration with SAS</title>
    <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189095#M1589</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is important that I know which data column corresponds to which variable since the analysis that I need to run is unique for each column. If I use a standardized naming scale at the import level I am concerned that if the order of the columns changes in the excel spreadsheet (the next time I download the sheet from our data provider) it will not be noticed causing misleading results. This is why I suspect I need the variable names to be imported as valid sas variable names, but unique names that will not depend on ordering of columns.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 Apr 2014 14:12:55 GMT</pubDate>
    <dc:creator>JohnDooley</dc:creator>
    <dc:date>2014-04-22T14:12:55Z</dc:date>
    <item>
      <title>importing xlsx files with difficult names</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189093#M1587</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to import an xlsx file. Unfortunately the variable names will contain special characters and blanks (there are &lt;STRONG&gt;many&lt;/STRONG&gt; such columns). The data is being downloaded from a third party provider to this xlsx sheet and I have no control over their naming convention. Furthermore, we will want to periodically update this spreadsheet (possibly adding more variables and switching the order of columns) and rerun the import statement for analysis purposes. Because of these concerns it would not be practical to hard code the names of each variable upon import.&lt;/P&gt;&lt;P&gt;I would like to strip out all of the special characters and spaces upon import (or replace them with underscores). This used to be feasible with the GETNAMES option for xls files but I do not believe that it is supported for xlsx file types (we need the xlsx file type because there is to much data for an xls).&lt;/P&gt;&lt;P&gt;Does anyone have any thoughts about how to rename these variables upon import (without changing the excel file)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Apr 2014 13:29:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189093#M1587</guid>
      <dc:creator>JohnDooley</dc:creator>
      <dc:date>2014-04-22T13:29:20Z</dc:date>
    </item>
    <item>
      <title>Re: importing xlsx files with difficult names</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189094#M1588</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bypass the column names row and use your own naming&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Apr 2014 13:54:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189094#M1588</guid>
      <dc:creator>jakarman</dc:creator>
      <dc:date>2014-04-22T13:54:54Z</dc:date>
    </item>
    <item>
      <title>Re: importing xlsx files with difficult names</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189095#M1589</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is important that I know which data column corresponds to which variable since the analysis that I need to run is unique for each column. If I use a standardized naming scale at the import level I am concerned that if the order of the columns changes in the excel spreadsheet (the next time I download the sheet from our data provider) it will not be noticed causing misleading results. This is why I suspect I need the variable names to be imported as valid sas variable names, but unique names that will not depend on ordering of columns.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Apr 2014 14:12:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189095#M1589</guid>
      <dc:creator>JohnDooley</dc:creator>
      <dc:date>2014-04-22T14:12:55Z</dc:date>
    </item>
    <item>
      <title>Re: importing xlsx files with difficult names</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189096#M1590</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Than do it in two steps....&lt;BR /&gt;At first just reading the column headers.&amp;nbsp; Do not forget options like validvarname=V7 obs=&amp;nbsp; &lt;/P&gt;&lt;P&gt;Do your inputvalidation on that dataset checking the unique=-names, after input-validation is passing than process further.&lt;/P&gt;&lt;P&gt;Remembering the rootcause of heart-bleed. The coder did not check/validate the incoming request. Just forgot it.&lt;/P&gt;&lt;P&gt;Fool/full-proof coding is hard work. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Apr 2014 14:41:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189096#M1590</guid>
      <dc:creator>jakarman</dc:creator>
      <dc:date>2014-04-22T14:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: importing xlsx files with difficult names</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189097#M1591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SAS will generally do this by default, assuming you don't have the option validvarname=any set.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Apr 2014 14:51:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189097#M1591</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2014-04-22T14:51:11Z</dc:date>
    </item>
    <item>
      <title>Re: importing xlsx files with difficult names</title>
      <link>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189098#M1592</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your help. The option validvarname=v7 worked very nicely and I will be sure to validate the names.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Apr 2014 15:25:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Microsoft-Integration-with-SAS/importing-xlsx-files-with-difficult-names/m-p/189098#M1592</guid>
      <dc:creator>JohnDooley</dc:creator>
      <dc:date>2014-04-22T15:25:30Z</dc:date>
    </item>
  </channel>
</rss>

