I've been stuck with this problems for 2 days now and I don't know how to corner it.
Basicly, I'm building list of report URL's with provided parameters in URL so I can run them without selecting each checkbox. I've found the way how to select most of the values without problem, but sometimes I want to choose "(Select All)" option from dropdown, but I don't know how. What do I need to pass in parameter so that it would select all for rendering a report?
Do you have any suggestions?
for example,this works for me:
&Company=xxxx&Partner=yyyy&Name=3&rs:Command=Render
Default the Parameter(s) to NULL in the RDL. Then you can simply call the report without specifying a value for the parameter and it will automatically pass NULL into the proc.
Then in your proc you will need to change your predicate (probably, although no code has been provided) to something like this:
Where (tablealias.Company = #Company or #Company is NULL)
AND (tablealias.partner = #Partner or #Partner is NULL)
etc
So taking company as an example, if you specify a value in the URL it will search for that value in the proc, if you don't it will return regardless of company.
Related
I need to get all issues by version id. My query is like:
http://archwork:2990/jira/rest/api/2/search\?jql\=project\=GP+and+fixVersion\=10001
working fine, but I want to get issues by VERSION
Link like:
http://archwork:2990/jira/rest/api/2/search\?jql\=project\=GP+and+version\=10001
returned "Field 'version' does not exist or you do not have permission to view it."
The two built-in version fields in JIRA can be accessed in JQL as fixVersion and affectedVersion. I suspect that you want the latter.
If you have another custom field (which is a version-type field) that you want to query, the error message suggests that you may not be using the correct name for it. The best way to check this is to type your JQL into JIRA's Issue Navigator manually (in the advanced search) and to take advantage of the dropdown box with field name suggestions to get the correct field name.
One way to bypass the problem of determining the correct JQL field name (which sometimes requires quoting, which gets slightly more messy if you are also URL-encoding the result) is to simply refer to a field by the custom field ID instead.
You can find the CF ID of a field by going to Admin->Issues->Custom Fields, finding the appropriate custom field, mousing over the "Configure" link, and then looking at the URL query parameter for customFieldId, and then use the syntax cf[xxxxxx] in your JQL instead of the field name, where xxxxxx is the custom field number.
I have a report that is being passed parameters through the URL, but would like to have the report load by default before the user has to click the 'View Report' button. I have rs:Command=Render in the URL but this doesn't seem to be doing it. Is there another tag that I am missing here? The URL is currently as follows:
https://server/subfolder/viewreport.aspx?Report%Name&rs:Command=Render&Parameter1=Value1&Parameter2=Value2
The report comes up with the appropriate values selected by default, as passed above, but it does not run until I hit View Report. Do I need to specify all the other parameters in the report through the URL in order for it to run by default, even though those parameters already have default values?
Found it, the report renders automatically as long as all parameters have a 'Default' value specified. Two text parameters in the report needed to have their default expressions set to =""
I would like to create a work item query where the user is always asked to pass the value of the argument he wants.
For example:
Team project= #Project
And Work Item Type = Bug
and State = ?
Then the user is asked for which state he wants to get the results.
Any ideas?
Queries does not support parameters.
What you can do:
Use TFS Reporting
Export query to Excel
Use you own WIQL query
I have found in sfDoctrineApplyPlugin a template called applyAfter.php
that shows a message like "You have registered ok..." after the users apply for an account. It is called from the sfApply/apply action this way: "return 'After';" when the apply form is valid.
What kind of template is that? I never saw that way (return 'After';) of calling a template. Can someone give me info about that?
Second question: I show a layout with a language select when the the
apply form is printed. I wouldn't like to show that language select in
the page that shows the message "You have registered ok...". As the action
is the same in the both pages (sfApply/apply), what should i do to hide
the language select in the verification page?
Javi
The function returns the string 'After' to the caller. The caller always seems to be as follows: $this->widgetSchema->setNameFormat('sfApplyResetRequest[%s]');
So, the string 'After' is being used in conjunction with the setNameFormat function (which is part of the symfony libraries). All it is doing, is setting the 'name' attribute for the form. More information on this function here.
For your second question, you could simply add an IF statement, to check to see if the current route is the one that you do not want to display the language select on. If it isn't, then display the language select.
You can verify the current route with the following code:
sfContext::getInstance()->getRouting()->getCurrentRouteName();
I have a slight problem with getting the options within the select tag. Some background information; This is a report, and as such the select options will vary depending on what is stored on the DB depending on some conditions. So, I'm using observe field to get the selected option, BUT, I need to get all the options because I want render that same report with a) the selected option that was chosen the first time and the remaining ones.
select "price", "desc", #desc, {:prompt => 'All'}
I'm obviously observing the field, to display the result, so the variable #desc is the hash with the all the values.
Can you help me get hash to be sent to the controller, and how can I have the selected option selected in the hash to be sent back to the view....
Cheers
You have the options already, so where'd you get them? Are they report specific? If so, send the report_id back so you can look all of them up again, then you can select the selected one.
You can't (easily) get all of the options in a select list. Technically, you could write a javascript function that would grab all of them and send them as parameters. Or, you could write them out as a hidden field and submit that with the request, but both of those ways are ugly.