250 Byte query parameter limit?
We updated the parameters in a project dashboard viewlet for Open vs
Closed Work Items. There are many parameters selected, and just a few
excluded in the GUI. Trying to save results in this popup:
The number of parameters selected exceeds the allowable limit:
1737 bytes > 250 bytes. The selected parameters were not updated.
Is there a way around this?
We tried creating a separate shared query which does run OK, but that
can't be used on a project-level dashboard.
Thanks!
Closed Work Items. There are many parameters selected, and just a few
excluded in the GUI. Trying to save results in this popup:
The number of parameters selected exceeds the allowable limit:
1737 bytes > 250 bytes. The selected parameters were not updated.
Is there a way around this?
We tried creating a separate shared query which does run OK, but that
can't be used on a project-level dashboard.
Thanks!
4 answers
On 4/10/2009 7:34 AM, Mark Ingebretson wrote:
This seems to be a restriction due to the way the parameters are stored
in the database. can you please open a work item for this, and assign it
to the Reports component? We will see if there's something we can do to
address the problem.
Thanks,
james
Jazz Reports Team Lead
We updated the parameters in a project dashboard viewlet for Open vs
Closed Work Items. There are many parameters selected, and just a few
excluded in the GUI. Trying to save results in this popup:
The number of parameters selected exceeds the allowable limit:
1737 bytes > 250 bytes. The selected parameters were not updated.
Is there a way around this?
We tried creating a separate shared query which does run OK, but that
can't be used on a project-level dashboard.
Thanks!
This seems to be a restriction due to the way the parameters are stored
in the database. can you please open a work item for this, and assign it
to the Reports component? We will see if there's something we can do to
address the problem.
Thanks,
james
Jazz Reports Team Lead
James, I think this was a dashboard problem in how dashboard parameters were persisted in 1.0. In 2.0 the dashboard will use report queries to persist its parameters. So I think the problem will go away since the reports component does not impose the 250 byte limit on its queries. I am not sure about non-report based viewlets.
Rafik is right. This issue should no longer be a problem in 2.0.
In 1.0, the dashboard was storing all the parameters itself
e.g. Team Areas
"/Jazz Development/Work Items,/Jazz Development/Reports, ..."
After a number of parameter selections, the limit was exceeded
In 2.0, the dashboard is now storing just the Report Query UUID instead of the raw parameters.
In 1.0, the dashboard was storing all the parameters itself
e.g. Team Areas
"/Jazz Development/Work Items,/Jazz Development/Reports, ..."
After a number of parameter selections, the limit was exceeded
In 2.0, the dashboard is now storing just the Report Query UUID instead of the raw parameters.
Thanks, James. Work item created:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=78430
Mark
James Moody wrote:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=78430
Mark
James Moody wrote:
This seems to be a restriction due to the way the parameters are stored
in the database. can you please open a work item for this, and assign it
to the Reports component? We will see if there's something we can do to
address the problem.