cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Discussions

Solve problems, and share tips and tricks with other JMP users.
Choose Language Hide Translation Bar
dyakunin1
Level I

Why is there such unexpected re-calculation of columns without formulas?

I often use JMP to prototype data pipelines, calculating column values in one table, then querying data into another table based on calculation results. I noticed a behaviour that looks to me very strange and counterintuitive. Say, I have a table with three columns:

dyakunin1_0-1760063081445.png

The second and the third columns are calculated as Lag ( :Column 1 ) and Col Sum ( :Column 1 ).

Now I query the rows into a new table where :Column 1 > 2. The result is:

dyakunin1_1-1760063388612.png

":Lag of Column 1" and ":Column 1 Sum" get re-calculated, since the table inherited the formulas. This is understandable.

But what if I delete the formulas and update the table? Then, since I do not have formulas and I do not re-calculate values in the destination table, I will see the data as it is in the the source table, right? Guess what, wrong! Nothing changes. I still see null, 3 and 7, 7 not 2, 3 and 10, 10.

 

Is this a defect? Or is this as expected? How can this be explained?

 

Thanks!

12 REPLIES 12
dyakunin1
Level I

Re: Why is there such unexpected re-calculation of columns without formulas?

I did not contact them. I'd rather count on this community and myself  

hogi
Level XIII

Re: Why is there such unexpected re-calculation of columns without formulas?

Hm, I prefer an official fix vs. "workarounds".

get it fixed - and forget about it.

find a workaround and don't forget!!
- and don't forget to tell every colleague!

hogi
Level XIII

Re: Why is there such unexpected re-calculation of columns without formulas?

Concerning "community and myself" - I added the topic to
Caution: Places where Jmp does something unexpected 

On the other hand, I am quite confident that this issue can be resolved in the GUI.
Options similar to those in Subset could help the customer to understand the issue, and the default option should be to remove or disable the formula column.

hogi_0-1760165421633.png

Let's see if this behavior is considered a bug: TS-00244891.

If not, it will take longer, as we first need to collect enough Kudos on the wish list: Query Builder: disable formula column 

Recommended Articles