cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
%3CLINGO-SUB%20id%3D%22lingo-sub-611402%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3EHandling%20Hidden%20%2F%20Excluded%20rows%20%2F%20columns%20in%20Table-handling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-611402%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20using%20the%20Table-processing%20commands%2C%20it%20would%20be%20helpful%20to%20provide%20checkboxes%20in%20the%20dialog%20to%20determine%20how%20to%20handle%20hidden%20%2F%20excluded%20rows%20or%20columns.%20In%20particular%2C%20this%20is%20problematic%20with%20splitting%20tables.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3EMehul%20Shroff%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-611402%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3E%3CLINGO-LABEL%3EData%20Blending%20and%20Cleanup%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-618980%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3ERe%3A%20Handling%20Hidden%20%2F%20Excluded%20rows%20%2F%20columns%20in%20Table-handling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-618980%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3E%3CP%3EI%20like%20this%2C%20I%20would%20also%20like%20to%20add%20in%20a%20check%20box%20for%20using%20only%20selected%20data%2C%20that%20way%20you%20don't%20have%20to%20subset%20then%20split%20from%20the%20new%20table.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESteve%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-620922%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3ERe%3A%20Handling%20Hidden%20%2F%20Excluded%20rows%20%2F%20columns%20in%20Table-handling%20-%20Status%20changed%20to%3A%20Needs%20Info%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-620922%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3E%3CP%3EThank%20you%20for%20this%20suggestion.%20Can%20you%20please%20provide%20additional%20information%20on%20what%20you%20would%20like%20to%20see%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-631634%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3ERe%3A%20Handling%20Hidden%20%2F%20Excluded%20rows%20%2F%20columns%20in%20Table-handling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-631634%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20like%20to%20have%20a%20dialog%20option%20to%20choose%20whether%20to%20include%20hidden%20%2F%20excluded%20rows%20in%20the%20output%20table%20when%20doing%20a%20Split%20Table.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20a%20related%20note%2C%20I%20would%20like%20to%20request%20the%20availability%20of%20the%20same%20option%20when%20doing%20an%20export%20from%20JMP%20into%20another%20format.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3EMehul%20Shroff%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644801%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3ERe%3A%20Handling%20Hidden%20%2F%20Excluded%20rows%20%2F%20columns%20in%20Table-handling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644801%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3E%3CBLOCKQUOTE%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.jmp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F26800%22%20target%3D%22_blank%22%3E%40hogi%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EAlternative%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eplease%20add%20an%20option%20to%20store%20the%20excluded%20state%20in%20an%20additional%20column%20(many%20column%20in%20the%20case%20of%20split).%3C%2FP%3E%0A%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3ETake%20a%20look%20at%20%3CA%20href%3D%22https%3A%2F%2Fwww.jmp.com%2Fsupport%2Fhelp%2Fen%2F17.1%2Findex.shtml%23page%2Fjmp%2Fstore-information-in-row-state-columns.shtml%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3ERow%20State%20columns%3C%2FA%3E.%20They%20do%20just%20that%3A%20store%20row%20states%20in%20a%20column.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644812%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3ERe%3A%20Handling%20Hidden%20%2F%20Excluded%20rows%20%2F%20columns%20in%20Table-handling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644812%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.jmp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6878%22%20target%3D%22_blank%22%3E%40Jeff_Perkinson%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Egreat%20that%20this%20feature%20is%20already%20available%20-%20I%20didn't%20find%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhich%20option%20tells%20Tables%2FSplit%20so%20map%20the%20row%20states%20of%20the%20the%20input%20table%20to%20row%20state%20columns%20in%20the%20output%20table%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644408%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3ERe%3A%20Handling%20Hidden%20%2F%20Excluded%20rows%20%2F%20columns%20in%20Table-handling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644408%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3E%3CP%3EWhat%20a%20brilliant%20idea%20%3CLI-EMOJI%20id%3D%22lia_slightly-smiling-face%22%20title%3D%22%3Acara_con_una_leve_sonrisa%3A%22%3E%3C%2FLI-EMOJI%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20there%20is%20a%20good%20reason%20why%20%3CSTRONG%3Esummary%3C%2FSTRONG%3E%20respects%20excluded%20-%20there%20could%20be%20a%20similar%20reason%20why%20the%20other%20platforms%20should%20respect%20it%20as%20well%20(at%20least%20for%20some%20cases).%3C%2FP%3E%3CP%3EIf%20there%20is%20a%20good%20reason%20why%20a%20platform%20doesn't%20respect%20excluded%20-%20there%20could%20be%20a%20similar%20reason%20why%20%3CSTRONG%3Esummary%3C%2FSTRONG%3E%20shouldn't%20either%20(at%20least%20for%20some%20cases).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%26nbsp%3B%3CBR%20%2F%3Eplease%20add%20a%20yes%2Fno%26nbsp%3B%20%26gt%3Boption%26lt%3B%20to%20%3CSTRONG%3EALL%3C%2FSTRONG%3E%20Table%20platforms%26nbsp%3B%3CBR%20%2F%3E...%26nbsp%3B%20to%20%3CSTRONG%3Erespect%20excluded%3C%2FSTRONG%3E%26nbsp%3B%20(for%20split%2C%20stack%2C%20update%20...)%3CBR%20%2F%3E...%20and%20if%20you%20wish%3A%20to%20disable%20it%20for%20summary%20%3CLI-EMOJI%20id%3D%22lia_slightly-smiling-face%22%20title%3D%22%3Acara_con_una_leve_sonrisa%3A%22%3E%3C%2FLI-EMOJI%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlternative%3A%26nbsp%3B%3C%2FP%3E%3CP%3Eplease%20add%20an%20option%20to%20store%20the%20excluded%20state%20in%20an%20additional%20column%20(many%20column%20in%20the%20case%20of%20split).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlternative%3A%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20add%20a%20warning%20that%20the%20respective%20Table%20Platform%20is%20one%20of%20those%20which%20ignore%20excluded%3CBR%20%2F%3E(e.g.%20as%20a%20option%20in%20the%20platform%3A%20%22respect%20excluded%22%20-%20an%20option%20which%20is%20disabled%3CBR%20%2F%3Eor%3A%20as%20status%20text%20on%20the%20bottom%20left)%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIt's%20clear%20that%20the%20user%20just%20has%20to%20generate%20a%20subset%20of%20the%20non-excluded%20row.%3CBR%20%2F%3Eso%20...%3CBR%20%2F%3E%3CSTRONG%3EWhy%20is%20this%20idea%20important%3F%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDue%20to%20table%20linking%20-%20the%20user%20gets%20a%20visual%20feedback%20that%20Tables%2FSummary%20does%20respect%20%22excluded%22%3A%3C%2FP%3E%3CPRE%3E%3CCODE%20class%3D%22%20language-jsl%22%3ECurrent%20Data%20Table()%20%26lt%3B%26lt%3B%20Data%20Filter(%0AAdd%20Filter(%0Acolumns(%20%3Aage%20)%2C%0AWhere(%20%3Aage%20%3D%3D%20%7B14%2C%2017%7D%20)%0A))%3B%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22hogi_0-1687316808898.png%22%20style%3D%22width%3A%20271px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22hogi_0-1687316808898.png%22%20style%3D%22width%3A%20271px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22hogi_0-1687316808898.png%22%20style%3D%22width%3A%20271px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22hogi_0-1687316808898.png%22%20style%3D%22width%3A%20271px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22hogi_0-1687316808898.png%22%20style%3D%22width%3A%20271px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22hogi_0-1687316808898.png%22%20style%3D%22width%3A%20271px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22hogi_0-1687316808898.png%22%20style%3D%22width%3A%20271px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22hogi_0-1687316808898.png%22%20style%3D%22width%3A%20271px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22hogi_0-1687316808898.png%22%20style%3D%22width%3A%20271px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22hogi_0-1687316808898.png%22%20style%3D%22width%3A%20271px%3B%22%3E%3Cspan%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22hogi_0-1687316808898.png%22%20style%3D%22width%3A%20271px%3B%22%3E%3Cimg%20src%3D%22https%3A%2F%2Fcommunity.jmp.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F53982i209777C40DF4646C%2Fimage-dimensions%2F271x345%3Fv%3Dv2%22%20width%3D%22271%22%20height%3D%22345%22%20role%3D%22button%22%20title%3D%22hogi_0-1687316808898.png%22%20alt%3D%22hogi_0-1687316808898.png%22%20%2F%3E%3C%2Fspan%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20it's%20not%20obvious%20that%20the%20other%20platforms%20ignore%20%22excluded%22%20-%20and%20it's%20hard%20to%20find%20this%20info%20in%20the%20Documentation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-702885%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3ERe%3A%20Handling%20Hidden%20%2F%20Excluded%20rows%20%2F%20columns%20in%20Table-handling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-702885%22%20slang%3D%22en-US%22%20mode%3D%22NONE%22%3E%3CP%3Eadded%20to%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.jmp.com%2Ft5%2FDiscussions%2FTiny-Traps-in-Jmp-and-JSL%2Fm-p%2F702685%23U702685%22%20class%3D%22lia-mention-container-editor-message%20lia-img-icon-forum-thread%20lia-fa-icon%20lia-fa-forum%20lia-fa-thread%20lia-fa%22%20target%3D%22_blank%22%3ETiny%20Traps%20in%20Jmp%20and%20JSL%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Choose Language Hide Translation Bar

Handling Hidden / Excluded rows / columns in Table-handling

Hello,

 

When using the Table-processing commands, it would be helpful to provide checkboxes in the dialog to determine how to handle hidden / excluded rows or columns. In particular, this is problematic with splitting tables.

 

Regards

Mehul Shroff

7 Comments
shampton82
Level VII

I like this, I would also like to add in a check box for using only selected data, that way you don't have to subset then split from the new table.

 

Steve

mia_stephens
Staff
Status changed to: Needs Info

Thank you for this suggestion. Can you please provide additional information on what you would like to see?

MShroff
Level V

Hello,

 

I would like to have a dialog option to choose whether to include hidden / excluded rows in the output table when doing a Split Table.

 

On a related note, I would like to request the availability of the same option when doing an export from JMP into another format.

 

Regards

Mehul Shroff

hogi
Level XI

What a brilliant idea

If there is a good reason why summary respects excluded - there could be a similar reason why the other platforms should respect it as well (at least for some cases).

If there is a good reason why a platform doesn't respect excluded - there could be a similar reason why summary shouldn't either (at least for some cases).

 

Yes, 
please add a yes/no  >option< to ALL Table platforms 
...  to respect excluded  (for split, stack, update ...)
... and if you wish: to disable it for summary

 

Alternative: 

please add an option to store the excluded state in an additional column (many column in the case of split).

 

Alternative: 

Please add a warning that the respective Table Platform is one of those which ignore excluded
(e.g. as a option in the platform: "respect excluded" - an option which is disabled
or: as status text on the bottom left)


It's clear that the user just has to generate a subset of the non-excluded row.
so ...
Why is this idea important? 

 

Due to table linking - the user gets a visual feedback that Tables/Summary does respect "excluded":

Current Data Table() << Data Filter(
Add Filter(
columns( :age ),
Where( :age == {14, 17} )
));

 

hogi_0-1687316808898.png

 

So, it's not obvious that the other platforms ignore "excluded" - and it's hard to find this info in the Documentation.

Jeff_Perkinson
Community Manager
@hogi wrote:

Alternative: 

please add an option to store the excluded state in an additional column (many column in the case of split).


Take a look at Row State columns. They do just that: store row states in a column.

 

 

hogi
Level XI

Hi @Jeff_Perkinson 

great that this feature is already available - I didn't find it.

 

Which option tells Tables/Split so map the row states of the the input table to row state columns in the output table?

hogi
Level XI