Dennis,
this is possible, but fairly complicated to setup. On the report that navigates TO your raw table, you will need to create a new column that uses the evalWiki function. It takes an explicit navigation link [such as this example from the online help]:
=EvalWiki("[[/myObject/!FILTER[myColumn="""&myColumn&"""]/ myReport|click here to see my report]]")
It can navigate to a report backed by a dataset [specifically the dataset's table transform]. The syntax for that is:
=EvalWiki("[[/@.TableTransform:<dataset name goes here>/!FILTER[myColumn="""&getLastFilterValue(myColumn)&"""]/ myReport|click here to see my report]]")
Specifically what it does is take a wikilink , and allow it to be clicked. The wiki link you want looks like this example [the details depend on column anmes, how many columns you are filtering on, etc]:
[[/tab:Service Costing/@.TableTransform:Cost Source Master Data/!filter[Cost Center="foo"]/MyReport]]
Then, copy/paste the raw table that you wish to edit onto this filtered, table transform based report. Right click it, and choose 'filter This Table'
Add the column that you are filtering on, pick equals, and in the values type:
<%=getLastFilterValue(Branch)%>
This will grab the value of the filter that you have applied to the report itself. This only work on reports backed by tables/objects, not top level or overview reports [What people are usually authoring with ad hoc query].
Hope this helps!