Microsoft Dynamics AX Connector Copyright Bottomline Technologies, Inc. 2008. 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. R ELEASE N OTES MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES In this document the following Release Notes are discussed: • Overview • New Features • Known Issues • Resolved Issues Product: Microsoft Dynamics AX Connector 3.0 Last modified: November 13, 2008 8:11 pm Created by: Development
Transcript
R E L E A S E N O T E S
MICROSOFT DYNAMICS AX CONNECTOR 3.0 RELEASE NOTES
In this document the following Release Notes are discussed:• Overview• New Features• Known Issues• Resolved Issues
Product: M i c r o s o f t D y n a m i c s A X C o n n e c t o r 3 . 0
Last modified:N o v e m b e r 1 3 , 2 0 0 8 8 : 1 1 p m
Created by:D e v e l o p m e n t
Microsoft Dynamics AX Connector Copyright Bottomline Technologies, Inc. 2008.All Rights Reserved, Printed in the United States of AmericaEvery effort has been made to ensure the accuracy of this manual. Information in this document is subject to change without notice and does not representa commitment on the part of Bottomline Technologies. Bottomline Technologies makes no warranties with respect to this documentation and disclaimsany implied warranties of merchantability or fitness for particular purpose. All software described in this manual is furnished under a license agreementor nondisclosure agreement, and may only be used in accordance with the terms of this agreement. Microsoft Dynamics AX Connector licensee(s) mayreproduce Microsoft Dynamics AX Connector instructional documentation as needed for distribution to users of the licensed Microsoft Dynamics AXConnector software. The licensee(s) agrees not to modify, adapt, translate, or otherwise alter the documentation prior to distribution.
2
. . . . . M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
Overview
OverviewThis document contains a summary of new features included in MicrosoftDynamics AX Connector 3.0. Microsoft Dynamics AX Connector 3.0 is aCreate!form solution that is installed into an existing Microsoft AXimplementation.
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.0.11
Microsoft Dynamics AX Connector Release Notes
3
. . . . .M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New FeaturesM I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
New Features
Automatic InstallerNew install program which will automatically imports XPOs, deploys labelfiles, compiles forward necessary classes, and deletes intermediate AXprojects. 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 toAll" during imports and to close the AX Client manually after each task iscomplete.
BTDPA NumberSequence DeprecationPrevious versions of Microsoft Dynamics AX Connector required that aBTDPA number sequence be created and referenced in order to use theimplementation. Utilizing the Number Sequence Framework in MicrosoftDynamics AX requires many manual steps by the user. Microsoft DynamicsAX Connector 3.0 has a more intrinsic method for generating unique idswhich will require no additional setup by the user after installation.Here is the list of AOT Objects created to support internal numbersequencing:
Localization of all UI TextAll text displayed in the user interface, including various info log messagesand modal dialogs, is now localized. This entails having all of the text locatedin the axDPA[lang-code].ald file, which is readable in a text editor.The following languages are supported:
AOT Object Name Object TypeBT_DPA_TableNumSequence TableBT_DPA_TableId Int FieldBT_DPA_NextNum Int FieldBT_DPA_TableNumSequenceGenerator Class
Microsoft Dynamics AX Connector Release Notes
4
. . . . . M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
Optional Use of Folder MonitorIn previous versions of Microsoft Dynamics AX Connector, Folder Monitorwas a required component in order to deliver XML output from MicrosoftDynamics AX to Create!form. In Microsoft Dynamics AX Connector 3.0, itsuse is now optional. XML Output Locations can be specified in the Defaultsform and in the delivery destination's Setup tab. Instead of a shared folder pathwhich is watched by Folder Monitor, a shared Create!form enabled printqueue path may be entered instead.
Removal of XML OptimizerA new XML engine has been implemented to produce XML which will notrequire addition processing afterwards.
Allow Copying/Sharing of Configuration Settings between Company AccountsConfiguration settings for the Defaults, Document Processes, and DeliveryDestinations forms are stored globally by setting the SaveDataPerCompany
Language Language Code Label File NameEnglish (United States) en-us axDPAen-us.aldEnglish (U.K.) en-gb axDPAen-gb.aldEnglish (Australia) en-au axDPAen-au.aldEnglish (Canada) en-ca axDPAen-ca.aldEnglish (New Zealand) en-nz axDPAen-nz.aldENGLISH (IRELAND) en-ie axDPAen-ie.aldEnglish (South Africa) en-za axDPAen-za.aldEnglish (India) en-in axDPAen-in.aldEnglish (Malaysia) en-my axDPAen-my.aldEnglish (Singapore) en-sg axDPAen-sg.aldSpanish (Spain - Modern Sort) es axDPAes.aldFrench (Standard) fr axDPAfr.aldGerman (Austria) de-at axDPAde-at.aldGerman (Switzerland) de-ch axDPAde-ch.aldDutch (Standard) nl axDPAnl.ald
Microsoft Dynamics AX Connector Release Notes
5
. . . . .M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New FeaturesM I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
property for the forms' corresponding tables to No. All company accountshave permission to access and modify the data stored in these tables.Here is the list of tables whose SaveDataPerCompany property is set to No:
The data stored in the Enabled Reports form's corresponding tables remainscompany specific. When accessing and configuring the Enabled Reports form,the administrator is only able to make changes for the current companyaccount. The administrator will need to close the form and switch companyaccounts in the Microsoft Dynamics AX Connector client in order toconfigure other company accounts.
Cheque Report Destination SecurityA 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 deliverydestinations to assign to the report.
Table Name Form NameBT_DPA_Defaults DefaultsBT_DPA_Destinations
Delivery Destinations
BT_DPA_DestinationGroupRestrictions
Delivery Destinations
BT_DPA_DestinationUserRestrictions
Delivery Destinations
BT_DPA_Processes Document Processes
Microsoft Dynamics AX Connector Release Notes
6
. . . . . M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
XML Version TagsAll XML output has version tags in the BT prolog in order to indicate theversion of Microsoft Dynamics AX Connector that generated the output andthe version of Microsoft Dynamics AX that Microsoft Dynamics AXConnector was run on.
CHM Help FilesCHM help can be accessed by clicking the F1 key or clicking the standard helpicon on the form.
XML Field XML Section DescriptionField_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.
Microsoft Dynamics AX Connector Release Notes
7
. . . . .M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New FeaturesM I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
Delete Preview PDF AutomaticallyUser generated preview PDFs are automatically deleted from the targetpreview folder after two days.
Handle Preview Scenario for BatchMicrosoft Dynamics AX Connector 3.0 supports the viewing of multipledocuments in a single preview PDF. Previously all the documents had to beviewed in separate PDFs. This functionality is still supported, but now all ofthe reports can be combined into a single report and therefore a single PDF bychecking the "Combine into one Report" checkbox under Print Options.
When combining into one report, a single XML file is generated with a singleBT_DPA prolog which contains all of the data for the documents in the multi-select batch. In the prolog there is a field called Field_TotalNumberInBatchwhich keeps track of the total documents in the batch. Each of the documentsin the batch is delimited by a section called Section_BT_DPA_Batch whichcontains the field Field_CurrentNumberInBatch and keeps track of thedocument's order in the batch.
Microsoft Dynamics AX Connector Release Notes
8
. . . . . M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
Single Listing for AOT Report NamesAn issue has been addressed in Microsoft Dynamics AX Connector 3.0 wheredropdown lists of AOT Reports contained multiple entries for a report if it hadbeen modified in multiple layers. Now the AOT report will only be listedonce.
Assigning Delivery Destinations to a ReportReport delivery destinations are associated with specific AX users and groups.The admin user can configure the module such that specific users only see thedelivery destinations that are appropriate for their role. Additionally, thedelivery destinations have attributes that will determine the physical routing ofthe output. For example, the XML output file can be directed to a particularnetwork location depending on the user.
XML Field XML Section DescriptionField_TotalNumberInBatch Section_BT_DPA Total number of documents in the
batch.Field_CurrentNumberInBatch Section_BT_DPA_Batch Document's order in the batch.
Microsoft Dynamics AX Connector Release Notes
9
. . . . .M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New FeaturesM I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
Microsoft Dynamics AX Connector Release Notes
10
. . . . . M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
Microsoft Dynamics AX Connector Release Notes
11
. . . . .M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New FeaturesM I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
Pass End-user's User Groups to BT-DPATwo new fields have been added to the BT_DPA prolog: Field_GroupIds andField_GroupNames. Field_GroupsIds contains a semicolon-delimited list ofthe end user's group IDs for the groups that the user has membership (forinstance FinCtrl). Field_GroupNames contains a semicolon-delimited list ofthe end user's group names for the groups that the user has membership (forinstance Finance Controller).
Destination Parameters Field to Delivery DestinationThe Setup tab on the Delivery Destination form now has a User Defined fieldthat can be used by the BT-DPA server solution. The field is a memo field sothat long text strings and multiple lines are supported. The limit on the fieldwill be 2,097,152 characters (i.e. 2 megabytes).
XML Field XML Section DescriptionField_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
Microsoft Dynamics AX Connector Release Notes
12
. . . . . M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
This feature required the following tables to be modified:
Report Parameters Field to Enable ReportsThe Setup tab on the Enabled Report form now has a User Defined field thatcan be used by the BT-DPA server solution. The field will be a memo field sothat long text strings and multiple lines can be entered. The new limit on thefield will be 2,097,152 characters (i.e. 2 megabytes).
AOT Table Name Field Name TypeBT_DPA_Destinations BT_DPA_DestinationUserDefined BT_DPA_DestinationUserDef
ined
Microsoft Dynamics AX Connector Release Notes
13
. . . . .M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New FeaturesM I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
This feature required the following tables to be modified:
Enabled Reports Testing Parameter a Memo FieldThe testing parameter on the Setup Tab of the Enabled Reports form is now amemo field so that more text can be supported. The new limit on the field willbe 2,097,152 characters (i.e. 2 megabytes).
AOT Table Name Field Name TypeBT_DPA_AOT_Reports BT_DPA_UserDefined BT_DPA_ReportUserDefined
Microsoft Dynamics AX Connector Release Notes
14
. . . . . M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
Testing of Popular ReportsQuality Assurance tested the following popular reports for this release:
Report Description AOT Report NamePurchase Order PurchPurchaseOrderAR Invoice SalesInvoiceAR Customer Statement CustAccountStatementExtAR Picking List WMSPickingList_OrderPickAR Packing Slip SalesPackingSlipCheck Cheque_US
Microsoft Dynamics AX Connector Release Notes
15
. . . . .M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New FeaturesM I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
Create!form Print MediumMicrosoft Dynamics AX Connector 3.0 now leverages AX's print mediums inorder to deliver reports to their destinations, which includes screens forProcess, Fax, E-Mail, Printer, and Screen. The screens were migrated from thenow deprecated Ad-hoc feature.
Microsoft Dynamics AX Connector Release Notes
16
. . . . . M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
Microsoft Dynamics AX Connector Release Notes
17
. . . . .M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New FeaturesM I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
Unattended Batch SupportA new feature in Microsoft Dynamics AX 2009 is support for unattendedbatches. In previous versions, a client always had to be logged on in order torun a batch. Microsoft Dynamics AX Connector 3.0 supports the running ofCreate!form enabled reports on unattended batches.
Delivery Method CodeIn previous versions of Microsoft Dynamics AX Connector, the deliverymethod for the report was represented in the BT prolog byField_DeliveryMethod. In Microsoft Dynamics AX Connector 3.0, sincelabels are now localized, Field_DeliveryMethod_Code has been added to theBT prolog in order to support Director projects which may service AX clients
Microsoft Dynamics AX Connector Release Notes
18
. . . . . M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
using multiple languages. Each delivery method type will be consistentlyrepresented with an assigned code.The BT prolog was modified in the following way:
Each of the delivery methods is coded as follows:
Each delivery method's code corresponds to its enumeration values from theBT_DPA_Dest_Type base enum.
Remove XPO Import WarningsIn v2.0, when the XPO was imported, a dialog displayed warning messagesabout the data dictionary objects. These warning no longer appear in 3.0.
Deployment Schedule for AOT ReportsBT-DPA enabled reports have a deployment schedule which allows theadministrator to control when to enable a report for Create!form and whichreport design to utilize. This functionality is controlled in the Enabled Reportform on the Deployment Schedule tab. Here the administrator is able to selectthe time zone to base the date and time from, and rows in the grid specifydeployment schedules, sorted by date. For each deployment schedule item, theadministrator can specify a date, a time, and a design to use. If the date andtime are left blank then the design is considered to be immediately enabled.If an enabled report does not have a deployment schedule specified then thereport will behave similarly to previous versions where reports areimmediately enabled and the first report design in the AOT Design subnode isutilized, considered the default design.
XML Field XML Section DescriptionField_DeliveryMethod_Code Section_BT_DPA Contains the code for the delivery
method of the report.
Delivery Method CodeScreen 0Printer 1E-Mail 2Fax 3Document Process 4
Microsoft Dynamics AX Connector Release Notes
19
. . . . .M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New FeaturesM I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
If the administrator does not wish to specify a deployment schedule but wouldlike to specify a design, the administrator can leave the date and time blankand just select a report design.This feature required the following AOT objects to be modified:
This feature required a new table called BT_DPA_DeploymentSchedule to becreated:
This feature required a new temporary table, which only exists in memory,called BT_DPA_AvailableDesigns to be created:
Enterprise Portal SupportMicrosoft Dynamics AX Connector 3.0 has code which handles displayinglegacy AOT Reports in Enterprise Support (as opposed to AOT Web Reports,which are not supported). Reports are enabled in the Enabled Reports form inthe conventional AX Client. Reports in the Enterprise Portal are displayed asPDF's.
AOT Object Change DescriptionBT_DPA_AOT_Reports BT_DPA_Timezone added Timezone for all of the
deployment times.
Field Type DescriptionBT_DPA_AOT_Report_Id BT_DPA_AOT_Obj
ect_IdTable'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.
Field Type DescriptionBT_DPA_ReportName BT_DPA_255Char The current report name.BT_DPA_DesignName BT_DPA_255Char Available designs for the report.
Microsoft Dynamics AX Connector Release Notes
20
. . . . . M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
New Features
Cheque Report Remittance LinesThe number of remittance lines to include in a cheque report is nowconfigurable. Previously, this was automatically set to 9999999.
AX Instance InformationAX instance information is now included in the BT_DPA prolog. The AOS idand the name of the instance will be included in Field_AX_AOSId andField_AX_Instance_Name respectively.
New AOT JobThere 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.0shared project.
Data Backup ProceduresInstructions are now available for importing and exporting BT_DPA data
Microsoft Dynamics AX Connector Release Notes
21
. . . . .M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
Known IssuesM I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
Known Issues
Known IssuesIssue 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.
Microsoft Dynamics AX Connector Release Notes
22
. . . . . M I C R O S O F T D Y N A M I C S A X C O N N E C T O R 3 . 0 R E L E A S E N O T E S
Resolved Issues
Resolved IssuesIssue 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.
