In this section: |
The following is a known issue in the WebFOCUS Environments area:
You can set global amper variables in the WebFOCUS Environments area, but you cannot save them. If you set a global amper variable in a procedure it will run, but if you create another procedure and run it to call the global amper variable, the following message appears:
0 ERROR AT OR NEAR LINE 11 IN PROCEDURE MEMFEX FOCEXEC * (FOC295) A VALUE IS MISSING FOR: & COUNTRY
You can set and save global amper variables in the Projects area.
The following are known issues when using the create synonym feature:
When using the Synonym Editor to add dimensions to an existing Master File, some of the dimensions and fields added may not be visible when the file is reopened in the Modeling View of Synonym Editor, or when the file is used in Report Painter. To ensure that these dimensions are visible, open the Master File using the Text Editor and remove the lines at bottom of the file that start with the text HIERARCHY =.
The following are known issues associated with metadata:
Note that there are cases where a message may not be displayed, for example, when trying to open a Master File in the Synonym Editor.
While using the Join tool, if you create a Where-based join with a parameter as a part of a Where condition you receive the message:
FOC295:A VALUE IS MISSING FOR:XXX
If you attempt to report against this join, a parsing error will occur in the Master File.
The following are known issues when working with graphs in Developer Studio:
These expressions are not currently supported in graph requests in Developer Studio.
Page cannot be displayed.
The following are known issues and enhancements for HTML Composer:
As of Version 7 Release 7, if you do not enable the Show layout items only check box when you import an existing PDF report using the Import Existing Procedure option, a FOCUS error may be generated in the PDF Layout preview. Although the error appears in the PDF Layout preview, the PDF report runs correctly.
If you open the Procedure Viewer in the Managed Reporting area of Developer Studio and use the Command Password option to provide the password to access a Master File with DBA security, the setting is not applied. As a result, a user access error occurs if you execute a request in the Procedure Viewer against the Master File with DBA security or if you try to open any of the tools using that Master File. You can add the setting SET PASS=DBA_PASSWORD at the top of the procedure as an alternative.
You cannot run an Update Assist application when you right-click an HTML page and choose the Run on Reporting Server option. This option will be removed in a future release. However, you can still use the Run on Reporting Server option when you run an Update Assist Navigation page.
WebFOCUS |