I have a composite app integrated with SFDC will a Web Integration Link (WIL.  (I'm accessing Sforce using Java with Axis 1.1.)

I noticed Saturday that it was not working using API 2.5 so I upgraded to the WSDL 3.0 and regenerated the Sforce client stubs.  This did fix the initial problems I was seeing.  (If you are currious, I was getting complaints about "nameField", which is a new element in Field in WSDL 3.0, even though I was still using 2.5).  

However further testing using 3.0 revealed an intermittent problem which I have not been able to work around.  I sometimes get the error back from the Sforce server saying that the session id is bad.

INVALID_SESSION_ID: Invalid Session ID found in SessionHeader

Using tcpmon I have compared traces of runs where it works and where it does not work.  The server will return this error with no changes on the client side.  It will work, then not work, then work again.  So it does not appear to be a problem with the session ID obtained from the WIL, nor with the client request.  I am thinking there is an intermittent issue on the Sforce server.

Please advise.

--SergeantAgni

I'm suddenly finding the UI and the API server are going very slow.  Is there a problem in progress?

11:30 AM Tuesday Feb 17, 2004.

Thanks

--Brad

My assumption from reading the SForce API documentation is that the IDs for the various SObjects are unique only within that SF account.  So a campaign ID from my account might be the same as a campaign ID for a campaign from some other SF account.

Is this correct?

 

In this message I'm using SF Account to mean the SFDC user account, not the Sforce Account object.  Don't know how else to phrase this, though it is confusing.

I'm building a composite application that is triggered via a SFDC Web Integration Link (WIL) and runs in the SFDC UI frame.  Multiple users from different SF accounts will use this composite application.  I need to be able to reliably identify/distinguish the account of the current user in order to organize and store info that is common to all users of that account.  I can find no way of doing this using the WIL or the SF API (version 2.5).  I must be missing something as the inability to do this is a show stopper for many types of applications.  Others must have figured this out.  What am I missing?

Note: the Organization Name available from the WIL can be changed by the user and so is not a reliable identifier.  If there were an Organization ID that was unique across all SF accounts (organizations?) and available via the WIL then the problem would be solved.

Suggestions?

--Brad

While querying from Organization I recieve the following fault from Axis which reports Oracle errors on the server:

org.apache.axis.AxisFault: java.sql.SQLException: ORA-00904: "ORGANIZATION"."WEB_TO_CASE_DEFAULT_ORIGIN": invalid identifier
ORA-06512: at "BUILD132R5.CAPICURSOR", line 136
ORA-06512: at line 1

The problem appears to be triggered by any query that includes the Organization field 'WebToCaseDefaultOrigin'.

--Brad

I'm porting to the new partner API, using Java and Axis 1.1.  Things were going fine then I started hitting the exception listed below.  I went back and ran a simple global describe script that was working earlier in the day and got the same exception.  Is is possible that something has changed with the server side certificates?  I would not expect a certificate to work and then stop working a few minutes later...

Actually, this traceback is from API version 2.0, but the 2.5 traceback is nearly the same.  Both versions are now doing the same thing.

javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Could not find trusted certificate
        at org.apache.axis.AxisFault.makeFault(AxisFault.java:129)
        at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:131)
        at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
        at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
        at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
        at org.apache.axis.client.Call.invoke(Call.java:2553)
        at org.apache.axis.client.Call.invoke(Call.java:2248)
        at org.apache.axis.client.Call.invoke(Call.java:2171)
        at org.apache.axis.client.Call.invoke(Call.java:1691)
        at salesforce.SalesforceConnectorBindingStub.login(SalesforceConnectorBindingStub.java:413)

Message Edited by SergeantAgni on 01-07-2004 04:45 PM

Any plans for samples using the Sforce Partner WS API?  The current samples appear to be for only the Enterprise version.

I'm just starting out to use the SForce API.  I'm using Java, Axis, and Jython.  My filter query calls to contact entities are working fine, but the same code used for campaign and lead enties reports bad field names for several fields that are listed as permitted by the coresponding describe calls.  For example, below is the error message when the select list of a filter query on a campaign entity includes only the "id" and "name" fields.

AxisFault
 faultCode: 1218
 faultSubcode:
 faultString: Bad field name 'name' in select list of query call
Bad field name 'name' in select list of query call

I would imagine I'm making an obvious or common mistake.  Thanks for your help.

--Brad

I have a composite app integrated with SFDC will a Web Integration Link (WIL.  (I'm accessing Sforce using Java with Axis 1.1.)

I noticed Saturday that it was not working using API 2.5 so I upgraded to the WSDL 3.0 and regenerated the Sforce client stubs.  This did fix the initial problems I was seeing.  (If you are currious, I was getting complaints about "nameField", which is a new element in Field in WSDL 3.0, even though I was still using 2.5).  

However further testing using 3.0 revealed an intermittent problem which I have not been able to work around.  I sometimes get the error back from the Sforce server saying that the session id is bad.

INVALID_SESSION_ID: Invalid Session ID found in SessionHeader

Using tcpmon I have compared traces of runs where it works and where it does not work.  The server will return this error with no changes on the client side.  It will work, then not work, then work again.  So it does not appear to be a problem with the session ID obtained from the WIL, nor with the client request.  I am thinking there is an intermittent issue on the Sforce server.

Please advise.

--SergeantAgni

In this message I'm using SF Account to mean the SFDC user account, not the Sforce Account object.  Don't know how else to phrase this, though it is confusing.

I'm building a composite application that is triggered via a SFDC Web Integration Link (WIL) and runs in the SFDC UI frame.  Multiple users from different SF accounts will use this composite application.  I need to be able to reliably identify/distinguish the account of the current user in order to organize and store info that is common to all users of that account.  I can find no way of doing this using the WIL or the SF API (version 2.5).  I must be missing something as the inability to do this is a show stopper for many types of applications.  Others must have figured this out.  What am I missing?

Note: the Organization Name available from the WIL can be changed by the user and so is not a reliable identifier.  If there were an Organization ID that was unique across all SF accounts (organizations?) and available via the WIL then the problem would be solved.

Suggestions?

--Brad

While querying from Organization I recieve the following fault from Axis which reports Oracle errors on the server:

org.apache.axis.AxisFault: java.sql.SQLException: ORA-00904: "ORGANIZATION"."WEB_TO_CASE_DEFAULT_ORIGIN": invalid identifier
ORA-06512: at "BUILD132R5.CAPICURSOR", line 136
ORA-06512: at line 1

The problem appears to be triggered by any query that includes the Organization field 'WebToCaseDefaultOrigin'.

--Brad

I'm porting to the new partner API, using Java and Axis 1.1.  Things were going fine then I started hitting the exception listed below.  I went back and ran a simple global describe script that was working earlier in the day and got the same exception.  Is is possible that something has changed with the server side certificates?  I would not expect a certificate to work and then stop working a few minutes later...

Actually, this traceback is from API version 2.0, but the 2.5 traceback is nearly the same.  Both versions are now doing the same thing.

javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Could not find trusted certificate
        at org.apache.axis.AxisFault.makeFault(AxisFault.java:129)
        at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:131)
        at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
        at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
        at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
        at org.apache.axis.client.Call.invoke(Call.java:2553)
        at org.apache.axis.client.Call.invoke(Call.java:2248)
        at org.apache.axis.client.Call.invoke(Call.java:2171)
        at org.apache.axis.client.Call.invoke(Call.java:1691)
        at salesforce.SalesforceConnectorBindingStub.login(SalesforceConnectorBindingStub.java:413)

Message Edited by SergeantAgni on 01-07-2004 04:45 PM

I'm just starting out to use the SForce API.  I'm using Java, Axis, and Jython.  My filter query calls to contact entities are working fine, but the same code used for campaign and lead enties reports bad field names for several fields that are listed as permitted by the coresponding describe calls.  For example, below is the error message when the select list of a filter query on a campaign entity includes only the "id" and "name" fields.

AxisFault
 faultCode: 1218
 faultSubcode:
 faultString: Bad field name 'name' in select list of query call
Bad field name 'name' in select list of query call

I would imagine I'm making an obvious or common mistake.  Thanks for your help.

--Brad

I am trying to figure out how to get the data that I see in the reports using SOAP.  Specifically I want to get the data returned from the "Opportunity Pipeline" report.  What is the procedure that I should follow to get the data from a named report?

Hi,

Is there a way to get the Organization ID of the Users (ID of the organization to which the users belong)? What kind of a permission would be needed to get this information? Also I went through the SForce API 2.0 and specifically through the ERD's but could not locate an entity by the name of Organization. Is there a different name for it or something that I'm missing?


Regards,
Vineet Gogia
Theikos.