- LookUp On Change Event Values LookupControlItem
- Posted by Andre Grumbach on October 16th, 2006
Hi all,
I try to set automatically some fields like account name (Custom Field) or
account address (address2) on the onChange Event from the LookUp Field
"Parent account" in contact.
But when I chack the onChange Event, the LookupControlItem has no properties
id, name or data.
Anyone an idea how I get the correct values?
Thanks,
Andre Grumbach
- Posted by Michael Höhne on October 16th, 2006
Andre,
To update additional fields you need to call the CRM web service from your
JavaScript code. The LookupControlItem itself does not contain the
information you're looking for.
--
Michael
Web: http://www.stunnware.com/crm2
Feed: http://www.stunnware.com/crm2/atom.aspx
----------------------------------------------------------
"Andre Grumbach" <Andre.Grumbach@nospam.de> schrieb im Newsbeitrag
news:uZescyP8GHA.4604@TK2MSFTNGP03.phx.gbl...
- Posted by Andre Grumbach on October 17th, 2006
Hello Michael,
have youn any information about calling a CRM Web Service from JScript?
But Please not http://blogs.msdn.com/arash/archive/...29/729320.aspx.
My Problem, I always get an error, when I call the CRM Web Service from
JScript.
Here my SQL Script:
form1.useService("http://itvtcrm/mscrmservices/2006/crmservice.asmx?WSDL","CRM");
// Text3 is always account
// Text4 is a GUID which existing in CRM on Account
var x = document.getElementById("Text3").value;
var y = document.getElementById("Text4").value;
var z = new Object();
z.Attributes = new Array();
z.Attributes[0] = "name";
z.Attributes[1] = "accountnumber";
alert(z.Attributes);
iCallID = form1.CRM.callService(myResults, "Retrieve", x,y,z);
Error: soap:Client Server was unable to process request.
Have youn any ideas?
Thanks,
Andre
"Michael Höhne" <michael.hoehne@nospam.nospam> schrieb im Newsbeitrag
news:OfNJ0ZQ8GHA.2092@TK2MSFTNGP03.phx.gbl...
- Posted by Michael Höhne on October 17th, 2006
Andre,
The following may help:
http://groups.google.de/group/micros...87e1862ffaac23.
It shows how to get to the correct soap request, if that's your problem.
Using it in the CRM form (or any other HTML form) then follows the various
samples you find in this newsgroup when searching for "soap:", including the
colon.
--
Michael
Web: http://www.stunnware.com/crm2
Feed: http://www.stunnware.com/crm2/atom.aspx
----------------------------------------------------------
"Andre Grumbach" <Andre.Grumbach@nospam.de> schrieb im Newsbeitrag
news:O0lIhag8GHA.3264@TK2MSFTNGP04.phx.gbl...
- Posted by Andre Grumbach on October 18th, 2006
Hello Michael,
I know building the SOAP Envelope works with out problems.
But there is another way to call webservice (with use and call webservice).
But with the CRM webservices a get the error:
soap:Client Server was unable to process request.
Any idea, how I can call the crm webservice on this way, because when i
rebuild the soap envelope, the Jscript is very blind.
Here my script which do not working:
form1.useService("http://itvtcrm/mscrmservices/2006/crmservice.asmx?WSDL","CRM");
// Text3 is always account
// Text4 is a GUID which existing in CRM on Account
var x = document.getElementById("Text3").value;
var y = document.getElementById("Text4").value;
var z = new Object();
z.Attributes = new Array();
z.Attributes[0] = "name";
z.Attributes[1] = "accountnumber";
alert(z.Attributes);
iCallID = form1.CRM.callService(myResults, "Retrieve", x,y,z);
Thanks again,
Andre
"Michael Höhne" <michael.hoehne@nospam.nospam> schrieb im Newsbeitrag
news:%23OyJ3kg8GHA.1252@TK2MSFTNGP04.phx.gbl...
- Posted by Michael Höhne on October 18th, 2006
You need to look at the log files to get a better understanding why CRM
cannot process your request. Enable tracing and download the CRM Trace Log
Viewer (http://www.stunnware.com/crm2/topic....raceLogViewer). Maybe
you find the error reason or at least a hint why your call fails.
--
Michael
Web: http://www.stunnware.com/crm2
Feed: http://www.stunnware.com/crm2/atom.aspx
----------------------------------------------------------
"Andre Grumbach" <Andre.Grumbach@nospam.de> schrieb im Newsbeitrag
news:OIQXVLp8GHA.1256@TK2MSFTNGP04.phx.gbl...