<?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: Using Column Properties in Column Functions? in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/Using-Column-Properties-in-Column-Functions/m-p/481995#M72635</link>
    <description>&lt;P&gt;You could use a formula with something like this:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-jsl"&gt;If(Row() == 1,
	specs = :NPN1 &amp;lt;&amp;lt; Get Property("Spec Limits");
	lsl = Try(specs["LSL"], .);
	usl = Try(specs["USL"], .);
	val = .;
);
val = IfMZ(:NPN1 &amp;lt; lsl | :NPN1 &amp;gt; usl, 1, 0);
val;&lt;/CODE&gt;&lt;CODE class=" language-jsl"&gt;&lt;/CODE&gt;&lt;BR /&gt;&lt;CODE class=" language-jsl"&gt;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;but if you have many columns to check, I think this is easier to do on tall/stacked data in which you can have columns such as parameter, value, lsl and usl. Then with those you can easily create a formula for flagging.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Some platforms also allow you to select and color out of spec values, but these might work only on one column at a time.&lt;/P&gt;</description>
    <pubDate>Mon, 25 Apr 2022 19:52:50 GMT</pubDate>
    <dc:creator>jthi</dc:creator>
    <dc:date>2022-04-25T19:52:50Z</dc:date>
    <item>
      <title>Using Column Properties in Column Functions?</title>
      <link>https://community.jmp.com/t5/Discussions/Using-Column-Properties-in-Column-Functions/m-p/481976#M72634</link>
      <description>&lt;P&gt;Is there a way to create a new function column within a table that uses the properties of another column along with that column's data?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For instance, making a flag column for items outside of assigned LSL and USL?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know I can do it by using JSL and iteratively evaluating cell values and Get Property ... etc, but that seems unnecessarily complex for such a simple comparison and logic operation. In particular, the nested Spec--&amp;gt;LSL and Spec--&amp;gt;USL are not easy to work with when one or both may be missing on a particular column.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 10 Jun 2023 23:47:37 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Using-Column-Properties-in-Column-Functions/m-p/481976#M72634</guid>
      <dc:creator>MoarData</dc:creator>
      <dc:date>2023-06-10T23:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: Using Column Properties in Column Functions?</title>
      <link>https://community.jmp.com/t5/Discussions/Using-Column-Properties-in-Column-Functions/m-p/481995#M72635</link>
      <description>&lt;P&gt;You could use a formula with something like this:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-jsl"&gt;If(Row() == 1,
	specs = :NPN1 &amp;lt;&amp;lt; Get Property("Spec Limits");
	lsl = Try(specs["LSL"], .);
	usl = Try(specs["USL"], .);
	val = .;
);
val = IfMZ(:NPN1 &amp;lt; lsl | :NPN1 &amp;gt; usl, 1, 0);
val;&lt;/CODE&gt;&lt;CODE class=" language-jsl"&gt;&lt;/CODE&gt;&lt;BR /&gt;&lt;CODE class=" language-jsl"&gt;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;but if you have many columns to check, I think this is easier to do on tall/stacked data in which you can have columns such as parameter, value, lsl and usl. Then with those you can easily create a formula for flagging.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Some platforms also allow you to select and color out of spec values, but these might work only on one column at a time.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2022 19:52:50 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Using-Column-Properties-in-Column-Functions/m-p/481995#M72635</guid>
      <dc:creator>jthi</dc:creator>
      <dc:date>2022-04-25T19:52:50Z</dc:date>
    </item>
  </channel>
</rss>

