Infor ERP Office Integration Technical Notes

# Table of Contents

- Known Bugs/Issues
- Bugfix overview
- Troubleshooting

# Known Bugs/Issues

· Maximum number of ERP related fields on a template are limited to 100. If a template exceeds this number the message "The template has too many fields (>100)' will be displayed.

· Templates based on a 1 to n relation of ERP related tables (f.e. header, lines and deliveries of a sales order) cannot be handled (correctly) by the 2.0 release.

# Bugfix overview

This section contains an overview of all bugs that have been fixed in the 1.1 release after the GA release. It provides information in which release what bug has been solved and what Scopus defects, cases and solutions are related to the bug fix.
The current release number of the Infor ERP Office Integration can be found in the (Control Panel) Add/Remove Programs dialog of Windows and the ‘About dialogs’ within the application.

### ID

Description

Scopus
Case(s)

Scopus

Defect(s)

Scopus Solution(s)

Release
required

1 | Dialog for testing templates improved. Datatypes 'Enumerate' and 'Date' can be handled more user friendly. | - | - | - | 2.00.0135
2 | Trying to create a new template on a device that was not ready resulted in a runtime error and aborted the application. | - | - | - | 2.00.0135
3 | On AS400 systems paths were not created correctly. | - | - | - | 2.00.0135
4 | Tables, which were removed in 'Insert Baan Fields' dialog by the option 'Remove Table' could not be added anymore. | - | - | - | 2.00.0135
5 | Update of default selection values in 'Test Baan Template' dialog went wrong in case more than one table was used for a template. The primary index of the related Baan table 'Default values template' (ntwrd050) is extended with the field 'Baan table' (ntwrd050.btbl). | - | - | - | 2.00.0135
6 | Installation (client): - Default component selection changed. Now (only) components for end users are used as default selection. - Sample templates Triton Service as installation component removed. Export/delivery now possible by the new functionality in Baan to exchange Office integration related templates. | - | - | - | 2.00.0135
7 | Divergent problems related to multibyte characters (e.g. Japanese). | - | 115504 | - | 2.00.0135
8 | Processing of data by the ‘Document Creator’ went wrong in case of certain regional number/currency format settings. | - | 121330 124399 | - | 2.00.0135
9 | Adding fields to an already existing template could result in the error message “This key is already associated with an element of this collection". | - | 123992 | - | 2.00.0135
10 | Parameters Baan Automation Server (BAS) cannot be changed in Baan. BAS no longer actual in release 2.0 as middleware. Concerning session(s) expired. | - | 124414 | - | 2.00.0135
11 | When MS Excel templates published with the option "BaanERP sessions only" are copied to a different template and the new template is published with the option "Microsoft Excel only", the new template is accessible from BaanERP sessions. | - | 125518 | - | 2.00.0135
12 | Disabling a filter using the “cell value” option not possible (filter still active) | - | 125615 | - | 2.00.0135
13 | Divergent problems related to the Baan Automation Server. BAS no longer actual in release 2.0 as middleware. | - | 125481 126045 | - | 2.00.0135
14 | Using the update mode (write back to Baan) in MS Excel sheets with more then 99 lines did not update the records after line 99. | - | 126171 | - | 2.00.0135
15 | Path of server directory cannot be changed (changes are not updated in Baan) in the Baan session ‘Office Parameters’ (ntint0500m000). | - | 127131 | - | 2.00.0135
16 | Performance during update mode (write back to Baan) improved. | - | 129950 | - | 2.00.0135
17 | Installation (client): Check on presence of previous installed version(s) added. | - | - | - | 2.00.0136
18 | Installation (client): - Update functionality added. From version 2.00 it is possible to update an already installed version. - Documentation (readme files (html) and user manual (pdf)) added. | - | - | 134254 | 2.00.0137
19 | Table description could not contain multibyte characters | - | 133667 | 132698 134254 | 2.00.0137
20 | Translation miscellaneous questions improved. | - | 136030 | 134254 | 2.00.0137
21 | Miscellaneous improvements related to the processing of (Baan) textfields: - Multiple textlines supported - Maximum length extended from 512 to 1024 positions (incl. separators). | - | 132921 134856 | 134254 | 2.00.0137
22 | Miscellaneous improvements regarding the usage of decimal/thousand symbols (.,) related to the regional settings and the MS Excel cell format. | - | 134686 | 134254 | 2.00.0137
23 | Datafields of type (multibyte) string were during the creation of a document/workbook truncated to a length of 85. Now the maximum output is extended to 256 positions. | - | 132386 | 134254 | 2.00.0137
24 | ‘Index out of dims’ could occur during import of templates (ntint0201m000) | - | - | 135714 | 2.00.0138
25 | Retry handling optimized during ‘Save to Baan’ transaction. | - | - | 135714 | 2.00.0138
26 | Table description not displayed correctly in case of (Baan) language switch. Selected tables and table descriptions were stored (as a kind of MRU-list) in the registry. Switching the (Baan) language setting resulted in an incorrect display of the table description. Now the table description is no longer stored in the registry but determined runtime, so always the most actual (and language related) description is presented. | - | - | 135714 | 2.00.0138
27 | Processing of templates with multibyte characters in template name and/or description implemented. Part of the solution is a change in the domains ‘ntdesc’ and ‘nttmpl’ used in the table ‘Office Templates’ (ntwrd010). RECONFIGURATION IS NECESSARY. | - | 115504 133669 | 135714 | 2.00.0138
28 | Processing records based on a MS Word template with the property ‘multi-document’ resulted in the error message ‘Invalid property value’ for all documents except the first one. | - | 137573 | 135714 | 2.00.0138
29 | BaanERP 6.0 compatible version introduced: - New naming of application processed in client setup. - License Override mechanism OpenWorld implemented. IMPORTANT: - The (client) installation of version 2.4 of the Open World adapter is required.

- It’s NOT possible to update a previous installed (2.0) version of the iBaan Integration Pack – MS Office with this new version, so a full install of this version necessary.

-

-

-

2.00.0139

30 | Copyright related contents changed to "SSA Global Technologies". Present license dialog removed from setup. | - | - | - | 2.00.0140
31 | Filters based on MS Excel cell didn’t function properly (error 302 during execute of template). | - | 141497 | 141183 | 2.00.0141
32 | New SSA related dialogs, naming etc added. | - | - | - | 2.00.0142
33 | - New SSA webtop 3.0 enabled version introduced. The document/workbook generation part for end users has been redesigned. It does not require a client installation anymore, except for MS Excel end users, which need to perform actions directly from the client (like creating a new workbook, (undo) read from SSA or save to SSA).

- SSA related dialogs, naming etc changed (no conversion of existing templates!).

- User manual no longer installed with client setup (because installation client software no longer always necessary).

-

-

142184

2.00.0142

34 | New SSA related icons implemented. | - | - | - | 2.00.0143
35 | Adding table in 'Insert ERP Fields Wizard' resulted in runtime error (35601). | - | 148227 | 144832 | 2.00.0144
36 | Mapping of table(field)s (containing combined field(s)) could result in “Array Index Out Of Bounds Exception” error. | - | 148390 | 146030 | -
37 | Usage of cell filter with fields of type enumerate resulted in “Object variable or with block variable not set” and/or “This key is already associated with an element of this collection” error. | - | 148762 | 146039 | 2.00.0145
38 | Miscellaneous minor adjustments client install: - Minimize during create instance of MS Excel/Word didn't work properly in XP release. - Cancel option during configuration of MS Excel/Word now disabled. - Error handling during abort and self-registration of files improved. | - | - | - | 2.00.0146
39 | Field properties (read-only/read-write) not always updated (correctly). | - | - | - | 2.00.0146
40 | T he Microsoft Java Virtual Machine (MSJVM) is not included with Windows XP SP1a, Windows XP SP2, Windows Server™ 2003, or any future Microsoft software. Due to this self-registration problems can occur during the installation of the client (Java) components. | - | 153361 | 149465 | -
41 | Cell filtering of datatype 'date' corrected. | - | 156786 | 203199 | 2.00.0147
42 | Modifying the filter configuration resulted in a locked process/application. | - | - | 203199 | 2.00.0147
43 | Cell format and display of numeric fields corrected | - | 157438 157438 | 203582 203301 205289 | 2.00.0148 2.00.0149
44 | - Cell filtering did not work in case of end user installations. - “Type mismatch” error could occur on numeric fields. | - | ERP-00000-02058 ERP-00000-02525 | 209240 | 2.00.0150
45 | - Replace COM DLLs by .NET libraries. Template designers need to install Infor Integration 6.2. - New Infor related dialogs, naming, etc. | - | - | - | 2.1.105
46 | Runtime error ‘429: ActiveX component cannot create object’ during start of miscellaneous integration options (like ‘Create New Workbook’) solved. | - | Tech-00000-03280 | 226459 | 2.1.109
47 | Microsoft Vista / Office 2007 compatible version introduced. | - |  | 227104 | 2.1.110
48 | Error message "The key is already associated with an element of the collection" when inserting fields. |  | Tech-00000-04041 | 233229 | 2.1.111
49 | Filter with constraint "is empty" is not saved |  | - | 244370 | 2.1.112
50 | In BFM (Field Mapper) descriptions of related tables in Japanese not completely shown |  | 292485 | 252184 | 2.1.113

# Troubleshooting

· During the installation of the Infor ERP Office Integration the system environment variable 'path' is extended with the Infor ERP Office Integration installation folder. In some cases (f.e. in the German version of Windows 98) semicolons are replaced by spaces in the added part of the variable ‘path’. Replacing the concerning semicolons by spaces after the client installation or avoiding the use of spaces as installation folder during the installation should solve/avoid the problem.