Row Drilldown ... First Field is too long

[SamChang]

I have done a drilldown for "SimpleResultsTable" module.
Below is my Drilldown settings

    <module name="SimpleResultsTable">
        <param name="drilldown">row</param>
        <param name="entityName">results</param>

        <module name="ConvertToDrilldownSearch">

            <module name="ConvertToIntention">

                .
                .
                .

            </module> <!-- module name="ConvertToIntention" -->

        </module> <!-- module name="ConvertToDrilldownSearch" -->

</module> <!-- module name="SimpleResultsTable" -->

I need transfer 4 parameters to drilldown search.
For example :

Transfer Param, Username, Src_IP, Dst_IP
aaaaaaaaaa-bbbbbbbbbb-cccccccccc-ddddddddddd, usera, 1.1.1.1, 10.10.10.10
gggggggggg-hhhhhhhhhh-uuuuuuuuuu-kkkkkkkkkkk, userb, 7.7.7.7, 20.20.20.20


So ... I get a problem ... The firsh field is too long.
Do you have any idea to fix this problem...
Maybe ...
01. let first field's width become to smaller ...
02. let first field become to hidden ...
03. let row drilldown's field become last field ...

Please help me to solve this problem ... Please

Dear Nick
I have fixed this problem by myself.
In my form search view ...
I can transfer many parameters to drilldown search.
I use "row" drilldown and put all parameters in first field.
so ... first field's value ...
look like ... param01-param02-param03-param04
When I click row ...
first field's value will be sent to drilldown search.

I let first field to be hid ...
01. I modify SimpleResultsTable.py
-- add some class to first field.

02. I modify css file for my view to hide first field.

[sideview]

One comment - i dont think it ever makes sense to have both ConvertToDrilldownSearch and ConvertToIntention in there. I recommend reading or re-reading the drilldown example views in the "ui examples for 4.1" app, which is available on splunkbase.

Im afraid that my earlier answer here completely misunderstood your problem. I thought that you needed all four values from the clicked-upon row in your search, but you just wanted to use the first value in the search but not have it display in the table.

Indeed as you've figured out, the best way to do that is to just use CSS to make the first cell not visible, but have it still be there so the drilldown logic will send down that string for the search.

UPDATE::

In Sideview Utils 2.2, there is a new module called "Table", and with the Table module come many improvements over the SimpleResultsTable module. Some of these improvements will help this issue greatly.

1) you can reference any field in the clicked-upon row using $row.fields.fieldName$ and $row.fields.someOtherFieldName$. Thus you're no longer restricted to only using the first column values in your drilldowns.

2) You can use the "hiddenFields" param to specify fields that you want available for drilldowns, but that you dont want to actually display in the visible table.

The latest version of Sideview Utils (2.2.10) is available for free, for internal use, from the sideview site -- http://sideviewapps.com/apps/sideview-utils

[SamChang]

I have updated my answer to my question ...