<?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: sas DI warning in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/sas-DI-warning/m-p/550455#M16889</link>
    <description>&lt;P&gt;Looks like something doesn't "stick" in SAS Metadata. You will need to inspect the generated code to decide if this warning also impacts on code generation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I personally wouldn't feel comfortable to not fix such a warning.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What sometimes helps is a Metadata analyze/repair (run out of SMC).&lt;/P&gt;
&lt;P&gt;Another option which worked for me sometimes in the past:&lt;/P&gt;
&lt;P&gt;1. Fix the mapping issue&lt;/P&gt;
&lt;P&gt;2. Save and then export the job (just the job without dependent objects)&lt;/P&gt;
&lt;P&gt;3. Rename the job in DIS&lt;/P&gt;
&lt;P&gt;4. Import the .spk&lt;/P&gt;
&lt;P&gt;5. Open the "new" job&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; - If you're lucky then the mapping warning is gone. Else fix it once more and test if it sticks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If nothing from above helps: If the join is not too complicated then I'd eventually rebuild the whole join starting with a new SQL Join transformation - but looking at how many input tables you've got I believe that's may be not an path you want to take.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I believe what also could work - but that's only to avoid the warning - is to add the list of source columns as comment to the expression. So you just add something at the end like /* col1 col2 ....*/&amp;nbsp; ....not to be used if your source tables are in Oracle and the like and you've instructed SAS to pass hints to the database.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 11 Apr 2019 22:35:56 GMT</pubDate>
    <dc:creator>Patrick</dc:creator>
    <dc:date>2019-04-11T22:35:56Z</dc:date>
    <item>
      <title>sas DI warning</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/sas-DI-warning/m-p/550330#M16885</link>
      <description>&lt;P&gt;I have a quirk that I’ve found in DI Studio and I was wondering if you could offer me any explanation for it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a join that is showing the warning ‘mapped source columns do not match columns used in expression’ (as seen below). When I fix the issue by correctly mapping the columns, the warning goes away, but if I save and close the job, then re-open it, the warning reappears.&lt;/P&gt;&lt;P&gt;I would like to know if the warning will cause any issues once I deploy and run the job on a scheduler.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Capture.PNG" style="width: 400px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/28653iB2A37D4082DDCA99/image-size/large?v=v2&amp;amp;px=999" role="button" title="Capture.PNG" alt="Capture.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2019 16:47:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/sas-DI-warning/m-p/550330#M16885</guid>
      <dc:creator>sathya66</dc:creator>
      <dc:date>2019-04-11T16:47:33Z</dc:date>
    </item>
    <item>
      <title>Re: sas DI warning</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/sas-DI-warning/m-p/550455#M16889</link>
      <description>&lt;P&gt;Looks like something doesn't "stick" in SAS Metadata. You will need to inspect the generated code to decide if this warning also impacts on code generation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I personally wouldn't feel comfortable to not fix such a warning.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What sometimes helps is a Metadata analyze/repair (run out of SMC).&lt;/P&gt;
&lt;P&gt;Another option which worked for me sometimes in the past:&lt;/P&gt;
&lt;P&gt;1. Fix the mapping issue&lt;/P&gt;
&lt;P&gt;2. Save and then export the job (just the job without dependent objects)&lt;/P&gt;
&lt;P&gt;3. Rename the job in DIS&lt;/P&gt;
&lt;P&gt;4. Import the .spk&lt;/P&gt;
&lt;P&gt;5. Open the "new" job&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; - If you're lucky then the mapping warning is gone. Else fix it once more and test if it sticks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If nothing from above helps: If the join is not too complicated then I'd eventually rebuild the whole join starting with a new SQL Join transformation - but looking at how many input tables you've got I believe that's may be not an path you want to take.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I believe what also could work - but that's only to avoid the warning - is to add the list of source columns as comment to the expression. So you just add something at the end like /* col1 col2 ....*/&amp;nbsp; ....not to be used if your source tables are in Oracle and the like and you've instructed SAS to pass hints to the database.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2019 22:35:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/sas-DI-warning/m-p/550455#M16889</guid>
      <dc:creator>Patrick</dc:creator>
      <dc:date>2019-04-11T22:35:56Z</dc:date>
    </item>
  </channel>
</rss>

