<?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: Changing CSV file header in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Changing-CSV-file-header/m-p/598762#M104425</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/172955"&gt;@jwhughes58&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;you solution should work.&lt;/P&gt;&lt;P&gt;but anyway, there's also the approach that's used in normalization: create a set of aliases in yout App or TA, (not in a single search) that could be useful also wgen there are other fields named in those ways to rename.&lt;/P&gt;&lt;P&gt;I always normalize my field names in extraction for using also in other apps.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 21 May 2022 09:06:50 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2022-05-21T09:06:50Z</dc:date>
    <item>
      <title>Changing CSV file header</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Changing-CSV-file-header/m-p/598724#M104422</link>
      <description>&lt;P&gt;I'm working with a csv file with this header&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Filenm,EIN,Status,Business Function,Maintained By, Region,Manufacturer Name,Building Name,Service Area,Model Name,Model Number,Serial Number,AM Tag Number,Equipment Type,Equipment Type Description,Network Connection Type Wired,IP Address v4 Wired,Nuvolo Flag,MAC Address Wired,Equipment Status Detail,Network Connection Type Wireless,IP Address v4 Wireless,IP Address Type Wireless,IP Address Type Wired,MAC Address Wireless,Host Name,Fully Qualified Domain Name,OS Version,Asset Type,Contains ePHI,Application Software Name&lt;/LI-CODE&gt;&lt;P&gt;What I would like to do is have Splunk transform to closer to Splunk field names.&amp;nbsp; Such as&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;filenm,ein,status,business_function,maintained_by,region,manufacturer_name,building_name,service_area,model_name,model_number,serial_number,am_tag_mumber,equipment_type,equipment_type_description,network_connection_type_wired,ip_addres_v4_Wired,nuvolo_flag,mac_address_wired,equipment_status_detail,network_connection_type_wireless,ip_Address_v4_wireless,ip_address_type_wireless,ip_ddress_type_wired,mac_address_wireless,host_name,fully_qualified_domain_name,os_version,asset_type,contains_ephi,application_software_name&lt;/LI-CODE&gt;&lt;P&gt;The only thing I've been able to find is putting something in the TA transforms.conf like this&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[edge_asset_header]
DELIMS = ","
FIELDS = "filenm","ein","status","business_function","maintained_by","region","manufacturer_name","building_name","service_area","model_name","model_number","serial_number","am_tag_mumber","equipment_type","equipment_type_description","network_connection_type_wired","ip_addres_v4_Wired","nuvolo_flag","mac_address_wired","equipment_status_detail","network_connection_type_wireless","ip_Address_v4_wireless","ip_address_type_wireless","ip_ddress_type_wired","mac_address_wireless","host_name","fully_qualified_domain_name","os_version","asset_type","contains_ephi","application_software_name"&lt;/LI-CODE&gt;&lt;P&gt;Is the only solution or did I miss something?&lt;/P&gt;&lt;P&gt;TIA,&lt;/P&gt;&lt;P&gt;Joe&lt;/P&gt;</description>
      <pubDate>Fri, 20 May 2022 19:48:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Changing-CSV-file-header/m-p/598724#M104422</guid>
      <dc:creator>jwhughes58</dc:creator>
      <dc:date>2022-05-20T19:48:49Z</dc:date>
    </item>
    <item>
      <title>Re: Changing CSV file header</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Changing-CSV-file-header/m-p/598762#M104425</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/172955"&gt;@jwhughes58&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;you solution should work.&lt;/P&gt;&lt;P&gt;but anyway, there's also the approach that's used in normalization: create a set of aliases in yout App or TA, (not in a single search) that could be useful also wgen there are other fields named in those ways to rename.&lt;/P&gt;&lt;P&gt;I always normalize my field names in extraction for using also in other apps.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 21 May 2022 09:06:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Changing-CSV-file-header/m-p/598762#M104425</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-05-21T09:06:50Z</dc:date>
    </item>
  </channel>
</rss>

