Dynamics SL 2011 Customization Upgrade

DB upgrade from SL 7 to SL 2011SP2:

1.  If you upgrade the DB from SL 7 to SL 2011 SP2, some alignment issues will be face. After fix the alignments issues and export the latest customizations.
2.  For testing purpose, delete the customization level for the particular screen ID in Customvba table and Re-import the CST file.

             In this scenario’s face problems:

                  a.  Customizations have “versions”. The newest version is 6.

                  b.  The export customizations that haven’t been updated to version 6, you can’t be able to re-                                            import the CST file you just created. You will get an event log like this:

                             “System Message 5016: Operation aborted, data is not formatted correctly. Data

                                                  Row contents: Source: 0”.

                  To get around this:

                   As always, have a good backup of your environment before making any changes

                         *  Export the customization, but don’t check the “export VBA as source” checkbox

                         *  Edit the file and remove the “Source: 0” line(s)

       3.  Then you can re-import. But in this scenario doesn’t not work for DB upgrade

Export the Customization from SL 7 and Import to SL 2011 SP2:

1.  Export the Customization from SL 7 environment with level like (All user, One group, One user, Supplemental, Self) and  import the customization to SL 2011 SP2 environment
2.  Launch the particular screen and customize the screen, then fix the alignment issues automatically version has been updated to 6  and export the latest customizations.
3.  Then delete the customization level for the particular screen ID in Customvba table
4. Then you can re-import customization. Its working fine

SQL Force SL to upgrade it to version 6 first:

   1.   Run the following in SQL:

Ø  Update CustomVBA set Version=Version+1000 where Version<1000

   2.  Open each customize screen and close

Ø  At this point, the version should update to 6.

  3.  Now export the customization. 

Automate Data Entry manner in Dynamics SL

 Data import into Dynamics SL can be attained through any of the below techniques.

  Transaction import (TI):

All Dynamics SL users have the standard import capabilities through the transaction import tool. When using the transaction import screen, the process is powerfully enhanced by use of the Control Macro Generator, which dynamically adjusts for any customization's for field names, and layout.

·         Integration tool of Dynamics SL to transfer data from an external file into any Dynamics SL window

·         Existing Dynamics SL business logic will validate the imported data ensuring the Transaction integrity is an advantage.

·         Can be launched as a batch script file or can be scheduled to run automatically using the “Application Server” tool of Dynamics SL.

·         The data source could be the data file in the comma or tab delimited format.

·         TI processing works only with the Active Desktop connection. If the machine is locked, TI won’t work and will resume only after the machine is unlocked which is a major disadvantage for data import automations.

   Solomon Object Model:

Solomon object model (SOM) is an automatic process for invoking the SL Standard (r) custom screen. The set of all members (properties, events, and methods) of a COM component, In the Microsoft Dynamics SL Object Model, this includes information about the SIVApplication and SIVToolbar objects and their members.

     More detail about Solomon object Module link beneath

     http://ajitkannan-erp.blogspot.in/2013/04/automatically-invoking-sl-standard-r.html

·         Any Dynamics SL window can be accessed as an object and pass data directly into the window.

·         Any COM-compliant application or programming tool can use Solomon Object model

Eg: VB.Net/ C# by adding the Microsoft.Dynamics.SL.ObjectModel.dll as the reference.

·         Best for Dynamics SL Data import Automations as it strictly follows the SL rules and validations ensuring the SL data integrity.

·         The data source could be the databases of home grown/legacy application or the CSV file.

      SQL injection:

·         Injecting the data into the SQL tables of Dynamics SL directly.

·         Need to replicate the table impacts and the validations of Dynamics SL while importing the data into SL.

·         Not highly recommended as there is always a threat of not replicating all the business rules of Dynamics SL.

Big Big thank you to Perumalsamy, else for all the tremendous effort that they put into these blog...

Quick Send in Dynamics SL 2011

·         Microsoft Dynamics SL has a built-in feature called “Quick Send” that allows you to automatically send invoices and purchase orders via email and fax by using application server technology.

·         Also Electronic Documents Delivery giving users of sending statements, invoices, order confirmations, purchase orders and other customer and vendor related documents by using the application server technology, you can easily create a mail routing to quickly send documents.

·         You can also have an alert sent to your organization every time a quick send is triggered.

·         Before going to this Quick Send setup, configure the Application Server Setup steps in Dynamics SL 2011. Link is beneath

         http://ajitkannan-erp.blogspot.in/2014/04/application-server-setup-in-dynamics-sl.html

Quick send Setup

 Instigate Microsoft Dynamics SL à Foundation à shared Information àSetup à Quick send setup    (21.951.00)

 Document type:

Make a choice the listed document type, this document to be delivered electronically using Application server.

Project preference:

Quick Send Project preference for the Project Invoice and Construction Billing document types are defined for the project or the customer.

Delivery Method:

Delivery methods are Email and Fax. In which the Quick Send request will be sent.

Request Priority:

Processing of the document when sent electronically by the Application Server. Delivery priorities are High, Low, and Normal. 

Application Server:

Specified “your server name “application server to send the documents using quick send.

Notify sender by E-mail:

Message is sent to the user who sends a document electronically. The notification email includes a log of events that occurred while the Application Server processed the document. 

Notify Email Address:

Email address that receives the notification email issued by the Application Server.

Reply Email Address:

Email address used when a vendor, customer, employee, or project stakeholder replies to the email message that contains the document.

File Type:

File contains the document when it is sent electronically. File types for documents sent electronically via email or Text, Word, Crystal Reports, Excel, Adobe Acrobat, Rich Text, XML, and Comma-separated values. 

How to use Quick send option in Screen

1.      Create purchase order 

2.   Click vendor Id look up button  in purchase order screen (04.250.00) to invoke vendor maintenance screen (03.270.00)

3.      In vendor maintenance screen (03.270.00) go to quick send tab to setup the quick send details for the particular vendor. If already quick send details has defined for the particular vendor ignore it.

4.      Click save and close vendor maintenance screen (03.270.00).

5.      Quick send options will enable in  purchase order screen (04.250.00)

6.      Click Quick send button popup message (Quick send entry created for this document) will invoke. Click OK

7.      Run the Application server outstanding requests will process also write a log

Microsoft Dynamics SL à Foundation à Application Server àProcesses à Application Server (96.010.00)

8.      Purchase order request process completed.

9.      if resend the particular documents again  using quick send inquiry ((21.200.00)

Microsoft Dynamics SL à Foundation à shared Information àinquiries à Quick send inquiry (21.200.00)

10.      Click Search/Refresh button it will load all Request. Select the particular document 

11.     Click Resend Requests to resubmit selected Quick Send requests for processing by the Application    Server using the Quick Send preferences defined for the recipient at the time the request was created.

12.  Click Edit Request to edit the Quick Send request in Edit Quick Send Requests (21.010.00).

Application Server Setup in Dynamics SL 2011

Before going to the set up an Application Server in Microsoft Dynamics SL 2011.

·         Check the Application Server email profile defined must be a valid Microsoft Exchange or Outlook.

·         If you plan to utilize the Application Server module to send email requests, be sure that Microsoft Visual Studio Tools for Office (VSTO) add-in is installed on the computer that has been designated as the Application Server.

·         Define a user ID and password for the Application Server (Application Server name - must be the same as a Solomon user ID ) on User Maintenance (95.260.00).

·         User ID has defined proper access right to the Application Server (96.010.00).

Application Server Setup Steps:

1.      Instigate Microsoft Dynamics SL à Foundation à Application Server àMaintenance à Application Server Administration Wizard (96.070.00)

2.      Click Next.

3.      Select user id of the Application Server displays or create a new User ID by clicking “Add user button”

Note: If the user id already defines in the Application Server name can’t view that particular Id to create another one.

4.      Click Next to continue.

5.      Type the number of the “polling interval”, in seconds, at Polling Interval (for example, type 3 the request queue every 3 seconds for new requests).

6.      Type the maximum number of requests (It allows up to 14) at “Maximum Requests Allowed”

7.      Type the Application Server’s email profile ID at “Email Profile ID”

      8.      Click Next.

9.      Enter Number of Entries; the maximum entries the Application Server should retain in the log before it begins overwriting log information.

10.      Enter Number of Days; specify the number of days should be maintained in the log.

11.      Click Next to continue.

12.      Enter Number of Days; Application server can automatically delete completed request from the queue.

13.      Click Next.

14.      Select “Report Routing options”

a.       Select “Delete non-Quick Send reports after they have been emailed” to delete report files immediately after they are sent via email to their recipients.

Note:  For historical intention, email messages containing documents associated with Quick Send requests (purchase orders, invoices, statements, order confirmations, shipping notices, or direct deposit advice slips) are not deleted.

b.      Select “keep the reports in the temporary directory” to maintain the results of a report request in the Application Server temporary file directory even after the reports have been sent via email to the correct recipients.

15.      Select “Process Email Requests”

16.      Click Next.

17.      Select Request Restart option.

a.      “Automatically resubmit incomplete requests” automatically resubmit incomplete requests for reprocessing.

b.      Select “Leave in queue and flag as ―Incomplete” incomplete status of the request and leave it in the request queue. The request can then be resubmitted or deleted from the Application Server Status (96.030.00) screen. 

18.      Click Next.

19.      Under Groups, select the check box for each Application Server group.

20.      Under Users, select the check box for each Application Server user. 

21.      Click Next.

22.      Select the check box for each group and user that will use this Application Server as their default Application Server.

23.      Click Finish.

Attachments Configuration in Dynamics SL 2011

Preface:

In the prior versions of Dynamic SL till SL 7.0, there is always a need to preserve the soft copy of the document pertaining to the transaction. This has been addressed in the latest 2011 versions through the document attachment feature.

   Ex:

     1.  Attach scanned copies of invoices from vendor to the voucher in the Voucher & adjustment screen.
     2.  Use it to attach a spreadsheet that you used to calculate the estimation of project in Dynamics.
     3.  Use it to attach copies of Signed Contracts to the project in project maintenance.
     4.  Multiple source document files can be attached.

It takes a little bit of set up to get to work, but once it is setup, it is very handy.

Attachments Configuration:

The source document files can be maintained from the SharePoint site or Network folder. If the source documents are detached, the files won’t be deleted from the external location. 

Source document files can be attached to data items by using the attachments option on the Notes/Attachments icon on data entry screens. 

The attachments should be configured in the Attachments Configuration screen of Dynamics SL and given below are the various routes.

    Open SL 2011 -> Administration -> Maintenance -> Attachments Configuration (98.400.00)

Upload Destinations Area

   a.  Existing Folder Location:

Select Existing Folder Location to store source document files on a network folder.

Click Browse button and select the path of the network folder. The path selected appears in UNC. Specify the full path of the network folder.

This option is not available if you select “Use Doc Share settings” or “Existing SharePoint Document  Library” option.

   b.  Existing SharePoint Document Library:

Select Existing SharePoint Document Library to store source document files on a SharePoint document library. Specify the Internet address of the SharePoint document library in URL.

This option is not available if you select “Use Doc Share Settings” or “Existing Folder Location” option.