In this section: |
|
When using the Upload utility with Microsoft Excel files, the time required to complete the upload depends on the machine configuration (for example, type of processor, amount of memory, and speed). The Upload utility supports Microsoft Excel files up to five megabytes. It is recommended that for up to a five megabyte Microsoft Excel file, you set the max Java memory heap size to two gigabytes on the application server.
The following are known issues and/or behaviors in the WebFOCUS Environments area:
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:
"Error Code: 401 The requested resource requires user authentication."
The following is an available solution:
In the DMC, if you open an Access File for a synonym while in the Modeling View of Synonym Editor and you click the Text View tab, you get an error that says:
Encountered an improper argument
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:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4846680
These expressions are not currently supported in graph requests in Developer Studio.
Page cannot be displayed.
The following are known issues when using Report Painter in Developer Studio:
In Report Painter, some fonts may not change appearance after you change the default font style.
The following are known issues and enhancements for the HTML Composer:
The following are known issues with the Document Composer:
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.
Intermittently, Developer Studio fails to open large files which prevents further report development. If the Master File is large, a timeout may occur while waiting for the reporting server and WFServlet to send a response. The Developer Studio communication layer (WFSCom) uses a specific code from Microsoft to set timeout values for requests. If the Developer Studio communication layer does not get a response from a Web server within the timeout period, a message is displayed. The timeout value for the request is normally set to infinite, however, the Microsoft Windows API function that sets timeout values for requests is not working properly. For more information, you can visit the Microsoft Support site at:
There are some cases where IIS truncates certain XML responses and impacts the behavior of Developer Studio. For example, you may not be able to see all available applications and requests will fail. The only known alternative is to try reinstalling IIS or you can try switching to another Web or application server.
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.
The following are known issues when using PushOK CVS as the Source Control product in Developer Studio:
When the status of the module shows Status unknown, the module usually does not exist, so it has to first be created. It is suggested to copy the CVS Module string right before creating the module and paste it back if the string has changed before accepting the selected module.
PushOK CVS enables you to retrieve an older version of a file. In order to get an older version, you must select the line for that version in the tree control. Selecting the check box next to the file version will not retrieve the file.
In some instances the read-only (R/O) file attribute is set, even if the file has to be read-write (R/W) by the virtue of being checked out. This behavior is generated by a fix for some problems encountered with CVS (for example, not being able to get a latest version if the file was modified out of SCC control). It is suggested to open up the Properties dialog box and uncheck the Read-only check box.
This happens only in certain instances. It is suggested to shut down the application and start it again.
WebFOCUS |