<?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: Identify invalid changes in value in a long dataset in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/557454#M155403</link>
    <description>I do have a list of all possible values as well as valid changes. I didn't think it was important to list that here.&lt;BR /&gt;&lt;BR /&gt;There are no missing values for id, type, or date in my data set. Basically want I want to do is set rules for valid changes and set all other conditions to be invalid.&lt;BR /&gt;&lt;BR /&gt;You are correct that I mean "within values of ID". For an ID that has only one record I suppose it is fine for the flag value to be missing.</description>
    <pubDate>Thu, 09 May 2019 14:40:09 GMT</pubDate>
    <dc:creator>martyvd</dc:creator>
    <dc:date>2019-05-09T14:40:09Z</dc:date>
    <item>
      <title>Identify invalid changes in value in a long dataset</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/557282#M155319</link>
      <description>&lt;P&gt;I have an issue similar to the one described &lt;A href="https://communities.sas.com/t5/General-SAS-Programming/Identify-change-in-value-in-long-dataset/m-p/270112/highlight/true#M37680" target="_self"&gt;here&lt;/A&gt;, but a bit more complex. See example data below. I need to flag when the type changes, but only for certain invalid changes. For example changing from type 1 to type 2 or vice versa is valid but changing from type 2 to type 3 is not.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Type&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; Date&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Flag&lt;/P&gt;&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/03/15&lt;/P&gt;&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/04/15&lt;/P&gt;&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;03/05/15&lt;/P&gt;&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/06/15&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&lt;/P&gt;&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp; 03/07/15&lt;/P&gt;&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/03/15&lt;/P&gt;&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/04/15&lt;/P&gt;&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/05/15&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&lt;/P&gt;&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;03/06/15&amp;nbsp;&lt;/P&gt;&lt;P&gt;0003&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/03/15&lt;/P&gt;&lt;P&gt;0003&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/04/15&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&lt;/P&gt;&lt;P&gt;0003&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/05/15&lt;/P&gt;&lt;P&gt;0004&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/06/15&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am hoping to create a variable for each observation that indicates valid change, invalid change, or no change. I would appreciate any suggestions.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2019 20:32:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/557282#M155319</guid>
      <dc:creator>martyvd</dc:creator>
      <dc:date>2019-05-08T20:32:37Z</dc:date>
    </item>
    <item>
      <title>Re: Identify invalid changes in value in a long dataset</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/557286#M155321</link>
      <description>&lt;P&gt;Use LAG() to check the difference.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data want;
set have;

by ID date; *may need to presort your data;

*get previous Type value;
prev_type = lag(Type);

*if first for that ID, don't use previous value since it will be for wrong ID;
if first.id then call missing(prev_type);

*rules to set flags, for more rules add more if/then statements;
if type=3 and prev_type = 2 then flag=1;



run;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/228746"&gt;@martyvd&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;I have an issue similar to the one described &lt;A href="https://communities.sas.com/t5/General-SAS-Programming/Identify-change-in-value-in-long-dataset/m-p/270112/highlight/true#M37680" target="_self"&gt;here&lt;/A&gt;, but a bit more complex. See example data below. I need to flag when the type changes, but only for certain invalid changes. For example changing from type 1 to type 2 or vice versa is valid but changing from type 2 to type 3 is not.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Type&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; Date&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Flag&lt;/P&gt;
&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/03/15&lt;/P&gt;
&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/04/15&lt;/P&gt;
&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;03/05/15&lt;/P&gt;
&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/06/15&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&lt;/P&gt;
&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp; 03/07/15&lt;/P&gt;
&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/03/15&lt;/P&gt;
&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/04/15&lt;/P&gt;
&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/05/15&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&lt;/P&gt;
&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;03/06/15&amp;nbsp;&lt;/P&gt;
&lt;P&gt;0003&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/03/15&lt;/P&gt;
&lt;P&gt;0003&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/04/15&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&lt;/P&gt;
&lt;P&gt;0003&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/05/15&lt;/P&gt;
&lt;P&gt;0004&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/06/15&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am hoping to create a variable for each observation that indicates valid change, invalid change, or no change. I would appreciate any suggestions.&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2019 20:56:01 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/557286#M155321</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2019-05-08T20:56:01Z</dc:date>
    </item>
    <item>
      <title>Re: Identify invalid changes in value in a long dataset</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/557322#M155345</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/228746"&gt;@martyvd&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;I have an issue similar to the one described &lt;A href="https://communities.sas.com/t5/General-SAS-Programming/Identify-change-in-value-in-long-dataset/m-p/270112/highlight/true#M37680" target="_self"&gt;here&lt;/A&gt;, but a bit more complex. See example data below. I need to flag when the type changes, but only for certain invalid changes. For example changing from type 1 to type 2 or vice versa is valid but changing from type 2 to type 3 is not.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Type&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp; Date&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Flag&lt;/P&gt;
&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/03/15&lt;/P&gt;
&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/04/15&lt;/P&gt;
&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;03/05/15&lt;/P&gt;
&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/06/15&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&lt;/P&gt;
&lt;P&gt;0001&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp; 03/07/15&lt;/P&gt;
&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/03/15&lt;/P&gt;
&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/04/15&lt;/P&gt;
&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/05/15&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&lt;/P&gt;
&lt;P&gt;0002&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;03/06/15&amp;nbsp;&lt;/P&gt;
&lt;P&gt;0003&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/03/15&lt;/P&gt;
&lt;P&gt;0003&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/04/15&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&lt;/P&gt;
&lt;P&gt;0003&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/05/15&lt;/P&gt;
&lt;P&gt;0004&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 03/06/15&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am hoping to create a variable for each observation that indicates valid change, invalid change, or no change. I would appreciate any suggestions.&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Have you covered all of the possible values and "valid" changes? Can any values&amp;nbsp;be missing? If missing then what are the rules involving that for a "valid" or "invalid" change.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And how do you want to indicate an invalid change? BTW, you didn't show any values of 3 or what appears to be an invalid change so your example data is incomplete. If practical you should show enough cases to cover the possibilities.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am assuming that you meant to specify "within values of ID". If so, what do you want to indicate for an ID that only has 1 record? Since there is not another to compare then you likely do not want a flag value that appears the same as "no change".&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2019 23:11:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/557322#M155345</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2019-05-08T23:11:35Z</dc:date>
    </item>
    <item>
      <title>Re: Identify invalid changes in value in a long dataset</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/557454#M155403</link>
      <description>I do have a list of all possible values as well as valid changes. I didn't think it was important to list that here.&lt;BR /&gt;&lt;BR /&gt;There are no missing values for id, type, or date in my data set. Basically want I want to do is set rules for valid changes and set all other conditions to be invalid.&lt;BR /&gt;&lt;BR /&gt;You are correct that I mean "within values of ID". For an ID that has only one record I suppose it is fine for the flag value to be missing.</description>
      <pubDate>Thu, 09 May 2019 14:40:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/557454#M155403</guid>
      <dc:creator>martyvd</dc:creator>
      <dc:date>2019-05-09T14:40:09Z</dc:date>
    </item>
    <item>
      <title>Re: Identify invalid changes in value in a long dataset</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/557637#M155476</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/228746"&gt;@martyvd&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;I do have a list of all possible values as well as valid changes. I didn't think it was important to list that here.&lt;BR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There are coding approaches that can work for specific values such as: thisvalue - thatvalue &amp;gt; 1 that might work when 1 to 3 is not valid (3 - 1 = 2) but what if 2 to 5 is acceptable? That specific calculation would not be invalid.&lt;/P&gt;
&lt;P&gt;So if there are not specific rules then all of the valid (or invalid , which ever is shorter) combinations are needed for code to have a chance to work the first time.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If one value can only be valid followed by one specific value, fine. That's a relatively short list. But if 2 could be followed by 4, 7, 8, 10 and 12 we have a completely different kettle of monkeys, or is that a barrel of fish?&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2019 22:48:01 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/557637#M155476</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2019-05-09T22:48:01Z</dc:date>
    </item>
    <item>
      <title>Re: Identify invalid changes in value in a long dataset</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/558759#M155968</link>
      <description>&lt;P&gt;The specific rules are as follows:&lt;BR /&gt;&lt;BR /&gt;1 to 2 or vice versa is valid.&lt;BR /&gt;3 to 13 or vice versa is valid.&lt;BR /&gt;3 to 23 or vice versa is valid.&lt;BR /&gt;97,98, or 99 to any other value is valid.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All other changes are invalid.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2019 20:13:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/558759#M155968</guid>
      <dc:creator>martyvd</dc:creator>
      <dc:date>2019-05-14T20:13:45Z</dc:date>
    </item>
    <item>
      <title>Re: Identify invalid changes in value in a long dataset</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/558766#M155971</link>
      <description>Given what is here you should be able to adapt the code to your rules. Are you having issues doing that? If so, post your code please.</description>
      <pubDate>Tue, 14 May 2019 20:35:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Identify-invalid-changes-in-value-in-a-long-dataset/m-p/558766#M155971</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2019-05-14T20:35:02Z</dc:date>
    </item>
  </channel>
</rss>

