Question What are the known issues with the Query Builder in Symantec Management Platform 7.0 SP2?
The Query Builder is a user-friendly tool that lets you create resource queries for reports and filters. A resource query is based on the tables that are available in the CMDB. The Query Builder provides a standard template and lets you select the tables and fields that you want to use. You do not need any SQL knowledge to define a resource query. The resource query is converted to SQL automatically, and the SQL is run on the CMDB to extract the appropriate resources.
The following table lists all of the known issues with the Query Builder in Symantec Management Platform 7.0 SP2. Where appropriate, a link to the corresponding KnowledgeBase article is included.
KB Article ID
When you generate reports using a specified date range, the time for both the start and end date is assumed to be 12:00 midnight on the previous day
Therefore, all the data for the start date will be included in the report, but no data for the end date. For example, if the end date is set as December 12, the report will include data up to midnight on December 11. No data from December 12 is included.
The Query Builder does not let you add conditions to joins
When you are using the Query Builder to create a report, you cannot add conditions to joins.
Report names are limited to a maximum of 250 characters
The maximum number of characters that you can have in a report name is 250. The maximum number that you can have in a report description is 512. Any extra characters that you enter in the Name or Description field are not displayed.
The Sort Direction of a Field in a report query is not saved unless a Sort Order is also specified
Setting the sort direction of a field in a report query has no effect unless the sort order is also specified. There is currently no check on this so, if you set a sort direction with no sort order, the sort direction setting is reset to the default.
Substitution parameters are not passed in a right-click action when it opens in a virtual window
If a right-click action (also known as an item task) is set to open in a virtual window, any substitution parameters that are defined for the action are not passed to the virtual window when the right-click action is performed.
The context menu does not work on report chart views
You can configure a report drilldown to show the context menu on a chart view. However, when you save the report and attempt to show the context menu on the chart view, the menu does not appear.
Text operands that you add to a filter expression are not being applied correctly to the query
This issue occurs when you are specifying a filter query in the Query Builder and are configuring filter expressions on the Filter Expressions tab. If you switch to Advanced Mode you can specify the filter expression type, value, and operands. However, if you specify a text operand, it is not applied correctly to the query when you save the changes.
When using the Query Builder to create or modify a report, clicking Apply disables some of the functionality of the Fields tab
After you have clicked Apply, an error message appears when you attempt to add any new fields, or edit an existing field. To restore the full functionality of the Fields tab, you need to click Save Changes to save the report, and then click Edit to return to editing mode.
The Context menu sometimes fails to load for results of a new resource report
When you create a new resource report using the Query Builder, the context (right-click) menu is not available in the results until you have explicitly selected the ShowContextMenu drilldown item in the Drilldowns tab. If you do not open the Drilldowns tab when creating and configuring the new report, when you right-click on an item in the report results, the context menu fails to load.
Report filter conditions are sometimes lost when you edit the report in the Query Builder
When you create a report using the Query Builder, you can specify filter conditions in the Filter Expressions tab. However, when you later edit the report, some filter conditions may be dropped from the report query. This happens whether or not you opened the Filter Expressions tab: when you save the modified report, some conditions may no longer appear in the report query.