| Both sides previous revision Previous revision Next revision | Previous revision |
| docs:8000_appendices:0200_known_issues [2023/02/26 22:07] – sean | docs:8000_appendices:0200_known_issues [2023/05/10 07:25] (current) – sean |
|---|
| | {{tag>Known_Issues}} |
| | [<10>] |
| ====== Appendix B. Known Bugs and Limitations ====== | ====== Appendix B. Known Bugs and Limitations ====== |
| | {{page>:admin:addpage:bugissue&showheader}} |
| |
| The following table lists all known problems and limitations of the Aware IM software and suggests workarounds where possible: | <invisible> This is the template for INHERITED known issues pages - add a tag to Issue: to allow this to show on the tagged page</invisible> |
| | |
| ^ Problem/Limitation Description | ^ Workaround ^ | |
| | Arithmetic operations with dates are not supported in ''[[a_f:a:find|FIND]]'' action, for example using the following will not work:<code aim>FIND Account WHERE Account.Date=CURRENT_DATE-1 </code> | | Use functions with dates (such as ''[[a_f:f:af:date_add|DATE_ADD]]'') instead of arithmetic operations, for example:<code aim>FIND Account WHERE Account.Date= DATE_ADD(CURRENT_DATE,-1) </code> | | |
| | The following functions and expressions are not supported if used in queries:\\ ''WAS CHANGED''\\ ''WAS CHANGED TO''\\ ''TYPE''\\ ''OLD_VALUE'' | | None | | |
| | The following functions are supported only in Cloudscape/Derby database:\\ ''WORD_NUMBER''\\ ''WORDS_FROM_LEFT''\\ ''WORDS_FROM_RIGHT'' | | None | | |
| | Printing of documents of HTML type from rules is not supported | | None | | |
| | Printing of documents of MS Excel type from rules is not supported under Linux and Mac OS X operating systems | | None | | |
| | Documents of MS Word type are not supported under Linux and Mac OS X operating systems (MS Word XML format can be used instead if browsers are running on the Windows platform) | | None | | |
| | If the //**Aware IM**// Server is started when either LAN or Internet connection is up and then either LAN goes down or Internet is disconnected, the server goes down too | | Start the //**Aware IM**// Server within the configuration that you intend to work with. For example, if you only use dial-up Internet connection occasionally make sure that you start the //**Aware IM**// Server first and then connect to the Internet. This way when you disconnect from the Internet //**Aware IM**// will continue to work properly. | | |
| | If two business objects are related through a parent/child relationship (see [[docs:2000_concepts:0200_basics:0400_reference_attributes|Reference Attributes]]) and the reference attribute to a child is defined as “Value must be provided” it is impossible to add a new child instance from a form of the parent instance using Add New button (see [[Working with References in the Operation Mode]]) | | Do not force “Value must be provided” flag for reference attributes or create child instance first and then add it to a parent using Add button. | | |
| | If you drag the bottom line of the Summary pane in the Report/Presentation Designer the height of the Summary band is not changed even though it appears visually that it is. | | Change height of the Summary band using Band Properties – see [[docs:2500_config_apps:4200_report_designer:1300_set_props#Setting_Band_Properties|Setting Band Properties]] | | |
| | Sorting on reference attributes in a query will not work if query searches business object group. For example, sorting in the following query will not work if Account is business object group:<code aim>FIND Account ORDER BY Account.Owner.Name </code> | | Define a shortcut attribute and sort by it, for example:<code aim>FIND Account ORDER BY Account.OwnerName </code> Where ''OwnerName'' is the shortcut to ''Account.Owner.Name'' | | |
| | Checking for ''UNDEFINED'' value of a multiple reference attribute (see Reference Attributes) in queries does not work correctly. For example, the following will not work:<code aim>FIND Account WHERE Account.Transactions IS UNDEFINED </code> | | Use ''EXISTS'' or ''COUNT'' expressions, for example<code aim>FIND Account WHERE COUNT Transaction WHERE (Transaction IN Account.Transactions) = 0 </code> | | |
| | ''MIN'', ''MAX'' and ''AVG'' expressions are not supported if used in subqueries on groups. For example the following query is not supported if Transaction is a group:<code aim>FIND Account WHERE (COUNT Transaction WHERE (MAX.Transaction.Amount = 1000)) </code> | | Avoid using these expressions in subqueries | | |
| | Negated ''IN'' expression is not supported in queries. For example, the following expression is not supported:<code aim>FIND Event WHERE NOT(LoggedInMember IN Event.Participants) </code> | | In many cases the negated ''IN'' expression can be replaced by using the equivalent ''COUNT'' or ''EXISTS'' expression, for example:<code aim>FIND Event WHERE COUNT Member WHERE( Member IN Event.Participants AND Member=LoggedInMember) = 0 </code> | | |
| | ''IN'' expressions using complex identifier of the reference list are not supported if used in subqueries. For example, the following query is not supported:<code aim>FIND Client WHERE (COUNT Account WHERE (Account IN Client.Carrier.Accounts) > 3) </code> Note that the following query is supported: <code aim>FIND Client WHERE (COUNT Account WHERE (Account IN Client.Accounts)>3) </code> | | Avoid using such constructs in queries | | |
| | Dragging bands in Report Designer to change their height is not supported on Mac OS X | | Hold down Apple key and click on the band’s header to bring up the bands property dialog. Specify the height of the band in the dialog | | |
| |
| | {{tagtopic>known_issues&showheader&exclude=/c_template/}} |
| |