Sign Up ›
  • MazA
  • NEWBIE
  • 0 Points
  • Member since 2006
  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 5
    Questions
  • 8
    Replies
0 replies

Email to case

Hi guys,
 
I've been asked to implement the 'Web to Case' feature for our company. I've used the SalesForce API before for leads, opportunities...etc so I'm familiar with it. I'm look at the following http://blogs.salesforce.com/features/2006/06/email_managemen.html and there is a Java Toolkit that does this. Does anyone know one for .NET (C#)? If I was to write one, how would I go about bringing all the pieces together? It there one main documentation that would tell me what to do?
 
The two Flash demos (Email Management for Administrators, Email Management for Support Reps ) just show me how to setup the salesforce side.
 
Are these the step?
1. Write an IMAP email reader that can read emails at regular intervals
2. Parse emails based on content (What keys am I looking for here in the email?)
3. Use SF API to inject this data into SalesForce.
 
Am I missing something here? Do you guys have a sample code using ASP.NET?
 
Thanks
Maz
 
 
  • November 28, 2007
  • Like
  • 0
2 replies

CS0117: 'site.sforce.Lead' does not contain a definition for 'Amount__c'

Hi everyone,
 
I've been using webservices to connect to salesforce (CRM) API for over a year now and today I added a new field 'Amount' to the salesforce and extracted the WDSLfile. On my local system running Window XP I did a Web References Update and everything worked fine. However, on our production server running Windows 2003 Server I got the following error message.
CS0117: 'site.sforce.Lead' does not contain a definition for 'Amount__c'
Ex.
...
lead.Description = Description;
lead.Amount__c = Amount;  // Only this fails. Works when I remove this line.
...
Why is that? Why on Windows 2003 Server and not on XP? I restarted IIS services as well too and still get the same problem.
Any suggestions?
 
Thanks
Maz.
 
  • August 08, 2006
  • Like
  • 0
1 replies

Creating a new Appexchange app from scratch

Hi everyone,
 
I'm sort of new to salesforce but have a limited exprience with sforce API. I like to write a small app for our company and all the articles that I see talk about it either in general or they talk about how to deploy it in salesforce. I have the following question that would really appreciate it if someone out there answered.
 
I'm using Visual Studio 2005 and need to know how to start writing this App that's executable on Salesforce.
 
Do I just create a web app (aspx) and if it works assume it would work on the Appexchange network? Don't I have to follow certains rules for compatibility? Am I totally off the path here? If so please provide me with some information on how to start (prefereably asp.net) .
 
BTW, I've already created a complete Partner Portal that's running on our server (which was easy using Salesforce API).
 
Thank you
Maz
 
  • May 26, 2006
  • Like
  • 0
1 replies

Creating a new Appexchange app from scratch

Hi everyone,
 
I'm sort of new to salesforce but have a limited exprience with sforce API. I like to write a small app for our company and all the articles that I see talk about it either in general or they talk about how to deploy it in salesforce. I have the following question that would really appreciate it if someone out there answered.
 
I'm using Visual Studio 2005 and need to know how to start writing this App that's executable on Salesforce.
 
Do I just create a web app (aspx) and if it works assume it would work on the Appexchange network? Don't I have to follow certains rules for compatibility? Am I totally off the path here? If so please provide me with some information on how to start (prefereably asp.net) .
 
BTW, I've already created a complete Partner Portal that's running on our server (which was easy using Salesforce API).
 
Thank you
Maz
 
  • May 26, 2006
  • Like
  • 0
2 replies

Creating an AppExchange App

Hi everyone,
 
I'm sort of new to salesforce but have a limited exprience with sforce API. I like to write a small app for our company and all the articles that I see talk about it either in general or they talk about how to deploy it in salesforce. I have the following question that would really appreciate it if someone out there answered.
 
I'm using Visual Studio 2005 and need to know how to start writing this App that's executable on Salesforce.
 
Do I just create a web app (aspx) and if it works assume it would work on the Appexchange network? Don't I have to follow certains rules for compatibility? Am I totally off the path here? If so please provide me with some information on how to start (prefereably asp.net) .
 
BTW, I've already created a complete Partner Portal that's running on our server (which was easy using Salesforce API).
 
Thank you
Maz
 
  • May 26, 2006
  • Like
  • 0
2 replies

CS0117: 'site.sforce.Lead' does not contain a definition for 'Amount__c'

Hi everyone,
 
I've been using webservices to connect to salesforce (CRM) API for over a year now and today I added a new field 'Amount' to the salesforce and extracted the WDSLfile. On my local system running Window XP I did a Web References Update and everything worked fine. However, on our production server running Windows 2003 Server I got the following error message.
CS0117: 'site.sforce.Lead' does not contain a definition for 'Amount__c'
Ex.
...
lead.Description = Description;
lead.Amount__c = Amount;  // Only this fails. Works when I remove this line.
...
Why is that? Why on Windows 2003 Server and not on XP? I restarted IIS services as well too and still get the same problem.
Any suggestions?
 
Thanks
Maz.
 
  • August 08, 2006
  • Like
  • 0
3 replies

Retrieval error: "There is an error in XML document (1, 487)"

Whenever I try to retrieve the LastModifiedDate field of an Account, I encounter the following error: "There is an error in XML document (1, 487)". I have no problems retrieving the other fields of the Account, though.
 
Any help will be appreciated. Thanks!
  • August 07, 2006
  • Like
  • 0
10 replies

Querying for CreatedDate results in "There is an eror in XML Document" error

I am using C# to obtain case data from Salesforce in my application. I dont have any problems querying the rest of the case-related information.

When I run the following query:

QueryResult qr = binding.query("Select CreatedDate from Case where CaseNumber = '00003511'");

The following exception is thrown:

Message: There is an error in XML document (1, 477).
Trace:    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlRea
der, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, St
ring encodingStyle)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClie
ntMessage message, WebResponse response, Stream responseStream, Boolean asyncCal
l)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodN
ame, Object[] parameters)
   at SFIncidentCaseData.sforce.SforceService.query(String queryString) in <path to project>\Web References\sforce\Reference.cs:line 678
   at SFIncidentCaseData.Program.GetIncidentCaseData(String strOrgName, String s
trStartCreatedDate, String strEndCreatedDate) in <path to source  file>:line 62

Any help is appreciated!

Thanks,
Prashanth
31 replies

System.Exception {System.FormatException}

I made this sforce.query() call...
 

m_queryArray = oSFDCQuery.ExecuteQuery("select Support_Code__c, Name, CreatedByID, CreatedDate, Amount__c, Asset_Typ__c from Asset_Activity_Log__C where AccountID__c = '00130000005CZLD' ", oLogin);

With the "CreatedDate" in the query receive the following error...

"String was not recognized as a valid DateTime." as my inner exception

The Full Stack trace is as follows....

at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)

at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle)

at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

at SFDCLibrary.Sforce.SforceService.query(String queryString)

at SFDCLibrary.SFDCQuery.ExecuteQuery(String strQuery, cLogin oLogin)

at LicenceDetails.GetActivityLog() in s:\Projects\2005\AssetManager\LicenceDetails.aspx.cs:line 102

Now when i do not have "CreatedDate" everything works fine. And the query worked fine up until this morning when i made the following change. Thru SFDC setup i adjusted my custom object. I had  field i changed from numeric(7,0) to a text field.  I downloaded a new WSDL and deployed it.

Any ideas or suggestions to what i might have done wrong?

11 replies

retrieve - there is an error in XML document

This problem has started in the last few days, with a long established program. On several objects the retrieve api call fails with "there is an error in XML document"

This is happening on account, case, contact, lead, opportunity and task objects (others appear OK). Also the error sometimes "goes away", the following is a partial trace:
TaskgetRecordDetail(1): Error: There is an error in XML document (1259, 22).
TaskgetRecordDetail(2): Error: There is an error in XML document (528, 45).
TaskgetRecordDetail(3): Error: There is an error in XML document (13050, 21).
TaskgetRecordDetail(4): Error: There is an error in XML document (3048, 6).
TaskgetRecordDetail(5): Error: There is an error in XML document (11611, 6).
TaskgetRecordDetail(6): Error: There is an error in XML document (14958, 6).
TaskgetRecordDetail(1): Error: There is an error in XML document (1337, 6).
TaskgetRecordDetail(2): Error: There is an error in XML document (14857, 5).
TaskgetRecordDetail(3): Error: There is an error in XML document (9781, 6).

My routine retries up to 10 times, primarily to compensate for network errors. But here the retry gives the same error but at a different points in the xml, finally getting a sucessful response.