Web application provides working only with ready reports. The following features are available:
Manage table and visualizer contents using controls.
Refresh data sources.
Edit and save changed data in tables, if permissions to change source are available.
Add autofilter.
Print report.
IMPORTANT. All functions of appearance setting and report structure are unavailable. The user cannot save or change report appearance.
Depending on the application in use there are the following differences in platform functionality:
| Functionality | Desktop application | Web application |
| Building Report |
|
|
| Working with Ready Report: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conventions:
- functionality is fully available.
- functionality is unavailable.
- functionality is available with specifications of use.
On creating a regular report in the desktop application to further open this report in the web application, follow the recommendations below.
Take into account the following features if you create a report in the desktop application to further open it in the web application:
| Constraint/feature | Recommendation |
| Cell text is wrapped in the report | Set cell width and height to fit to the whole text |
| Conditional formatting defined with histograms, does not show | Use conditional formatting based on color scales or icons |
| Diagonal cell borders cannot be seen | Set borders only using horizontal and vertical borders |
| Hatching cannot be seen | Use image fill or some fill without using the patterns |
| Cell images cannot be aligned | Select the images that fit the cell size |
| Merged cells, that are only partially located in fixed area, while the other part is in a non-fixed area, can be displayed incorrectly | When creating a report, avoid merging cells that are only partially located in fixed area, while the other part is a non-fixed area |
| If rows height is auto adjusted, on export to XLS the text in the row can be partially hidden because fonts in Foresight Analytics Platform and Excel do not match | After selecting the height automatically, manually increase the row height, or do not use autofit at all |
| Multiline headers and footers are trimmed on export to RTF | Use fewer words or make the header/footer font smaller |
| Headers and footers are not exported to HTML | Warn the user that headers and footers cannot be exported before exporting the report to HTML |
| Charts and images can export to PDF incorrectly, if no background is defined for these objects | Define background color for maps and charts, for example, white color |
| Constraint/feature | Recommendation |
| Tooltips are not shown for 3D charts | Select 2D chart types if it is required to show tooltips |
| The Masked String Editor control is not supported | Use the String Editor control and check the entered data |
| Element groups and selection schemas are not available when working with dimension elements | Use hierarchical dictionaries elements of which are already grouped to different levels as data sources for dimensions |
| Information messages called from units used for report event handling, are not supported | Replace information messages with another method of informing the user. For example, show information on a separate report sheet |
| Page break cannot be inserted into a report sheet | Create a report without using page breaks |
| Formulas using OR statement are not exported to XLS. For example: =(C2=0) or (D2=0) | It is recommended to export into XLS format the values calculated by formulas instead of formulas |
See also: