I have a parent search which retrieves list of values in a tabular format. On clicking any of the values the events corresponding to this value(child search) is retreived in another table.
However not all the events are being retrieved. There is only a certain sub set of events which are being displayed. When the same child query is executed on the flash timeline the results are completely different.
I am using a events viewer module to display the results of the child search.Below is the code.
I'm not sure why you're only getting a subset of the correct events.
My first suggestion is that you throw the following into the HTML module immediately downstream from your table click:
search is : <b>$search$</b>
timerange is : <b>$search.timeRange.earliest$</b>, <b>$search.timeRange.latest$</b>
Quite possibly there will be something about that search that is different from the control search that you're running in flashtimeline.
That aside, there is one problem with this XML that is possibly contributing to the problem. That is that you have an autoRun="true" nested inside another autoRun="True". This can cause some pretty unpredictable behavior and should never be done. Remove the deeper one and in fact you should remove both of them and have only one living all the way up on the TimeRangePicker module up top. Also delete the autoRun="False" because this is always meaningless.
Here's some other advice to help clean things up:
1) You dont need to respecify the layoutPanel attributes at each level. If a module has no layoutPanel attribute, it will inherit the value from the upstream modules.
2) you are nesting modules downstream from a SimpleResultsHeader but there's no reason for this. You can denest all those and make your view a bit less indented.
3) if you're using HTML modules already you can dispense with these SimpleResultsHeaders and just add
<h3> No of results $results.count$</h3>
to your existing HTML modules where appropriate. and delete the SimpleResultsHeader modules.
4) You're doing something a bit sketchy by having these fragments of table code carving up the page. I'd be surprised if that was working out correctly in all browsers. Fortunately you can just use panel_row1_col1, panel_row1_col2 and panel_row1_col3 to create three rounded corner panels all in a single row, and if you want to group modules WITHIN a single rounded-corner panel, you can use
panel_row1_col1 - will be a full width subsection across the top of the rounded-corner panel.
panel_row1_col1_grp1 - will be the lower left half of the rounded-corner panel
oanel_row1_col1_grp2 - will be the lower right half of the rounded corner panel.
Likewise if you want to evenly divide the panel into thirds, just add a panel_row1_col1_grp3. All in all I think this will be much easier to keep track of than these fragments of <table> and <tr><td> html .