Bex Broadcaster - filtering by characteristic based on query results?

[Former Member]

Hiya,

I run a bex query which gives me a list of projects (0PROJECT) a user is working on. A result set can be say 20 projects long. Now, I need Broadcaster to send 20 Excel files to the user in question so that they can forward each file to their clients for review.

I set up a broadcaster setting with user in variable and 0PROJECT characteristic in the drilldown and then filtered by characteristic 0PROJECT. But it requires me to manually set up the filter to include the 20 projects - it's not picking up from the initial query which already has 20 projects. The list of projects will change constantly for the user, on a daily basis, new projects will be added etc. and I don't want to be updating the filters constantly, that would not be feasible for thousands of users worldwide.

Anyone have any ideas, please?

In the full business scenario I want to distribute separate emails to all users that have any projects and I want to split by their projects. So user A will receive email with 20 Excel files, user B with 15 Excel files etc. So ideally would like to use one filter by USER and second by 0PROJECT, but I need them to work nicely together.

[Former Member]

Koen, I think we will look at WEBI more closely, especially that the broadcaster is old technology. I haven't tried much scheduling in WEBI, so not quite familiar with what it can do, but your suggestion that it can do what I need is very promising.

[Former Member]

William, Thanks for the suggestion, but I don't see how it would work. I have no ability to add a variable to the "filter by selected characteristics" option on the broadcaster setting - it only accepts values. If you mean using another option here, "Filter by control query" then it also doesn't look like an option to me. I would have to create multiple control queries for every single user and use them to control the original query?

[former_member492038]

No I mean directly within the Query you are broadcasting. Can you not add a replacement path variable to the characteristic restrictions directly within the Query?

[Former Member]

I think I am beginning to understand what you are saying. Do you mean that if the 0PROJECT gets filtered at query level, the broadcaster will recognize this filter?

But doesn't that mean that I have to create multiple control queries for all my users to act as replacement paths for 0PROJECT in each user's broadcaster setting? Say, I run the main query for user A - I need to run a control query to retrieve user A's project first and add them as filter to my main query. The control query would have to be hardcoded to run for that particular user A, so that I can use it in my replacement path. Then I would need to repeat the process for all my users...

[kohesco]

Hi,

have you the ability the use webi on top of your bex query (via dynamic recipients, you could easily match this issues) and you could this case as a stepping stone to the BI Launchpad and Webi Environment

grtz

Koen

[former_member492038]

Try setting up a replacement path variable on 0PROJECT referencing your query that gives the projects you want and use that in the characteristic restrictions of the query you are broadcasting