Respect a filter already applied to a table?

rbuser

Hi Team,
Is there anyway to tell RB to respect a Filter already applied to a Table when a report is called?

The end user can apply all sorts of filter conditions to the table.
e.g Filter := (Date_In = 20/01/2017 and completed = false and '1234'$customer).

And other conditions, combinations that they would like to print a reoprt from.d

Regards & TIA,
Ian

nicocizik

Hi Ian,

I'm a bit unclear about your requirement.

ReportBuilder simply uses the data it is given. If you have applied
filters to a dataset that is connected to the report, then that filtered
data is what the report will use during generation.

Perhaps more information about how your application is designed and what
exactly you would like to happen will help me understand what you need
and allow me provide you with the best solution.

--

rbuser

Nico Cizik (Digital Metaphors) wrote:


Hi Nico,
Yeah. I think that is where my configuration falls down.

ATT as the App suite uses bith the Standalone & embeded reporting functionality, all the reports are contained in the
rbxxxx data files and are accessed by both the RB End User app and from inside the other Apps. This is to allow ready
customisation of the 'embeded'
IOW the core of the 'end user' example is in the Apps.
As they are accessing the Database directly they do not see the local table/dataset which is applying the filter.
I don't think I have ever used RB 'naked' as it were. Something to look at.

Regards,
Ian

nicocizik

Hi Ian,

If I understand correctly, you are using our End-User solution with
report templates saved to DB. Each of these reports contains its own
data definition (DADE) and is therefore self contained as far as data
access is concerned.

Where I become unclear is where and how you are allowing your users to
apply various filters to your tables. Is this done on a separate
Dataset in Delphi? What is the purpose of this dataset? If so, this
filter is not going to be used for the reports (which create their own
datsets). You would need to apply any filters as query search
conditions after the report loads (perhaps in the Template.OnLoadEnd.

--