MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES

Transcription

1 R ELEASE NOTES Product: Microsoft Dynamics AX Connector 3.0 Last modified: November 13, :11 pm Created by: Development MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES In this document the following Release Notes are discussed: Overview Known Issues Resolved Issues Microsoft Dynamics AX Connector Copyright Bottomline Technologies, Inc All Rights Reserved, Printed in the United States of America Every effort has been made to ensure the accuracy of this manual. Information in this document is subject to change without notice and does not represent a commitment on the part of Bottomline Technologies. Bottomline Technologies makes no warranties with respect to this documentation and disclaims any implied warranties of merchantability or fitness for particular purpose. All software described in this manual is furnished under a license agreement or nondisclosure agreement, and may only be used in accordance with the terms of this agreement. Microsoft Dynamics AX Connector licensee(s) may reproduce Microsoft Dynamics AX Connector instructional documentation as needed for distribution to users of the licensed Microsoft Dynamics AX Connector software. The licensee(s) agrees not to modify, adapt, translate, or otherwise alter the documentation prior to distribution.

2 2 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES Overview Overview This document contains a summary of new features included in Microsoft Dynamics AX Connector 3.0. Microsoft Dynamics AX Connector 3.0 is a Create!form solution that is installed into an existing Microsoft AX implementation. Supported Client Operating Systems Windows XP SP2 Windows Vista (32-bit) SP1 Supported Create!form Components Create!form 6 product suite Supported Third Party Software Adobe Acrobat and Acrobat Reader v7.1 and higher Microsoft Dynamics AX v4.0 SP2 Microsoft Dynamics AX 2009 Latest Microsoft Dynamics AX Connector 3.0 Build Tested

3 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES 3 Automatic Installer New install program which will automatically imports XPOs, deploys label files, compiles forward necessary classes, and deletes intermediate AX projects. This is accomplished by having the AX Client launch several times, each time performing a certain task. The user is only required to click "Yes to All" during imports and to close the AX Client manually after each task is complete. BTDPA NumberSequence Deprecation Previous versions of Microsoft Dynamics AX Connector required that a BTDPA number sequence be created and referenced in order to use the implementation. Utilizing the Number Sequence Framework in Microsoft Dynamics AX requires many manual steps by the user. Microsoft Dynamics AX Connector 3.0 has a more intrinsic method for generating unique ids which will require no additional setup by the user after installation. Here is the list of AOT Objects created to support internal number sequencing: AOT Object Name BT_DPA_TableNumSequence BT_DPA_TableId BT_DPA_NextNum BT_DPA_TableNumSequenceGenerator Object Type Table Int Field Int Field Class Localization of all UI Text All text displayed in the user interface, including various info log messages and modal dialogs, is now localized. This entails having all of the text located in the axdpa[lang-code].ald file, which is readable in a text editor. The following languages are supported:

4 4 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES Language Language Code Label File Name English (United States) en-us axdpaen-us.ald English (U.K.) en-gb axdpaen-gb.ald English (Australia) en-au axdpaen-au.ald English (Canada) en-ca axdpaen-ca.ald English (New Zealand) en-nz axdpaen-nz.ald ENGLISH (IRELAND) en-ie axdpaen-ie.ald English (South Africa) en-za axdpaen-za.ald English (India) en-in axdpaen-in.ald English (Malaysia) en-my axdpaen-my.ald English (Singapore) en-sg axdpaen-sg.ald Spanish (Spain - Modern Sort) es axdpaes.ald French (Standard) fr axdpafr.ald German (Austria) de-at axdpade-at.ald German (Switzerland) de-ch axdpade-ch.ald Dutch (Standard) nl axdpanl.ald Optional Use of Folder Monitor In previous versions of Microsoft Dynamics AX Connector, Folder Monitor was a required component in order to deliver XML output from Microsoft Dynamics AX to Create!form. In Microsoft Dynamics AX Connector 3.0, its use is now optional. XML Output Locations can be specified in the Defaults form and in the delivery destination's Setup tab. Instead of a shared folder path which is watched by Folder Monitor, a shared Create!form enabled print queue path may be entered instead. Removal of XML Optimizer A new XML engine has been implemented to produce XML which will not require addition processing afterwards. Allow Copying/Sharing of Configuration Settings between Company Accounts Configuration settings for the Defaults, Document Processes, and Delivery Destinations forms are stored globally by setting the SaveDataPerCompany

5 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES 5 property for the forms' corresponding tables to No. All company accounts have permission to access and modify the data stored in these tables. Here is the list of tables whose SaveDataPerCompany property is set to No: Table Name BT_DPA_Defaults BT_DPA_Destinatio ns BT_DPA_Destinatio ngrouprestrictions BT_DPA_Destinatio nuserrestrictions BT_DPA_Processes Form Name Defaults Delivery Destinations Delivery Destinations Delivery Destinations Document Processes The data stored in the Enabled Reports form's corresponding tables remains company specific. When accessing and configuring the Enabled Reports form, the administrator is only able to make changes for the current company account. The administrator will need to close the form and switch company accounts in the Microsoft Dynamics AX Connector client in order to configure other company accounts. Cheque Report Destination Security A security measure was added which restricts any report containing "Cheque" to only have Printer delivery destinations available. Document Process, E- mail, Fax, and Screen destination will be filtered out of the available delivery destinations to assign to the report.

6 6 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES XML Version Tags All XML output has version tags in the BT prolog in order to indicate the version of Microsoft Dynamics AX Connector that generated the output and the version of Microsoft Dynamics AX that Microsoft Dynamics AX Connector was run on. XML Field XML Section Description Field_BT_AX_ConnectorVersion Section_BT_DPA The version of Microsoft Dynamics AX Connector installed when generated. Field_AXVersion Section_BT_DPA The version of AX installed when generated. CHM Help Files CHM help can be accessed by clicking the F1 key or clicking the standard help icon on the form.

7 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES 7 Delete Preview PDF Automatically User generated preview PDFs are automatically deleted from the target preview folder after two days. Handle Preview Scenario for Batch Microsoft Dynamics AX Connector 3.0 supports the viewing of multiple documents in a single preview PDF. Previously all the documents had to be viewed in separate PDFs. This functionality is still supported, but now all of the reports can be combined into a single report and therefore a single PDF by checking the "Combine into one Report" checkbox under Print Options. When combining into one report, a single XML file is generated with a single BT_DPA prolog which contains all of the data for the documents in the multiselect batch. In the prolog there is a field called Field_TotalNumberInBatch which keeps track of the total documents in the batch. Each of the documents in the batch is delimited by a section called Section_BT_DPA_Batch which contains the field Field_CurrentNumberInBatch and keeps track of the document's order in the batch.

8 8 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES XML Field XML Section Description Field_TotalNumberInBatch Section_BT_DPA Total number of documents in the batch. Field_CurrentNumberInBatch Section_BT_DPA_Batch Document's order in the batch. Single Listing for AOT Report Names An issue has been addressed in Microsoft Dynamics AX Connector 3.0 where dropdown lists of AOT Reports contained multiple entries for a report if it had been modified in multiple layers. Now the AOT report will only be listed once. Assigning Delivery Destinations to a Report Report delivery destinations are associated with specific AX users and groups. The admin user can configure the module such that specific users only see the delivery destinations that are appropriate for their role. Additionally, the delivery destinations have attributes that will determine the physical routing of the output. For example, the XML output file can be directed to a particular network location depending on the user.

9 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES 9

10 10 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES

11 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES 11 Pass End-user's User Groups to BT-DPA Two new fields have been added to the BT_DPA prolog: Field_GroupIds and Field_GroupNames. Field_GroupsIds contains a semicolon-delimited list of the end user's group IDs for the groups that the user has membership (for instance FinCtrl). Field_GroupNames contains a semicolon-delimited list of the end user's group names for the groups that the user has membership (for instance Finance Controller). XML Field XML Section Description Field_GroupIds Section_BT_DPA All group ids for which the user has membership Field_GroupNames Section_BT_DPA All group names for which the user has membership Destination Parameters Field to Delivery Destination The Setup tab on the Delivery Destination form now has a User Defined field that can be used by the BT-DPA server solution. The field is a memo field so that long text strings and multiple lines are supported. The limit on the field will be 2,097,152 characters (i.e. 2 megabytes).

12 12 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES This feature required the following tables to be modified: AOT Table Name Field Name Type BT_DPA_Destinations BT_DPA_DestinationUserDefined BT_DPA_DestinationUserDef ined Report Parameters Field to Enable Reports The Setup tab on the Enabled Report form now has a User Defined field that can be used by the BT-DPA server solution. The field will be a memo field so that long text strings and multiple lines can be entered. The new limit on the field will be 2,097,152 characters (i.e. 2 megabytes).

13 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES 13 This feature required the following tables to be modified: AOT Table Name Field Name Type BT_DPA_AOT_Reports BT_DPA_UserDefined BT_DPA_ReportUserDefined Enabled Reports Testing Parameter a Memo Field The testing parameter on the Setup Tab of the Enabled Reports form is now a memo field so that more text can be supported. The new limit on the field will be 2,097,152 characters (i.e. 2 megabytes).

14 14 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES Testing of Popular Reports Quality Assurance tested the following popular reports for this release: Report Description Purchase Order AR Invoice AR Customer Statement AR Picking List AR Packing Slip Check AOT Report Name PurchPurchaseOrder SalesInvoice CustAccountStatementExt WMSPickingList_OrderPick SalesPackingSlip Cheque_US

15 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES 15 Create!form Print Medium Microsoft Dynamics AX Connector 3.0 now leverages AX's print mediums in order to deliver reports to their destinations, which includes screens for Process, Fax, , Printer, and Screen. The screens were migrated from the now deprecated Ad-hoc feature.

16 16 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES

17 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES 17 Unattended Batch Support A new feature in Microsoft Dynamics AX 2009 is support for unattended batches. In previous versions, a client always had to be logged on in order to run a batch. Microsoft Dynamics AX Connector 3.0 supports the running of Create!form enabled reports on unattended batches. Delivery Method Code In previous versions of Microsoft Dynamics AX Connector, the delivery method for the report was represented in the BT prolog by Field_DeliveryMethod. In Microsoft Dynamics AX Connector 3.0, since labels are now localized, Field_DeliveryMethod_Code has been added to the BT prolog in order to support Director projects which may service AX clients

18 18 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES using multiple languages. Each delivery method type will be consistently represented with an assigned code. The BT prolog was modified in the following way: XML Field XML Section Description Field_DeliveryMethod_Code Section_BT_DPA Contains the code for the delivery method of the report. Each of the delivery methods is coded as follows: Delivery Method Code Screen 0 Printer 1 2 Fax 3 Document Process 4 Each delivery method's code corresponds to its enumeration values from the BT_DPA_Dest_Type base enum. Remove XPO Import Warnings In v2.0, when the XPO was imported, a dialog displayed warning messages about the data dictionary objects. These warning no longer appear in 3.0. Deployment Schedule for AOT Reports BT-DPA enabled reports have a deployment schedule which allows the administrator to control when to enable a report for Create!form and which report design to utilize. This functionality is controlled in the Enabled Report form on the Deployment Schedule tab. Here the administrator is able to select the time zone to base the date and time from, and rows in the grid specify deployment schedules, sorted by date. For each deployment schedule item, the administrator can specify a date, a time, and a design to use. If the date and time are left blank then the design is considered to be immediately enabled. If an enabled report does not have a deployment schedule specified then the report will behave similarly to previous versions where reports are immediately enabled and the first report design in the AOT Design subnode is utilized, considered the default design.

19 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES 19 If the administrator does not wish to specify a deployment schedule but would like to specify a design, the administrator can leave the date and time blank and just select a report design. This feature required the following AOT objects to be modified: AOT Object Change Description BT_DPA_AOT_Reports BT_DPA_Timezone added Timezone for all of the deployment times. This feature required a new table called BT_DPA_DeploymentSchedule to be created: Field Type Description BT_DPA_AOT_Report_Id BT_DPA_AOT_Obj ect_id Table's reference to enabled reports in BT_DPA_AOT_Reports. BT_DPA_DesignName BT_DPA_255Char Report design to use when processing. BT_DPA_DateDesignEnabled TransDate The date when to enable the design. BT_DPA_TimeDesignEnabled timeofday The time when to enable the design on the enablement date. This feature required a new temporary table, which only exists in memory, called BT_DPA_AvailableDesigns to be created: Field Type Description BT_DPA_ReportName BT_DPA_255Char The current report name. BT_DPA_DesignName BT_DPA_255Char Available designs for the report. Enterprise Portal Support Microsoft Dynamics AX Connector 3.0 has code which handles displaying legacy AOT Reports in Enterprise Support (as opposed to AOT Web Reports, which are not supported). Reports are enabled in the Enabled Reports form in the conventional AX Client. Reports in the Enterprise Portal are displayed as PDF's.

20 20 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES Cheque Report Remittance Lines The number of remittance lines to include in a cheque report is now configurable. Previously, this was automatically set to AX Instance Information AX instance information is now included in the BT_DPA prolog. The AOS id and the name of the instance will be included in Field_AX_AOSId and Field_AX_Instance_Name respectively. New AOT Job There is a new AOT job which handles clearing testing parameters for reports. Often users will want to do this before going live. The AOT Job "ClearTestingParameters" is in the Microsoft Dynamics AX Connector 3.0 shared project. Data Backup Procedures Instructions are now available for importing and exporting BT_DPA data

21 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES Known Issues 21 Known Issues Issue ID #1198 Group Id and Group name accepting characters with semicolon. When adding a Group Id or Group name containing a semicolon, an additional name is generated. Workaround - Do not use a semicolon when creating a Group Id or Group name Issue ID #1201 Sales Invoice: Field_PagesTotal is not reflected correctly in XML. The AX report (not CF Enabled) shows the correct value Issue ID #1205 XML generated from a Standard AX Report Design contains a duplicate section with no data. Issue ID # 1239 The location of the Preview PDF folder has constraints if the user will be viewing Create!form enabled reports through Enterprise Portal. The World Wide Web Publishing service must have access and Full Control permission to the Preview PDF folder for the report to display through the web browser. If the Preview PDF folder resides on a different machine than the AOS and Enterprise Portal server, then a Create!form enabled Invoice fails to display to the user viewing it through a Web Browser. Instead, the user is presented with a text file that contains no data. Workaround - If this occurs, move the Preview PDF folder local to the AOS and Enterprise Portal.

22 22 MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES Resolved Issues Resolved Issues Issue ID # 1240 An issue has been addressed in Microsoft Dynamics AX Connector 3.0 where dropdown lists of AOT Reports contained multiple entries for a report if it had been modified in multiple layers. Now the AOT report will only be listed once.