versago:known_deficiencies
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
versago:known_deficiencies [2019/07/31 13:38] runger [Introduction] |
versago:known_deficiencies [2019/08/01 13:12] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Introduction ====== | + | This page describes |
| - | + | ||
| - | This document identifies | + | |
| ====== Deficiencies ====== | ====== Deficiencies ====== | ||
| - | | + | |
| - | - DATEADD calculation does not produce results when used in a Grid Control field in Forms (v2). | + | |
| - | - DATEDIFF calculations are different between header section and grid rows in Forms (v2). | + | |
| - | - Numeric input is incorrect based on select culture in Forms (v2). | + | |
| - | - No error message is displayed if no output fields are defined in Lookup in Forms (v2). At least one output field is required. | + | |
| - | - Opening an existing form record (Forms v2) with more than 78 data fields does not display any data. | + | |
| - | - Changing the format of a row with a Grid Control in Forms (v2) causes the control to be lost but it cannot be used again. | + | |
| - | - When defining a Link in a Report to be in a new column the Admin Console allows selecting an existing column. It should not. | + | |
| - | - Lookup reports in a detail row cannot use values from the header field as parameters. The workaround is to have a column in the detail row table to match the column in the header. Use the {formdata.$...} variable to copy the header value into the row, and use the row value in the lookup. | + | |
versago/known_deficiencies.1564594691.txt.gz · Last modified: 2019/07/31 13:38 by runger
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
