We have implemented index aware functionality in BOXI R2 environment.
We have created condition filter in which we have used primary_key parameter in @promt() syntax and equate this @prompt with id (for e.g. Country_id).
Condition filter syntax:
country_id in @Prompt('Country...?','C','Country\Country',multi,primary_key)
When we used this condition filter at report level, user can able to see LOV of country, and in where clause of final SQL query country ids are appeared. Thus our purpose of using ids instead of name in where clause of SQL query gets fulfilled.
Problem Statement:
But when user try to schedule this report and choose values in prompt while scheduling, county name get reflected (instead of country_id) in where clause of SQL query.
Thus scheduled report dont have any data to show, as we country_ids get equated with Country Name.
We have tried to check the same with 3 different BO XI R2 environment, but got the same o/p as above. But strangely same thing is working in BOXI R 3.1 environment. We need to fix this issue on BOXI R 2 environment.
I think we have used undocumented feature “primary_key” in BOXI R2 SP2 environment, so this issue arised.
I think primary_key parameter feature is not working in BOXI R2 evironment.
The Index Aware feature requires that the user select from the List of Values in order to get the index key. If the user enters a value manually, Index Aware is not used. I suspect that the folks that wrote the code for scheduling reports (and building prompts to react to) did not take IA into account until 3.x.
yes in release note of BO XI R2 SP2 its not documented. however in release note of SP4, I guess it’s documented. so may be in release SP 4, hope that should be taken in account, hopefully.
(but not sure) if anybody having with SP4 can help us. I am not having SP4.
If this issue is resolved in SP4, then we can go ahead with that. (i.e. from SP2 to SP4)
Hi, we are experiencing almost the same problem, and we are using XIR2 SP4
We can schedule a report with index aware prompts, but then we can’t subsequently re-schedule the same instance. We have to create a new schedule from the original instance or it doesn’t work
It generates a DB error as the selected prompt values (for just the index aware prompts) are not populated into the SQL statement
We also have another issue but I’ll create a new post about that (it’s to do with passing parameters to an index aware prompt through the opendocument syntax )
(BOB member since 2008-05-13)
(BOB member since 2007-10-24)
(BOB member since 2002-06-06)
)
(BOB member since 2005-11-21)