|
|
|
|
|
|
|
|
|
|
| |
JB,
I have found this to be the case with many IM scripts upgraded from previous
IM releases. However, here is what I have done to work around this issue and
it may or may not work depending on your case.
Method 1:
1) Open notepad.exe
2) Copy/Paste the event/field script into notepad
3) Delete the script, save the integration and exit IM
4) Open IM, open the event/field script and paste from notepad
5) Compile and test
Method 2:
1) Create a blank integration database (Tools > Create Database)
2) Change IM to point to the new database (Tools > Options)
3) Restart IM
4) Import all your integrations into the new database (File > Import
Integrations)
5) Open your scripts and recompile
6) Test
Best regards,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
"JB" wrote:
> Is anyone using this functionality successfully in an IM 10 integration?
> Regardless of the parameters it gives me a "Type mismatch" error.
>
> This is code moved over from an IM 9 integration that worked fine.
>
> Here's the code, doesn't get much simpler:
>
> LogDocDetail "NEW ITEM"
>
>
> |
| |
|
| |
Was this post helpful to you? |
|
|
|
|
|
|
|
 Reply |
| |
 |
|
 Top |
|
|
|
|
|
|
|
|
|
| |
Thank you to both of you for your responses. The issue is also affecting
CancelDocument - it's possible though untested by me that all functions that
take parameters have this problem.
Mariano I'll try out your suggestions and see if I can trigger something
that will get it working.
I believe there's also a bug if the top line of a script is left blank.
There was probably a change in the script editing window since IM 9 since I
don't remember it happening in the past. Here's how I can trigger it:
Create a new script
Hit enter to bypass the first line in the script and enter code only on the
second line
Save the script and exit the script editor
Try to reopen the script, I get the error "Argument 'Start' must be greater
than zero".
I have to remove the script and create a new one since I can't open that
script at all once I close it.
I'm using IM 10 SP2, from 5/28/08.
Thanks!
Jeff
"Mariano Gomez" <MarianoGomez@discussions.microsoft.com> wrote in message
news:BBC7E60D-AA97-4D2E-9B7A-540E46866FA2@microsoft.com...
> JB,
>
> I have found this to be the case with many IM scripts upgraded from
> previous
> IM releases. However, here is what I have done to work around this issue
> and
> it may or may not work depending on your case.
>
> Method 1:
>
> 1) Open notepad.exe
> 2) Copy/Paste the event/field script into notepad
> 3) Delete the script, save the integration and exit IM
> 4) Open IM, open the event/field script and paste from notepad
> 5) Compile and test
>
> Method 2:
>
> 1) Create a blank integration database (Tools > Create Database)
> 2) Change IM to point to the new database (Tools > Options)
> 3) Restart IM
> 4) Import all your integrations into the new database (File > Import
> Integrations)
> 5) Open your scripts and recompile
> 6) Test
>
> Best regards,
> --
> MG.-
> Mariano Gomez, MIS, MCP, PMP
> Maximum Global Business, LLC
> http://www.maximumglobalbusiness.com
>
>
> "JB" wrote:
>
>> Is anyone using this functionality successfully in an IM 10 integration?
>> Regardless of the parameters it gives me a "Type mismatch" error.
>>
>> This is code moved over from an IM 9 integration that worked fine.
>>
>> Here's the code, doesn't get much simpler:
>>
>> LogDocDetail "NEW ITEM"
>>
>>
>>
|
| |
|
| |
Was this post helpful to you? |
|
|
|
|
|
|
|
Reply |
| |
|
|
Top |
|
|
|
|
|
|
|
| |
 Answer |
|
| |
Jeff,
You actually hit the nail right on the head so to speak when you said "...
that all functions that take parameters have this problem". Here is what I
was able to find out from development. 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.
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.
You used to be able to do the following which now generates a Type Mismatch
error:
LogDocDetail "Test doc detail message"
As a work around until these functions are fixed, supply a value for ALL
parameters since the C# is now considered those as required parameters.
Ex:
LogDocDetail "Test doc detail message","IM",1,"field1","value1"
Give this a try. This method should let you log the additional detail you
need.
Regards,
Greg Willson - GP Developer Support
Microsoft Online Support Engineer
======================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix issues and simple how to questions.
======================================================
We also love to hear your product feedback!
Let us know what you think by posting
from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================== |
| |
|
| |
Was this post helpful to you? |
|
|
|
|
|
|
|
Reply |
| |
|
|
Top |
|
|
|
|
|
|
|
|
|
| |
Great - Can we get a list of the parameters for all functions - including
CancelDocument?
HS
"Greg Willson [MSFT]" <grwill@online.microsoft.com> wrote in message
news:Ic0k6mt1IHA.5360@TK2MSFTNGHUB02.phx.gbl...
> Jeff,
>
> You actually hit the nail right on the head so to speak when you said "...
> that all functions that take parameters have this problem". Here is what
> I
> was able to find out from development. 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.
>
> 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.
>
> You used to be able to do the following which now generates a Type
> Mismatch
> error:
> LogDocDetail "Test doc detail message"
>
> As a work around until these functions are fixed, supply a value for ALL
> parameters since the C# is now considered those as required parameters.
>
> Ex:
> LogDocDetail "Test doc detail message","IM",1,"field1","value1"
>
>
> Give this a try. This method should let you log the additional detail you
> need.
>
> Regards,
> Greg Willson - GP Developer Support
> Microsoft Online Support Engineer
>
>
> ======================================================
> PLEASE NOTE: The partner managed newsgroups are provided to assist with
> break/fix issues and simple how to questions.
> ======================================================
>
> We also love to hear your product feedback!
> Let us know what you think by posting
> from the web interface: Partner Feedback
> from your newsreader: microsoft.private.directaccess.partnerfeedback.
> We look forward to hearing from you!
>
> ======================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others
> may learn and benefit from this issue.
>
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ======================================================
|
| |
|
| |
Was this post helpful to you? |
|
|
|
|
|
|
|
Reply |
| |
|
|
Top |
|
|
|
|
|
|
|
|
|
| |
Habib,
I was able to find them in the IM User's Guide, but then again, hopefully
they are all there.
Best regards,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
"HSalim[MVP]" wrote:
> Great - Can we get a list of the parameters for all functions - including
> CancelDocument?
>
> HS
>
> "Greg Willson [MSFT]" <grwill@online.microsoft.com> wrote in message
> news:Ic0k6mt1IHA.5360@TK2MSFTNGHUB02.phx.gbl...
> > Jeff,
> >
> > You actually hit the nail right on the head so to speak when you said "...
> > that all functions that take parameters have this problem". Here is what
> > I
> > was able to find out from development. 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.
> >
> > 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.
> >
> > You used to be able to do the following which now generates a Type
> > Mismatch
> > error:
> > LogDocDetail "Test doc detail message"
> >
> > As a work around until these functions are fixed, supply a value for ALL
> > parameters since the C# is now considered those as required parameters.
> >
> > Ex:
> > LogDocDetail "Test doc detail message","IM",1,"field1","value1"
> >
> >
> > Give this a try. This method should let you log the additional detail you
> > need.
> >
> > Regards,
> > Greg Willson - GP Developer Support
> > Microsoft Online Support Engineer
> >
> >
> > ======================================================
> > PLEASE NOTE: The partner managed newsgroups are provided to assist with
> > break/fix issues and simple how to questions.
> > ======================================================
> >
> > We also love to hear your product feedback!
> > Let us know what you think by posting
> > from the web interface: Partner Feedback
> > from your newsreader: microsoft.private.directaccess.partnerfeedback.
> > We look forward to hearing from you!
> >
> > ======================================================
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others
> > may learn and benefit from this issue.
> >
> > ======================================================
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > ======================================================
>
>
> |
| |
|
| |
Was this post helpful to you? |
|
|
|
|
|
|
|
Reply |
| |
|
|
Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Thanks for checking on that Greg, I tried it and all of the functions do
work if supplied with all the parameters.
Unfortunately I ran into a few more hiccups and I've decided just to do the
importing myself using C# and eConnect. There were too many changes between
IM 9 and 10 and I'd rather spend time working on my standalone solution than
in trying to resolve the remainder of my IM 10 issues. So far eConnect has
been great though and my progress on a C# solution is much faster than I
would have guessed.
I do like that eConnect was integrated into IM but I was unable to use the
eConnect adapter because it didn't have as many fields exposed as the old
OLE adapter (the user defined fields in the inventory options screen, in my
case). They're available in the eConnect XML schema but for some reason
they didn't make it into the IM adapter that I could see.
Jeff
"Greg Willson [MSFT]" <grwill@online.microsoft.com> wrote in message
news:Ic0k6mt1IHA.5360@TK2MSFTNGHUB02.phx.gbl...
> Jeff,
>
> You actually hit the nail right on the head so to speak when you said "...
> that all functions that take parameters have this problem". Here is what
> I
> was able to find out from development. 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.
>
> 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.
>
> You used to be able to do the following which now generates a Type
> Mismatch
> error:
> LogDocDetail "Test doc detail message"
>
> As a work around until these functions are fixed, supply a value for ALL
> parameters since the C# is now considered those as required parameters.
>
> Ex:
> LogDocDetail "Test doc detail message","IM",1,"field1","value1"
>
>
> Give this a try. This method should let you log the additional detail you
> need.
>
> Regards,
> Greg Willson - GP Developer Support
> Microsoft Online Support Engineer
>
>
> ======================================================
> PLEASE NOTE: The partner managed newsgroups are provided to assist with
> break/fix issues and simple how to questions.
> ======================================================
>
> We also love to hear your product feedback!
> Let us know what you think by posting
> from the web interface: Partner Feedback
> from your newsreader: microsoft.private.directaccess.partnerfeedback.
> We look forward to hearing from you!
>
> ======================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others
> may learn and benefit from this issue.
>
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ======================================================
|
| |
|
| |
Was this post helpful to you? |
|
|
|
|
|
|
|
Reply |
| |
|
|
Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I believe the issue is that you have a blank line in your autodim.txt file.
Make sure to remove any extra lines you might have.
patrick
dev support
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Katie" <Katie@discussions.microsoft.com> wrote in message
news:36BACA5E-C197-4D07-A04A-3B66BCBC88A8@microsoft.com...
> Hello. I am running into this error in v9 when attempting to launch
> Integration Manager via AutoDim software. I have a batch file which fires
> AutoDim, which in turn fires GP and IM to import inventory transactions.
> This process has worked flawlessly for almost two years now until about a
> week or so. Now the process is continuing to "hang" after GP is opened,
> before IM opens, with the error "Run-time Error 13: Type mismatch." I am
> not
> sure if their Network team updated any software, however, GP has not been
> updated. GP is currently at version 9.00.0293. Any ideas?
>
> Thanks,
> Katie
>
> "Kayla Backer" wrote:
>
>> Hi there Jeff,
>>
>> Anything else we can do for you here on this query?
>>
>> Please post back at your convenience and we will be here for you.
>> Thanks again for using the partner newsgroups!
>>
>> Have a great week!
>>
>>
>> Kayla Backer
>>
>> Microsoft Online Support Engineer
>>
>>
>>
>> Get Secure! - www.microsoft.com/security
>>
>> ==============================================
>>
>> PLEASE NOTE: The partner managed newsgroups are provided
>>
>> to assist with break/fix issues and simple how to questions.
>>
>>
>>
>> We also love to hear your product feedback!
>>
>> Let us know what you think by posting
>>
>> from the web interface: Partner Feedback
>>
>> from your newsreader:
>> microsoft.private.directaccess.partnerfeedback.
>>
>> We look forward to hearing from you!
>>
>> =====================================================
>>
>> When responding to posts, please "Reply to Group" via your newsreader
>>
>> so that others may learn and benefit from this issue.
>>
>> ======================================================
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> ======================================================
|
| |
|
| |
Was this post helpful to you? |
|
|
|
|
|
|
|
Reply |
| |
|
|
Top |
|
|
|
|
|
Question
Notify me of replies