| | Known Issues
Table Widget Editor
- Some planned features are not yet implemented:
|
| |
-
- There is no option to specify that a field (column) should perform a data lookup. Consequently, ILF code must be used in the Post PCF Read event point to manually retrieve data.
Table Widget Runtime |
|
<
< |
- The table widget is only suitable for displaying a relatively small number of records. Otherwise, the time needed to download the records to the client can get excessive. Records can only be loaded at a rate of about 2,000 records per second (depending on network speed and load). Consequently, the table widget probably cannot be used as a record selector for larger records sets. For example, the time needed to load about 30,000 records is about 15 seconds.
|
>
> |
- Performance may be an issue if you are loading a large number of records, depending on network speed, server load, amount of data and desktop processor. For example, loading 10,000 records from DMO CONTACT takes 2-3 seconds. Reading all 10,000 records to find the contacts for a selected Prospect is less than a second (using --- INCLUDE RECORD in Post PCF Read of the Table Resource).
|
| |
- Appx navigation keys take priority when in the Table Widget. Any key that would set --- OPTION (eg, Page Up/Page Down) will be returned to your input process and will not affect the table widget. Other keys, such as cursor up/down, can be used to navigate in the Table Widget.
- Date columns sort based on the displayed value, not the actual date. For example, dates displayed as mm/dd/yy will not sort in date order.
- At runtime, you cannot click on a row to select it unless all modifiable fields on the screen have satisfied the hard edits which are enforced by the engine. For example, an invalid character in a numeric field on the same screen will prevent you from selecting a record.
|
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.