<?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 Profiling on dynamic data source in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/Profiling-on-dynamic-data-source/m-p/483692#M15085</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are trying to run&amp;nbsp;the profiling process we have build and an&amp;nbsp;error occurred regarding a field that has been retired from the source. Before this change the&amp;nbsp;profiling process was completed successfully as expected.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please note that our data source is a view table. Thus, changes are expected in the table structure&amp;nbsp;such as new or&amp;nbsp;retired fields.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any way to run the same&amp;nbsp;profiling when the dataset is changing dynamically&amp;nbsp;without modifying the process?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ioanna&lt;/P&gt;</description>
    <pubDate>Fri, 03 Aug 2018 07:48:54 GMT</pubDate>
    <dc:creator>IoannaKPMGcy</dc:creator>
    <dc:date>2018-08-03T07:48:54Z</dc:date>
    <item>
      <title>Profiling on dynamic data source</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Profiling-on-dynamic-data-source/m-p/483692#M15085</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are trying to run&amp;nbsp;the profiling process we have build and an&amp;nbsp;error occurred regarding a field that has been retired from the source. Before this change the&amp;nbsp;profiling process was completed successfully as expected.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please note that our data source is a view table. Thus, changes are expected in the table structure&amp;nbsp;such as new or&amp;nbsp;retired fields.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any way to run the same&amp;nbsp;profiling when the dataset is changing dynamically&amp;nbsp;without modifying the process?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ioanna&lt;/P&gt;</description>
      <pubDate>Fri, 03 Aug 2018 07:48:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Profiling-on-dynamic-data-source/m-p/483692#M15085</guid>
      <dc:creator>IoannaKPMGcy</dc:creator>
      <dc:date>2018-08-03T07:48:54Z</dc:date>
    </item>
    <item>
      <title>Re: Profiling on dynamic data source</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/Profiling-on-dynamic-data-source/m-p/486727#M15159</link>
      <description>&lt;P&gt;Ioanna,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I see clearly the scenario you are depicting.&amp;nbsp; Unfortunately, once a Data Plan has been saved and established it expects to be served with the same schema for each run.&amp;nbsp; The data sources and content can be dissimilar, as long as the schema matches the original data source.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As transformations are associated with a Data Plan, the transformations are working against specific columns/data types. When your view undergoes schema change, any transformations that worked directly against a "now-gone" column would be come invalidated.&amp;nbsp; This may invalidate one transformation and have a cascading effect through others.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Answering your question directly;&amp;nbsp; structural changes made in the schema of your view would require intervention on your part.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Quick thought: most difficulties occur when your view has dropped a column and a transformations in your Data Plan performs actions on that dropped column.&amp;nbsp; Conversely, If your view added a column, the Data Plan does not worry quite so much because the new column has no association with transformations in your Data Plan.&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Daniel Paner&lt;/P&gt;
&lt;P&gt;Principal Product Manager&lt;/P&gt;
&lt;P&gt;SAS Viya Data Management&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2018 15:48:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/Profiling-on-dynamic-data-source/m-p/486727#M15159</guid>
      <dc:creator>SAS-Dan</dc:creator>
      <dc:date>2018-08-14T15:48:20Z</dc:date>
    </item>
  </channel>
</rss>

