<?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: Can we exclude the defalut code generated while export a processflow? in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/640994#M35887</link>
    <description>&lt;P&gt;Are you talking about the macro definitions in your photograph?&lt;/P&gt;</description>
    <pubDate>Sat, 18 Apr 2020 19:54:08 GMT</pubDate>
    <dc:creator>Tom</dc:creator>
    <dc:date>2020-04-18T19:54:08Z</dc:date>
    <item>
      <title>Can we exclude the defalut code generated while export a processflow?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/640942#M35882</link>
      <description>&lt;P&gt;Hello all -&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am seeing some default code getting generated while I am exporting the processflow into a SAS single program in SAS Enterprise guide 8.2, Is there any way to exclude the default code so that I can see only the code related to my process flow.&lt;/P&gt;&lt;P&gt;Any help is appreciated..,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Thalla&lt;/P&gt;</description>
      <pubDate>Sat, 18 Apr 2020 12:06:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/640942#M35882</guid>
      <dc:creator>THALLA_REDDY</dc:creator>
      <dc:date>2020-04-18T12:06:19Z</dc:date>
    </item>
    <item>
      <title>Re: Can we exclude the defalut code generated while export a processflow?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/640945#M35885</link>
      <description>&lt;P&gt;As soon as the window for "Export all Project Code" opens, you have an option to exclude wrapper code.&lt;/P&gt;</description>
      <pubDate>Sat, 18 Apr 2020 12:43:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/640945#M35885</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2020-04-18T12:43:55Z</dc:date>
    </item>
    <item>
      <title>Re: Can we exclude the defalut code generated while export a processflow?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/640985#M35886</link>
      <description>&lt;P&gt;thanks for your reply, I tried the same thing that you have mentioned but still I can see lot of line in my exported code. Actually i am using a query builder and a LIST data task in my process flow, So the actual code for these two objects is about 50 lines but after excluding the options in the EXPORT window still I am seeing around 320 lines of code generated when I exported the project. So any other options available for me to exclude the code auto generated when exporting my project?&lt;/P&gt;</description>
      <pubDate>Sat, 18 Apr 2020 18:07:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/640985#M35886</guid>
      <dc:creator>THALLA_REDDY</dc:creator>
      <dc:date>2020-04-18T18:07:24Z</dc:date>
    </item>
    <item>
      <title>Re: Can we exclude the defalut code generated while export a processflow?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/640994#M35887</link>
      <description>&lt;P&gt;Are you talking about the macro definitions in your photograph?&lt;/P&gt;</description>
      <pubDate>Sat, 18 Apr 2020 19:54:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/640994#M35887</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2020-04-18T19:54:08Z</dc:date>
    </item>
    <item>
      <title>Re: Can we exclude the defalut code generated while export a processflow?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/640999#M35888</link>
      <description>Yeah, most of them are the macro definition lines.</description>
      <pubDate>Sat, 18 Apr 2020 21:01:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/640999#M35888</guid>
      <dc:creator>THALLA_REDDY</dc:creator>
      <dc:date>2020-04-18T21:01:07Z</dc:date>
    </item>
    <item>
      <title>Re: Can we exclude the defalut code generated while export a processflow?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/641008#M35889</link>
      <description>&lt;P&gt;The %eg_conditional_dropds is a macro frequently used in code created by EG tasks. It is normally sent from EG to the workspace server when a connection is established, and necessary for EG-created code to work. Therefore you must keep it in the exported code.&lt;/P&gt;</description>
      <pubDate>Sat, 18 Apr 2020 22:23:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Can-we-exclude-the-defalut-code-generated-while-export-a/m-p/641008#M35889</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2020-04-18T22:23:06Z</dc:date>
    </item>
  </channel>
</rss>

