• RohitM
  • NEWBIE
  • 25 Points
  • Member since 2011

  • Chatter
    Feed
  • 1
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 5
    Questions
  • 5
    Replies

Hi all,

 

I am trying to create a simple report on Cases. I've used the "Create New Report" button and then selected "Cases" from the "Customer Support Reports" section. In the report builder, I can't drag and drop the fields at all. When I drag a field on to the columns section, the field becomes "red" and goes back to the left panel when I drop it.

 

Am I missing something ?





 

Thanks,

Rohit

Hello everyone,

 

We are looking to display an alert message of some sort to the user and were glad to find a Highlights Panel in Opportunity page layout. We've added a few fields that are globally visible - like the account name, just to see whether it fits our design but the panel doesn't show up on the detail page. Is there any other permission needed to get this enabled ? I've checked user permissions and profiles and no special permission seems to exist for Highlights Panel.

 

Here's what I've done:

1. Edit the page layout on an Opportunity 'X'

2. Customize the Highlights panel and add a few fields like Name, Amount, Stage

3. Save the page layout and refresh the Opportunity 'X'.

 

Am I missing something ?

 

-Rohit

Hi all,

 

I have irritating time debugging issues whenever I use the new developer console. The problem is that the logs don't show up whenever there's an active trigger.

 

For example, if I am writing a simple code to insert an account and there's an acive trigger on the account then the logs won't open. I get a random error message : "Error: Open request failed. 210351096-7846 (-1439493276)"

Whenever I deactivate the trigger, it works fine.

 

I am not sure if this has got something to do with the size of the logs.

 

Is anyone else facing same problem ? The older sysem log was better

 

 

-Rohit

 

  • February 07, 2012
  • Like
  • 0

Hi all,

 

We've got the Winter '12 release recently and have some issues with the new System Console (the "Developer Console"). I've written a test class for one of our controllers and had to change it to general Apex class to check out the system  logs. However, after running the class, I am unable to open the log as it fails loading with the error : "Error: Open request failed 382644515-103 (-1439493253)". The numbers change every time I double click the log to view.

 

Steps:

1. I have written a small test class which was later converted to an apex class :

public with sharing class PicklistTester{ 

public void getItems() {
        Account acc1 = new Account();
        acc1.Name = 'Test GetItems 1';
        Database.SaveResult sr = Database.insert(acc1);
        Id acc1Id = sr.getId();  
...
// No asserts here - only printing the values fetched.
...
}

}

 2. Go to Developer consoler (My Name -> Developer Consoler) and execute it:

PicklistTester pt = new PicklistTester();
pt.getItems();

 3. Double click on the log entry. Error follows:

Error: Open request failed

382644515-179 (-1439493253)

 

Earlier, when we got such error with this new console, we used the "Old system log" option and it was showing fine in that. Now that the old system log option is removed, does anyone know how to view the log ?

  • January 24, 2012
  • Like
  • 0

Hi all,

 

I am trying to invoke an external webservice from SFDC. I've imported the WSDL and generated APEX classes out of it. We are using certificate based authentication and hence I've given the certificate name in the apex client code too. However, when I invoke the external service, I found that the request doesn't have ANY namespace associated with it. (I got to know this from the logs at the external service end. Is there any way to log the request being sent from SFDC ? )

 

Expected request:

<env:Envelope>
<env:Header/>
<env:Body>
<QuoteRequest xmlns="http://www.aaa.com/aaa/QuoteRequest.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" end-customer-name="TEA CONSULTANTS, INC." standard-deal-status="Not Submitted" xsi:schemaLocation="http://www.aaa.com/aaa/QuoteRequest.xsd http://www.aaa.com/aaa/QuoteRequest.xsd"> <StandardRequestDetail product-type="Product"/> <StandardRequestDetail product-type="Product"/> </QuoteRequest>
</env:Envelope>
</env:Body>

 Actual request from SFDC :

<env:Envelope>
<env:Header/>
<env:Body>
<m:QuoteRequest standard-deal-status="Not Submitted" end-customer-name="TEA CONSULTANTS, INC.">
<StandardRequestDetail product-type="Product" />
<StandardRequestDetail product-type="Product" />
</m:QuoteRequest>
</env:Body>
</env:Envelope>

 As we can see, the QuoteRequest is marked with namespace 'm' in the actual request from SFDC, but the namespace reference 'm' doesn't have any namespace attached to it.

I've read some of the previous posts regarding this error but failed to find a solution. I've found that someone asked the elementFormDefault value of the XSD be changed to "qualified" but that didn't work either.

 

WSDL:

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
	xmlns:s0="http://www.aaa/aaa/QuoteResponse.xsd"
	xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
	xmlns:tm="http://microsoft/wsdl/mime/textMatching/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
	xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.aaa/aaa/QuoteRequest.xsd"
	xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.aaa/aaa/QuoteRequest.xsd"
	xmlns="http://schemas.xmlsoap.org/wsdl/">
	<types>
		<xs:schema targetNamespace="http://www.aaa/aaa/QuoteResponse.xsd"
			version="2.0" xmlns="http://www.aaa/aaa/QuoteResponse.xsd"
			xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
			<xs:element name="QuoteResponse" type="QuoteResponseType" />

			<xs:complexType name="QuoteResponseType">
				<xs:sequence>
					<xs:element maxOccurs="1" minOccurs="1"
						name="PaymentOptionsTable" type="PaymentOptionsTableType" />
					<xs:element maxOccurs="1" name="Description">
						<xs:simpleType>
							<xs:restriction base="xs:string" />
						</xs:simpleType>
					</xs:element>
					<xs:element maxOccurs="1" name="ErrorMessage">
						<xs:simpleType>
							<xs:restriction base="xs:string">
								<xs:maxLength value="2000" />
							</xs:restriction>
						</xs:simpleType>
					</xs:element>
				</xs:sequence>			
			</xs:complexType>
		</xs:schema>
		<xs:schema targetNamespace="http://www.aaa/aaa/QuoteRequest.xsd"
			version="2.0" xmlns="http://www.aaa/aaa/QuoteRequest.xsd"
			xmlns:xs="http://www.w3.org/2001/XMLSchema">

			<xs:element name="QuoteRequest" type="QuoteRequestType" />

			<xs:complexType name="QuoteRequestType">
				<xs:sequence>
					<xs:element maxOccurs="unbounded" minOccurs="0"
						ref="StandardRequestDetail" />
				</xs:sequence>
				<xs:attribute name="end-customer-name" use="optional">
					<xs:simpleType>
						<xs:restriction base="xs:string">
							<xs:maxLength value="50" />
						</xs:restriction>
					</xs:simpleType>
				</xs:attribute>
				<xs:attribute name="standard-deal-status" use="optional">
					<xs:simpleType>
						<xs:restriction base="xs:string">
							<xs:maxLength value="50" />
						</xs:restriction>
					</xs:simpleType>
				</xs:attribute>
			</xs:complexType>

			<xs:element name="StandardRequestDetail" type="StandardRequestDetailType" />

			<xs:complexType name="StandardRequestDetailType">
				<xs:attribute name="product-type" use="optional">
					<xs:simpleType>
						<xs:restriction base="xs:string">
							<xs:maxLength value="50" />
						</xs:restriction>
					</xs:simpleType>
				</xs:attribute>
			</xs:complexType>		

		</xs:schema>
	</types>
	<message name="APricingServiceHandlerIn">
		<part name="parameters" element="tns:QuoteRequest" />
	</message>
	<message name="APricingServiceHandlerOut">
		<part name="parameters" element="s0:QuoteResponse" />
	</message>
	<portType name="APricingService">
		<operation name="APricingServiceHandler">
			<input message="tns:APricingServiceHandlerIn" />
			<output message="tns:APricingServiceHandlerOut" />
		</operation>
	</portType>
	<binding name="APricingService" type="tns:APricingService">
		<soap:binding style="document"
			transport="http://schemas.xmlsoap.org/soap/http" />
		<operation name="APricingServiceHandler">
			<soap:operation soapAction="ccxRequest" style="document" />
			<input>
				<soap:body use="literal" parts="parameters" />
			</input>
			<output>
				<soap:body use="literal" parts="parameters" />
			</output>
		</operation>
	</binding>
	<service name="APricingService">
		<port name="APricingService" binding="tns:APricingService">
			<soap:address
				location="http://aaa/aaa/pricingService" />
		</port>
	</service>
</definitions>

 

Any help ?

 

 

 

Cheers,

Rohit M

Hi all,

 

I am trying to create a simple report on Cases. I've used the "Create New Report" button and then selected "Cases" from the "Customer Support Reports" section. In the report builder, I can't drag and drop the fields at all. When I drag a field on to the columns section, the field becomes "red" and goes back to the left panel when I drop it.

 

Am I missing something ?





 

Thanks,

Rohit

Hello everyone,

 

We are looking to display an alert message of some sort to the user and were glad to find a Highlights Panel in Opportunity page layout. We've added a few fields that are globally visible - like the account name, just to see whether it fits our design but the panel doesn't show up on the detail page. Is there any other permission needed to get this enabled ? I've checked user permissions and profiles and no special permission seems to exist for Highlights Panel.

 

Here's what I've done:

1. Edit the page layout on an Opportunity 'X'

2. Customize the Highlights panel and add a few fields like Name, Amount, Stage

3. Save the page layout and refresh the Opportunity 'X'.

 

Am I missing something ?

 

-Rohit

Hi all,

 

I have irritating time debugging issues whenever I use the new developer console. The problem is that the logs don't show up whenever there's an active trigger.

 

For example, if I am writing a simple code to insert an account and there's an acive trigger on the account then the logs won't open. I get a random error message : "Error: Open request failed. 210351096-7846 (-1439493276)"

Whenever I deactivate the trigger, it works fine.

 

I am not sure if this has got something to do with the size of the logs.

 

Is anyone else facing same problem ? The older sysem log was better

 

 

-Rohit

 

  • February 07, 2012
  • Like
  • 0

Hi all,

 

We've got the Winter '12 release recently and have some issues with the new System Console (the "Developer Console"). I've written a test class for one of our controllers and had to change it to general Apex class to check out the system  logs. However, after running the class, I am unable to open the log as it fails loading with the error : "Error: Open request failed 382644515-103 (-1439493253)". The numbers change every time I double click the log to view.

 

Steps:

1. I have written a small test class which was later converted to an apex class :

public with sharing class PicklistTester{ 

public void getItems() {
        Account acc1 = new Account();
        acc1.Name = 'Test GetItems 1';
        Database.SaveResult sr = Database.insert(acc1);
        Id acc1Id = sr.getId();  
...
// No asserts here - only printing the values fetched.
...
}

}

 2. Go to Developer consoler (My Name -> Developer Consoler) and execute it:

PicklistTester pt = new PicklistTester();
pt.getItems();

 3. Double click on the log entry. Error follows:

Error: Open request failed

382644515-179 (-1439493253)

 

Earlier, when we got such error with this new console, we used the "Old system log" option and it was showing fine in that. Now that the old system log option is removed, does anyone know how to view the log ?

  • January 24, 2012
  • Like
  • 0

Hello,

 

I am generating two  from a WSDL file, the code seems ok but when I create a message and send that message to the end point the "Lead" node does not have a namespace associated with it. If I get an instance of that WSDL using XML-spy I get a different xml instance, one that has the "Lead" node with the proper namespace and that one gets validated correctly.

Does anybody know why the message created from the APEX classes does not tag the "lead"node with a namespace? Do I need to alter a value from the class generated by APEX? Or Do I need to modify something in WSDL file before generating the classes?

 

Thanks,

Eduardo

 

Apex message send (fails):

<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <env:Header/>
 <env:Body>
  <ScoreLeadBiztalk xmlns="http://tempuri.org/">
   <Lead>
    <Id xmlns="http://ApexService.Lead">00Q3000000Tat8f</Id>
   </Lead>
  </ScoreLeadBiztalk>
 </env:Body>
</env:Envelope>

XML-Spy instance (works):

 

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:m0="http://ApexService.Lead">
 <SOAP-ENV:Body>
  <m:ScoreLeadBiztalk xmlns:m="http://tempuri.org/">
   <m0:Lead>
    <m0:Id>123</m0:Id>
   </m0:Lead>
  </m:ScoreLeadBiztalk>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

WSDL file:

<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://tempuri.org/" xmlns:s1="http://ApexService.Lead" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://tempuri.org/">
 <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">BizTalk assembly "ApexService, Version=1.0.0.0, Culture=neutral, PublicKeyToken=5962b974ab64847c" published web service.</wsdl:documentation>
 <wsdl:types>
  <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/">
   <s:import namespace="http://ApexService.Lead"/>
   <s:element name="ScoreLeadBiztalk">
    <s:complexType>
     <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" ref="s1:Lead"/>
     </s:sequence>
    </s:complexType>
   </s:element>
   <s:element name="ScoreLeadBiztalkResponse">
    <s:complexType>
     <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" ref="s1:Lead"/>
     </s:sequence>
    </s:complexType>
   </s:element>
  </s:schema>
  <s:schema elementFormDefault="qualified" targetNamespace="http://ApexService.Lead">
   <s:element name="Lead">
    <s:complexType>
     <s:sequence>
      <s:element minOccurs="0" maxOccurs="1" name="Id" type="s:string"/>
     </s:sequence>
    </s:complexType>
   </s:element>
  </s:schema>
 </wsdl:types>
 <wsdl:message name="ScoreLeadBiztalkSoapIn">
  <wsdl:part name="parameters" element="tns:ScoreLeadBiztalk"/>
 </wsdl:message>
 <wsdl:message name="ScoreLeadBiztalkSoapOut">
  <wsdl:part name="parameters" element="tns:ScoreLeadBiztalkResponse"/>
 </wsdl:message>
 <wsdl:portType name="WebService_ApexServiceSoap">
  <wsdl:operation name="ScoreLeadBiztalk">
   <wsdl:input message="tns:ScoreLeadBiztalkSoapIn"/>
   <wsdl:output message="tns:ScoreLeadBiztalkSoapOut"/>
  </wsdl:operation>
 </wsdl:portType>
 <wsdl:binding name="WebService_ApexServiceSoap" type="tns:WebService_ApexServiceSoap">
  <soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
  <wsdl:operation name="ScoreLeadBiztalk">
   <soap:operation soapAction="http://tempuri.org/WebService_ApexService/ScoreLeadBiztalk" style="document"/>
   <wsdl:input>
    <soap:body use="literal"/>
   </wsdl:input>
   <wsdl:output>
    <soap:body use="literal"/>
   </wsdl:output>
  </wsdl:operation>
 </wsdl:binding>
 <wsdl:service name="WebService_ApexService">
  <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">BizTalk assembly "ApexService, Version=1.0.0.0, Culture=neutral, PublicKeyToken=5962b974ab64847c" published web service.</wsdl:documentation>
  <wsdl:port name="WebService_ApexServiceSoap" binding="tns:WebService_ApexServiceSoap">
   <soap:address location="/ApexService/WebService_ApexService.asmx"/>
  </wsdl:port>
 </wsdl:service>
</wsdl:definitions>

 

Two APEX classes :

 

//Generated by wsdl2apex

public class apexWrapper {
    public class WebService_ApexServiceSoap {
        public String endpoint_x = '/ApexService/WebService_ApexService.asmx';
        public Map<String,String> inputHttpHeaders_x;
        public Map<String,String> outputHttpHeaders_x;
        public String clientCertName_x;
        public String clientCert_x;
        public String clientCertPasswd_x;
        public Integer timeout_x;
        private String[] ns_map_type_info = new String[]{'http://ApexService.Lead', 'apexLead', 'http://tempuri.org/', 'apexWrapper'};
        public apexLead.Lead_element ScoreLeadBiztalk(apexLead.Lead_element Lead) {
            apexWrapper.ScoreLeadBiztalk_element request_x = new apexWrapper.ScoreLeadBiztalk_element();
            apexWrapper.ScoreLeadBiztalkResponse_element response_x;
            request_x.Lead = Lead;
            Map<String, apexWrapper.ScoreLeadBiztalkResponse_element> response_map_x = new Map<String, apexWrapper.ScoreLeadBiztalkResponse_element>();
            response_map_x.put('response_x', response_x);
            WebServiceCallout.invoke(
              this,
              request_x,
              response_map_x,
              new String[]{endpoint_x,
              'http://tempuri.org/WebService_ApexService/ScoreLeadBiztalk',
              'http://tempuri.org/',
              'ScoreLeadBiztalk',
              'http://tempuri.org/',
              'ScoreLeadBiztalkResponse',
              'apexWrapper.ScoreLeadBiztalkResponse_element'}
            );
            response_x = response_map_x.get('response_x');
            return response_x.Lead;
        }
    }
    public class ScoreLeadBiztalk_element {
        public apexLead.Lead_element Lead;
        private String[] Lead_type_info = new String[]{'Lead','http://ApexService.Lead','Lead_element','0','1','false'};
        private String[] apex_schema_type_info = new String[]{'http://tempuri.org/','true','false'};
        private String[] field_order_type_info = new String[]{'Lead'};
    }
    public class ScoreLeadBiztalkResponse_element {
        public apexLead.Lead_element Lead;
        private String[] Lead_type_info = new String[]{'Lead','http://ApexService.Lead','Lead_element','0','1','false'};
        private String[] apex_schema_type_info = new String[]{'http://tempuri.org/','true','false'};
        private String[] field_order_type_info = new String[]{'Lead'};
    }
}

 

//Generated by wsdl2apex

public class apexLead {
    public class Lead_element {
        public String Id;
        private String[] Id_type_info = new String[]{'Id','http://www.w3.org/2001/XMLSchema','string','0','1','false'};
        private String[] apex_schema_type_info = new String[]{'http://ApexService.Lead','true','false'};
        private String[] field_order_type_info = new String[]{'Id'};
    }
}