<?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: save import code from from the 'SAS Data Explorer-Manage Data' in SAS Studio</title>
    <link>https://communities.sas.com/t5/SAS-Studio/save-import-code-from-from-the-SAS-Data-Explorer-Manage-Data/m-p/668641#M9260</link>
    <description>&lt;P&gt;Unfortunately, there is not.&amp;nbsp; If you are doing a local file import then the "code" is actually a set of REST calls to the SAS Viya microservices.&amp;nbsp; The most important of these is a POST to the CAS Management service to stream the data to the CAS server to have the table created.&amp;nbsp; Internally CAS Management is using the CAS Java client to invoke a table.upload CAS action.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you are importing an unloaded table from a caslib, then the code for performing the import is contained in the corresponding Job Definition used to run the Import job.&amp;nbsp; All of these job definitions are running CASL code, and they should be publicly viewable using the Job Definitions service REST API to retrieve them.&amp;nbsp; The returned definition will have a "code" member that contains the parameterized CASL code block that it uses.&lt;/P&gt;</description>
    <pubDate>Sun, 12 Jul 2020 14:55:17 GMT</pubDate>
    <dc:creator>BenRyan</dc:creator>
    <dc:date>2020-07-12T14:55:17Z</dc:date>
    <item>
      <title>save import code from from the 'SAS Data Explorer-Manage Data'</title>
      <link>https://communities.sas.com/t5/SAS-Studio/save-import-code-from-from-the-SAS-Data-Explorer-Manage-Data/m-p/668500#M9259</link>
      <description>&lt;P&gt;When you import data through the Manage Data visual interface, is there a way to save the code (similar to how we could save the code in the 9.4 import wizard)?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I need this because my attempts to import with code don't work but importing through the interface does work.&amp;nbsp; This would help me know what I am doing wrong. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jul 2020 23:55:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/save-import-code-from-from-the-SAS-Data-Explorer-Manage-Data/m-p/668500#M9259</guid>
      <dc:creator>telligent</dc:creator>
      <dc:date>2020-07-10T23:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: save import code from from the 'SAS Data Explorer-Manage Data'</title>
      <link>https://communities.sas.com/t5/SAS-Studio/save-import-code-from-from-the-SAS-Data-Explorer-Manage-Data/m-p/668641#M9260</link>
      <description>&lt;P&gt;Unfortunately, there is not.&amp;nbsp; If you are doing a local file import then the "code" is actually a set of REST calls to the SAS Viya microservices.&amp;nbsp; The most important of these is a POST to the CAS Management service to stream the data to the CAS server to have the table created.&amp;nbsp; Internally CAS Management is using the CAS Java client to invoke a table.upload CAS action.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you are importing an unloaded table from a caslib, then the code for performing the import is contained in the corresponding Job Definition used to run the Import job.&amp;nbsp; All of these job definitions are running CASL code, and they should be publicly viewable using the Job Definitions service REST API to retrieve them.&amp;nbsp; The returned definition will have a "code" member that contains the parameterized CASL code block that it uses.&lt;/P&gt;</description>
      <pubDate>Sun, 12 Jul 2020 14:55:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/save-import-code-from-from-the-SAS-Data-Explorer-Manage-Data/m-p/668641#M9260</guid>
      <dc:creator>BenRyan</dc:creator>
      <dc:date>2020-07-12T14:55:17Z</dc:date>
    </item>
  </channel>
</rss>

