Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Listing report will not return values with two date fields and a binary field set to QAR
One binary field configured for checkbox or radio button style All fields set to Query-at-Runtime ( QAR ) A filter is set on both date fields with opposing equalities (e.g. Start Date > QAR and End Date < QAR).
CMS-XML Reports with more than 2 'query at runtime' search filters for the same field may not return any data
As an example: Submit Date >= ( Query At Runtime ) and
CMS-XML Error in Distribution Reports when using query at runtime on text fields : An error occurred while processing the last request. Please contact your administrator.The server was processing this URL when this message was created:http://win8r2dc/tmtrack/...
Error in Distribution Reports when using query at runtime on text fields : An error occurred while processing the last request. Please contact your administrator.The server was processing this URL when this message was created:http://win8r2dc/tmtrack/...
CMS-XML A report with two filters on a date field and one on a binary field set to QAR will not return results.
Here is an example of a report with filters that does not work: Submit date > QAR Submit date < QAR
CMS-XML Query at runtime report returning error
(1) Create a query at runtime report that queries the Project field (need more than 250 projects in the db). ( 2 ) Run report , choose Find with no keywords. (3) When it says that there are more than 250 selections, make sure that is selected.
CMS-XML Reports: Advanced SQL filters do not work well with Query at Runtime on the same report
you may see behaviour similar to that described below. 1. Create two reports with QAR field at Basic conditions and ASQL condition, which could be the following: @where TS_TITLE like '%a%'
CMS-XML Query At Runtime reports using date/time fields for a range produce no results when there should be
If Date/Time fields are used in reports for Query at Runtime and are for a range then the results can be incorrect. e.g. If wish to get all items between DateField <= date1 and >= date 2 then you may get no results when some are expected. TeamTrack is incorrectly building the SQL and transposing the values so the condition is impossible to be satisfied.
CMS-XML Usability issue when creating report with (Query at Runtime)
2 . Note that under "Field Values" box, if you selected ( Query At Runtime ), you can not move it to the right, and you may think that you can not add ( Query at Runtime ) for this field for your report (see attached screenshot). How it works is, you can just select (Query at Runtime) from the left and it will be added for your report. Expected results: User should be able to move (Query at Runtime) to the right to avoid confusion
CMS-XML Creating a report with two matching runtime fields caused user report issues until system refreshed
If you have a listing report with two matching query at runtime fields on an aux table then when you try "FIND" on this field you will get "error on page" from IE and expanding that “form.Report Type is null or not an object” from qbetop.js. The "find" seems to never finish and also you cannot create a listing report with any search criteria (all search criteria options are blank even for inactive/active). To recreate:
CMS-XML An error occurred while processing the last reques - .on drill-down in some trend and duration reports when using Query at Runtime for Start and End dates
1) Create any graphical report with QAR in Start/End date fields e.g. Open and Completed, backlog trend report 2 ) Save and Run report ; 3) Drill-down to some value:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs