VBScript "Type Mismatch" Error with Integration Manager 10.0

For those of you battling it out with a "Type Mismatch" error in your event or field scripts upgraded to IM 10.0 from previous releases of IM, sweat it no more! This issue has been recognized as a bug by Microsoft and was unfortunately not resolved in Feature Pack 1 (or Service Pack 2). The problem seems to occur with all IM VBScript functions that accept parameters.

"The issue is that these functions (and many other) accepted OPTIONAL parameters in prior versions of IM. The reason these are now failing is because Integration Manager has been switched over from VB6 to C# .Net code. The problem with that is that C# does not support optional parameters. That means that those existing function's "Optional" parameters are now actually Required parameters." said Greg Willson with Microsoft in the Microsoft Dynamics GP Community group.

However, as a workaround, IM developers must supply all parameters for the affected functions until a Hot Fix is made available in July. Willson proceed to explain the issue with an example.

"So with that said, the LogDocDetail function has five parameters (message, source, status_code, field_name and field_value). All parameters are string values except "status_code" which is an Integer value. So, now that we know that, if you supply a value for all parameters, it will work as expected.".

The list of affected functions include (but may not be limited to):

  • CancelDocument [message, source, status_code, field_name, field_value]
  • CancelIntegration [message, source, status_code]
  • Execute path [, timeout] [, window_style]
  • LogDetail [message, source, status_code]
  • LogDocDetail [message, source, status_code, field_name, field_value]
  • LogDocWarning [message, source, status_code, field_name, field_value]
  • LogWarning [message, source, status_code]
  • PlaySound path

Functions not affected:

  • ClearVariables
  • DocumentIsNew
  • DocumentNo
  • GetVariable(variable) -- the parameter is mandatory
  • SetVariable variable, value -- the parameters are mandatory
To access and contribute to the discussion thread on the Microsoft Dynamics GP community click here.

Until next post!

MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Unknown said…
Hi there! I am getting this message in IM v9. I am using Auto Dim which works similar to a login macro to open Dynamics GP and then Integration Manager. I am getting this error after GP opens, just as Integration Manager is called. This is "breaking" the macro and hanging up the integration. What do I change in the integration to avoid this error? You can email me at katiebley@gmail.com. Thank you!

Katie
December 9, 2010 at 10:08 AM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more