Report builder diferences in the parameters concept makes multiquery reports unusable
Hi There,
I'm upgraded from version 11 to version 12 recently with a fantastic
perception of evolution of the product. Only with one exception:
In version 12 a report parameter updates the search criteria of a query
including the value and the operator, in previous version this doesn't
occur.
RESULT:
Report parameter need to only change values and not entiry search criteria.
An example of it:
query1:
select count(*) from stock where startdate < :dateparam
query2:
select count(*) from stock where startdate = :dateparam
query3:
select count(*) from stock where startdate > :dateparam
After inserting a date for dateparam
All the staments will be changed to :
query1:
select count(*) from stock where startdate = :dateparam
query2:
select count(*) from stock where startdate = :dateparam
query3:
select count(*) from stock where startdate = :dateparam
Sorry. It's a wrong concept.
For me : operators need to remain in each query and values are updated from
parameters.
Thanks
Francisco Ruiz
I'm upgraded from version 11 to version 12 recently with a fantastic
perception of evolution of the product. Only with one exception:
In version 12 a report parameter updates the search criteria of a query
including the value and the operator, in previous version this doesn't
occur.
RESULT:
Report parameter need to only change values and not entiry search criteria.
An example of it:
query1:
select count(*) from stock where startdate < :dateparam
query2:
select count(*) from stock where startdate = :dateparam
query3:
select count(*) from stock where startdate > :dateparam
After inserting a date for dateparam
All the staments will be changed to :
query1:
select count(*) from stock where startdate = :dateparam
query2:
select count(*) from stock where startdate = :dateparam
query3:
select count(*) from stock where startdate = :dateparam
Sorry. It's a wrong concept.
For me : operators need to remain in each query and values are updated from
parameters.
Thanks
Francisco Ruiz
This discussion has been closed.
Comments
search criteria field alias value. For example, set it to 'Start Date'.
When Parameter.AutoSearchSettings.FieldAlias matches the search criteria
field alias, the parameter is very tightly bound.
--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
And congratulations for the step ahead in report builder.
Francisco Ruiz
Thanks!
--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com