Just as there is the option HIDDEN_ROWS. For those that don't want to just hide a row, but want it to be deleted.
You should be able to get the effect of "delete_column" but DROPping the variable(s) you don't want in what ever you are doing to create the output. Similarly a Where clause as a dataset option may allow only showing the rows you want or subset the data prior to what ever creates the output.
proc (whatever) data=mylib.mydataset (drop= thisvar thatvar where= ( othervar in (<some list of values))) ;
or othervar ❤️ or similar.
Thanks, BallardW https://communities.sas.com/t5/user/viewprofilepage/user-id/13884
But not good enough for me. You present truly reasonable reasons why I shouldn't need this feature. BUT -- How would you output PROC TABULATE column headers and append them to the top of subsequent PROC PRINT output. I used the HIDDEN_ROWS option to do this with ODS EXCEL. Would you know another way I could have structured PROC-TABULATE-like column headers with the option of string ouput as is available in PROC PRINT or REPORT? (I admit I didn't look very hard for another solution)
An example to clarify the issue would help if could show the behavior without the desired function and with the desired function. I'm not sure if your example is a before or after and what the exact desired change would be.
Sorry for the delay in responding, I certainly need a better illustration, forgive me, and thanks for responding.
So I like the ODS EXCEL option HIDDEN_ROWS because it allows me to hide the rows 6-8 in the output below, so that it is shown as it is in the graphic (my comment above).
I like HIDDEN_ROWS, but it would be also good if a user could chose to delete these rows; a user may not want their customer or anyone to have access or unhide these rows ever.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.