In this section:
The following are known issues in the WebFOCUS language.
Autoprompt correctly lists a value that contains double quotation marks ("), but when selected for a single select list, the request fails with a syntax error. The problem does not occur for a multi-select list control.
In prior releases, MATCH FILE requests did not group verb objects with their sort keys across files. The resulting record was laid out by appending the fields from each file to the resulting record in the HOLD file. The current default behavior is to group verb objects with their sort keys. This can result in the fields being propagated to the HOLD file in a different order and can affect the MATCH results if the request uses the default alias names generated in the HOLD Master File. The advantage of this technique is that it supports HOLD file formats such as FORMAT FOCUS that generate an associated Master File. If you need to invoke the processing from prior releases, issue the following command.
SET MATCHCOLUMNORDER = UNGROUPED
The new option SET ASNAMES = FLIP makes the field name from the original Master File the alias value in the HOLD Master File and generates default field names in the HOLD Master File. For complete information, see the Creating Reports With WebFOCUS Language manual.
A Master File Profile is a FOCEXEC that is invoked whenever the Master File is referenced in a request. If the MFD_PROFILE references itself, an infinite loop can result. For information about using a counter in the MFD_PROFILE request to prevent infinite looping, see the MFD_PROFILE Usage Notes in the Describing Data With WebFOCUS Language manual.
Hierarchical reporting uses BY HIERARCHY syntax to display hierarchies defined in Master Files automatically indented to show the hierarchical relationships between the members. For complete information about hierarchical reporting, see the Creating Reports With WebFOCUS Language manual.
Reports with BY TOTAL and ACROSS, using conditional styling with column notation rather than column name, may apply conditional styling to incorrect columns.
When using a URL attribute with a TYPE=DATA, ACROSSCOLUMN=field declaration, the URL data value of the first ACROSS column is being assigned to all ACROSS columns.
When the size of the LEFTMARGIN is customized, only the first table, which is displayed automatically when the request is run, respects this margin. When the second or lower value for the highest-level sort field is selected from the TOC tree, the default size of the left margin is used.
As a result, when View Entire Report (On/Off) is selected in the TOC tree, two left margin sizes are displayed and a separation of the report into two parts occurs. The first table shows the left margin specified, while all other tables adhere to the default left margin size.
The following are known issues with Accordion By Row reports:
A COMPUTE field with a URL containing a blank space in the value generates a bad workbook.
In EXL2K formatted reports, with headings or footings containing multiple items that are separated by spot markers without spaces, the spot marker adds an additional space between the items within the text in the cell. The workaround is to use XLSX formatted reports, instead.
The following are known issues with EXL2K FORMULA:
FORMAT XML creates an XML output file based on an internal DTD that includes the rows that are displayed in the final report output. For more information, see the Creating Reports With WebFOCUS Language manual.
When OBJECT=BOX and BORDER-STYLE=DOUBLE is used with FORMAT PPTX in StyleSheet syntax, a solid border, instead of a double border, is generated.