web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

GP 10 / Integration Manager and Autodim

(0) ShareShare
ReportReport
Posted on by 100

We have recently upgraded to GP 10 and are looking for an updated version of autodim.exe - does anyone know where we may be able to find this utility?

 

Ann

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    What does this utility do?

  • Ann Kidston Profile Picture
    100 on at

     

    We found the utility - it is a Microsoft Professional Services Tool - we were using it to automate the login to various Great Plains databases in the integration process.
  • JasonBeheler Profile Picture
    230 on at

    We are getting ready to design an integration from a couple different enterprise systems and we hope to use integration manager. 

    I am curious to learn more about this utility and exactly how it is used and perhaps what your integration architecture is (which systems are invovled, what data is being integrated, how you have your physical implemnetation setup, etc).  My understanding of integration manager is that it needs to run on a server with the GP client running.  Do you have a dedicated PC/server for this? 

    Anything you can share would be appreciated. 

  • Ann Kidston Profile Picture
    100 on at

    We have approx 50 Great Plains databases and 1 in-house developed operational system.  Both are running on SQL 2005.  We integrate the operational system to approx 30 GP databases on a daily basis.  We have 1 server dedicated to Great Plains, and Integration Manager is installed on our Citrix server (a separate server).  The finance team accesses Great Plains solely via Citrix.  The integration creates a GL entry in the GP database and records back to the operational system that the record has been transferred.  We use AutoDim.exe to automate loging in to each of the GP databases and trigger the integration.  My role is not that of a developer, so I cannot provide more details, however, hope this helps!

    Ann

  • Community Member Profile Picture
    on at

    Where did you find it? I don't see it in the MPSTs inside GP, and I can't find an executable outside of GP.

  • Ann Kidston Profile Picture
    100 on at

    We had to purchase from our MBC Partner - Tectura - the cost was approx $600 CDN.  I have enclosed the file that was included - it contains more detailed information.

    Ann

    AutoDimVersion 10.0

    The AutoDim tool allows you to launch Microsoft Dynamics GP and run one or more integrations or integration groups and have Microsoft Dynamics GP exit upon completion of the integrations. This tool also supports integrating into several different companies.

    Files included in the zip file

    1.       AutoDim.exe – The program file used to launch Dynamics and the integrations.2.       AutoDim.txt - A sample text file to show the syntax expected by the application.3.       Auto.mac – A sample macro used to login to Dynamics.4.       AutoDim.rtf – This readme.5.       20050121-112000.txt – Sample output file showing debug output with Debug on.6.       SupplementalEULAforMicrosoftTools.txt – license agreement

    Installing AutoDim

    Users can extract the contents of the zip file to the preferred location. For example, extract the contents in the default location of Microsoft Dynamics GP folder if you prefer to use AutoDim in that location.

    Using AutoDim

    When launched, the AutoDim.exe program will perform the following action depending on if it is launched with a command line argument or without:Command line arguments are not case sensitive and are:Debug – this will create a debug output file named AutoDimDebug.txt next to the autodim.exe file. Default is no debug output file.Delay=xx – this sets the “wait” interval for the login/logout of Dynamics/eEnterprise.  Default is 30 seconds.Source=”your path here” – The path must be enclosed in quotes.  The Source parameter is to tell autodim where to find the input file to run the integrations.  The default is to look for autodim.txt in the same folder as the autodim.exe.WAITFORAPP=xx AutoDim normally waits “forever” for the integration to finish.  However by adding this line, AutoDim will only run for XX number of seconds for the integration to finish.  While this might be useful in obscure cases, it is doubtful if this really ought normally be changed.Example syntax to run AutoDimAutodim.exe Debug Source="c:\dynamics\MyAutofile.txt"Would use the myAutofile.txt from c:\dynamics as the source and create the debug output file using standard delay of 30 seconds.Autodim.exe Delay=45Would create no debug file output, set the login/logout delay to 45 seconds, and use the standard autodim.txt in the current folder as the input.Autodim.exe The last has no command line parameter so will look for a file named AutoDim.txt next to the AutoDim.exeAutoDim will read the text file specified or the AutoDim.txt (only the first 100 lines will be read), store the information in an internal array field, and close the text file.It will start by launching Dynamics and running the macro specified as the first parameter.  After executing the command, it will pause the default 30 seconds or the user specified Delay=xx seconds to allow logging into the system.  Next, the 2nd parameter of the file is the command line to run the integration manager.  The program will wait forever for Integration Manager to finish, so if there are any unrecoverable problems from Integration Manager that causes it not to finish the program will sit there until addressed.  It would then continue from that point.  After the Integration is finished, Dynamics will close.  The next login/integration sequence would proceed until all lines in the text file are processed.A sample AutoDim.txt file is below.c:\dyn50btr\dynamics.exe dynamics.set login.mac,c:\dyn50btr\im\imrun.exe /I "My Customers"c:\dyn50btr\dynamics.exe dynamics.set login.mac,c:\dyn50btr\im\imrun.exe /G "RMGroup2"The first line launches dynamics from the c:\dyn50btr folder using the login.mac macro to log in. Then integration manager is invoked and calls the single integration My Customers.  Note the space between the words.  Per the Integration Manager manual, there needs to be double quotes around the name in that case.  A good habit to get into would just be put double quotes around the integration and group names.Refer to the chapter in the Integration Manager manual on Command Line Integrations for creating a login macro as well as command line syntax for running integrations.

    History

    3/26/08  V1.5.11 changed the input method to fso to read input file
    1/21/05 V 1.5.0.1 Fixed a problem that could sometimes happen where GP does not close in unusual situations.
    1/21/05 V 1.5.0.1 Changed the debug file output to be named YYYYMMDD-HHMMSS.txt instead of AutoDimDebug.txt1/20/05 V 1.5.0.0 Changed contents of AutoDimDebug.txt to be little more clear.2/4/03 Fixed a problem with the Delay argument.  Problem was that the integer was being overflowed if > 32.11/4/03 Added code to make Demo version.  Integrate to Lesson Company only.

    Advanced Product Support Services

    If you are interested in learning more about services and tools provided by the Advanced Product Support Services team, contact us at MBSProfessionalServices@microsoft.com

  • Community Member Profile Picture
    on at

    Thanks for the info! That gets me pointed in the right direction.

  • Ann Kidston Profile Picture
    100 on at

    Happy I could be of assistance!

  • johnortega3 Profile Picture
    5 on at

    Hello All,

    I know it has been a long while since this post was active, but I wanted to share some insight that I have gained through experienced using Dynamics GP and AutoDIM.  We had a client ecommerce integration solution that required integrating with Dynamics GP.  Our custom integration was designed to login, run the integration from code, and then kill the GP process after Integration manager was done running.  However, this proved to be inconsistent and caused system errors.  We had our client purchase the AutoDIM tool and the integration has been running smoothly ever since.

    HTH

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans