<?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: Single Column V look up equivalent in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902420#M106138</link>
    <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.jmp.com/t5/user/viewprofilepage/user-id/2687"&gt;@txnelson&lt;/a&gt;&amp;nbsp;!&lt;/P&gt;
&lt;P&gt;I was wanting to keep it as a formula column but I'll keep this in my back pocket as well.&lt;/P&gt;</description>
    <pubDate>Sun, 21 Sep 2025 16:46:36 GMT</pubDate>
    <dc:creator>shampton82</dc:creator>
    <dc:date>2025-09-21T16:46:36Z</dc:date>
    <item>
      <title>Single Column V look up equivalent</title>
      <link>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902328#M106129</link>
      <description>&lt;P&gt;Hey everyone,&lt;/P&gt;
&lt;P&gt;So I have been using a formula that works in the same way as vlookup in excel but I have now discovered that it does not work on larger data tables as it basically bogs down and kills JMP.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Attached is a sample data table and where I have split out the two functions that I had combined which works as expected:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="shampton82_2-1758413937922.png" style="width: 400px;"&gt;&lt;img src="https://community.jmp.com/t5/image/serverpage/image-id/83012iCCCDAE0638327FA0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="shampton82_2-1758413937922.png" alt="shampton82_2-1758413937922.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;VLU Item&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="shampton82_1-1758413916252.png" style="width: 400px;"&gt;&lt;img src="https://community.jmp.com/t5/image/serverpage/image-id/83011i3AB71BF089CDF071/image-size/medium?v=v2&amp;amp;px=400" role="button" title="shampton82_1-1758413916252.png" alt="shampton82_1-1758413916252.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;VLU Result&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="shampton82_0-1758413903290.png" style="width: 400px;"&gt;&lt;img src="https://community.jmp.com/t5/image/serverpage/image-id/83010i591EFB8BDFBC6B88/image-size/medium?v=v2&amp;amp;px=400" role="button" title="shampton82_0-1758413903290.png" alt="shampton82_0-1758413903290.png" /&gt;&lt;/span&gt;&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;
&lt;P&gt;If I were to take the formula from the "VLU Item" column and put it into the VLU Results formula this will cause the death spiral.&amp;nbsp; Having the columns be two separate ones is not a deal breaker but it would be cleaner if I could do it in one formula.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for any ideas!!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Steve&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 21 Sep 2025 00:25:32 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902328#M106129</guid>
      <dc:creator>shampton82</dc:creator>
      <dc:date>2025-09-21T00:25:32Z</dc:date>
    </item>
    <item>
      <title>Re: Single Column V look up equivalent</title>
      <link>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902364#M106131</link>
      <description>&lt;P&gt;With the introduction of fancy new Col Aggregation, some speed issues got fixed in JMP19:&lt;BR /&gt;&lt;LI-MESSAGE title="New in Graph Builder for JMP 19" uid="895744" url="https://community.jmp.com/t5/JMPer-Cable/New-in-Graph-Builder-for-JMP-19/m-p/895744#U895744" discussion_style_icon_css="lia-mention-container-editor-message lia-img-icon-blog-thread lia-fa-icon lia-fa-blog lia-fa-thread lia-fa"&gt;&lt;/LI-MESSAGE&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;this one as well : )&lt;/P&gt;</description>
      <pubDate>Sun, 21 Sep 2025 08:20:37 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902364#M106131</guid>
      <dc:creator>hogi</dc:creator>
      <dc:date>2025-09-21T08:20:37Z</dc:date>
    </item>
    <item>
      <title>Re: Single Column V look up equivalent</title>
      <link>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902366#M106132</link>
      <description>&lt;P&gt;Another way to do a VLookup in JMP is to use the Update platform.&amp;nbsp; This is a very efficient.&amp;nbsp; It does require that the lookup values are in a separate table, however, for your data table, that is an easy operation.&amp;nbsp; Here is a script that performs your lookup very quickly.&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-jsl"&gt;Names Default To Here( 1 );
dt = Current Data Table();
// Select matching cells
dt &amp;lt;&amp;lt; Select Where( :VALUE_STR == "" );
// Invert current selection
dt &amp;lt;&amp;lt; Invert Row Selection;
// Subset data table
// → Data Table( "Subset of Vlookup example" )
dt &amp;lt;&amp;lt; Select Where( :VALUE_STR == "" );
dt &amp;lt;&amp;lt; Invert Row Selection;
dtSum = dt &amp;lt;&amp;lt; Subset(
	Selected Rows( 1 ),
	columns( :HEADER_ID, :VALUE_STR ),
	output table( "Lookup" )
);
// Change column name: VALUE_STR → VLU Result from UPdate
dtSum:VALUE_STR &amp;lt;&amp;lt; Set Name( "VLU Result from UPdate" );
// Update data table
dt &amp;lt;&amp;lt; Update(
	With( Data Table( dtSum ) ),
	Match Columns( :HEADER_ID = :HEADER_ID )
);
// Remove Lookup table
Close( dtSum, nosave );&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sun, 21 Sep 2025 08:30:53 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902366#M106132</guid>
      <dc:creator>txnelson</dc:creator>
      <dc:date>2025-09-21T08:30:53Z</dc:date>
    </item>
    <item>
      <title>Re: Single Column V look up equivalent</title>
      <link>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902369#M106133</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.jmp.com/t5/user/viewprofilepage/user-id/16391"&gt;@shampton82&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;If I were to take the formula from the "VLU Item" column and put it into the VLU Results formula this will cause the death spiral.&amp;nbsp;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;It actually feels like a death spiral - but looking closer, it's a spiral of extreme coffee consumption.&lt;BR /&gt;And it will show you how often JMP re-calculates column formulas!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The issue is caused by the&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-jsl"&gt;Col Maximum(if (String comparison ))&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Besides abandoning the idea of a column formula, other workarounds for&amp;nbsp; JMP &amp;lt; 19 are:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;DON'T use a string comparison, convert the string to a number:&lt;BR /&gt;
&lt;PRE&gt;&lt;CODE class=" language-jsl"&gt;:VALUE_STR[Col Maximum( If( :X__3 == 3.1, Row(), . ), :HEADER_ID )]&lt;/CODE&gt;&lt;/PRE&gt;
&lt;LI-MESSAGE title="Tips and Tricks - best practice with JMP/JSL" uid="662686" url="https://community.jmp.com/t5/Discussions/Tips-and-Tricks-best-practice-with-JMP-JSL/m-p/662686#U662686" discussion_style_icon_css="lia-mention-container-editor-message lia-img-icon-forum-thread lia-fa-icon lia-fa-forum lia-fa-thread lia-fa"&gt;&lt;/LI-MESSAGE&gt;&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;... or use &lt;FONT face="courier new,courier"&gt;Contains()&amp;nbsp;&amp;nbsp;&lt;/FONT&gt;&lt;BR /&gt;
&lt;PRE&gt;&lt;CODE class=" language-jsl"&gt;:VALUE_STR[Col Maximum( If( contains(:X__3 , "V3_1"), Row(), . ), :HEADER_ID )]&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/LI&gt;
&lt;LI&gt;DON'T use &lt;FONT face="courier new,courier"&gt;col max()&lt;/FONT&gt; to "distribute" a single value in groups&lt;BR /&gt;&amp;nbsp;...&amp;nbsp;&lt;FONT face="courier new,courier"&gt;col median()&lt;/FONT&gt; is much faster:&lt;BR /&gt;
&lt;PRE&gt;&lt;CODE class=" language-jsl"&gt;:VALUE_STR[Col Median( If( :X__3 == "V3_1", Row(), . ), :HEADER_ID )]&lt;/CODE&gt;&lt;/PRE&gt;
&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Mon, 22 Sep 2025 07:26:59 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902369#M106133</guid>
      <dc:creator>hogi</dc:creator>
      <dc:date>2025-09-22T07:26:59Z</dc:date>
    </item>
    <item>
      <title>Re: Single Column V look up equivalent</title>
      <link>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902420#M106138</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.jmp.com/t5/user/viewprofilepage/user-id/2687"&gt;@txnelson&lt;/a&gt;&amp;nbsp;!&lt;/P&gt;
&lt;P&gt;I was wanting to keep it as a formula column but I'll keep this in my back pocket as well.&lt;/P&gt;</description>
      <pubDate>Sun, 21 Sep 2025 16:46:36 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902420#M106138</guid>
      <dc:creator>shampton82</dc:creator>
      <dc:date>2025-09-21T16:46:36Z</dc:date>
    </item>
    <item>
      <title>Re: Single Column V look up equivalent</title>
      <link>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902421#M106139</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.jmp.com/t5/user/viewprofilepage/user-id/26800"&gt;@hogi&lt;/a&gt;&amp;nbsp;!&lt;/P&gt;
&lt;P&gt;I like your analogy better.&amp;nbsp; Also, your suggestion for use COLMEDIAN() worked perfectly.&amp;nbsp; Crazy that the two functions have such difference performances.&amp;nbsp; Just one more reason to look forward to getting 19 installed soon.&lt;/P&gt;</description>
      <pubDate>Sun, 21 Sep 2025 16:51:21 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902421#M106139</guid>
      <dc:creator>shampton82</dc:creator>
      <dc:date>2025-09-21T16:51:21Z</dc:date>
    </item>
    <item>
      <title>Re: Single Column V look up equivalent</title>
      <link>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902457#M106143</link>
      <description>&lt;P&gt;I also came up with a solution based on an Associative Array&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-jsl"&gt;As Constant(
	Summarize( bygp = by( :HEADER_ID, :VALUE_STR ) );
	aa = Associative Array( bygp[1], bygp[2] );
);
Parse( Eval( Parse( "aa[\!"" || Char( :HEADER_ID[Row()] ) || "\!"]" ) ) );&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 22 Sep 2025 01:31:23 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902457#M106143</guid>
      <dc:creator>txnelson</dc:creator>
      <dc:date>2025-09-22T01:31:23Z</dc:date>
    </item>
    <item>
      <title>Re: Single Column V look up equivalent</title>
      <link>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902473#M106148</link>
      <description>&lt;P&gt;wow!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Summarize with a 2 dimensional &lt;FONT face="courier new,courier"&gt;by&lt;/FONT&gt; group *)&lt;/LI&gt;
&lt;LI&gt;... fed into an associative array to strip off the missing entries:&lt;BR /&gt;Summarize sorts the entries, missing comes first - and is overwritten with the second pair&lt;/LI&gt;
&lt;LI&gt;speedup by using &lt;FONT face="courier new,courier"&gt;As Constant&lt;/FONT&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;even shorter:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-jsl"&gt;As Constant(
	Summarize( bygp = by( :HEADER_ID, :VALUE_STR ) );
	aa = Associative Array( bygp[1], bygp[2] );
);
aa[Char( :HEADER_ID[Row()] )];&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*) important: Summarize stores strings (for numeric columns as well) &lt;BR /&gt;-&amp;gt;&amp;nbsp; &amp;nbsp;&lt;FONT face="courier new,courier"&gt;aa[char( number&amp;nbsp; )]&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Sep 2025 05:36:27 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Single-Column-V-look-up-equivalent/m-p/902473#M106148</guid>
      <dc:creator>hogi</dc:creator>
      <dc:date>2025-09-22T05:36:27Z</dc:date>
    </item>
  </channel>
</rss>

