• sravanthi bhavanam
  • NEWBIE
  • 5 Points
  • Member since 2016

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 4
    Questions
  • 5
    Replies
I am using Metadata API version 37 while one of our sandboxes were upgraded to v40 (Spring '17). We ran into an issue while running the statement:
ReadResult readResult = mdConnection.readMetadata("KnowledgeSettings", new String[] { "*" });


This returned KnowledgeSettings response:
<?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://soap.sforce.com/2006/04/metadata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body>
        <readMetadataResponse>
          <result>
            <records xsi:type="KnowledgeSettings">
              <fullName>*</fullName>
              <answers>
                <enableArticleCreation>false</enableArticleCreation>
            </answers>
            <cases>
                <defaultContributionArticleType>How_To</defaultContributionArticleType>
                <editor>standard</editor>
                <enableArticleCreation>true</enableArticleCreation>
                <enableArticlePublicSharingSites>false</enableArticlePublicSharingSites>
                <enableCaseDataCategoryMapping>true</enableCaseDataCategoryMapping>
                <useProfileForPDFCreation>false</useProfileForPDFCreation>
            </cases>
			---
      </readMetadataResponse>
    </soapenv:Body>
  </soapenv:Envelope>


The property enableCaseDataCategoryMapping is not available on v37 but Salesforce sends the response treating it as v40. Can this be avoided by having backward compatibility with the responses?
The issue is that this application is deployed on various environments and getting updates for every new version is quite difficult to maintain.
Hi,
describeSobjects call is giving not exist fields like LastViewedDate when we pass multiple objects like Account, custom__c. Passing single object to the describe call getting correct fields. Have anyone seen this issue before? what could be the cause?
 
How do we find if a given field is part of a Master-detail or a lookup relationship? Using SOAP API, the describesObjectResult
 has childobjects that does not have the relationship type.

 
I've been trying to download files (Documents, Attachments, ContentVersions, etc.) through Rest API.
The URL is:
https://<baseuri>/sObjects/<objname>/<id>/<bodyfield>


One of the issues encountered was that the ContentVersion files that are large in size (1.5 - 2 GB) are not downloaded completely. Tried testing it through CURL where the file download automatically closes after a certain time (10-15 minutes). This is strange since other files are downloaded and probably aren't as big as the contentversions for the issue to occur. Has anyone encountered such an issue while downloading large files and is there any way to download these files?
I am using Metadata API version 37 while one of our sandboxes were upgraded to v40 (Spring '17). We ran into an issue while running the statement:
ReadResult readResult = mdConnection.readMetadata("KnowledgeSettings", new String[] { "*" });


This returned KnowledgeSettings response:
<?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://soap.sforce.com/2006/04/metadata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body>
        <readMetadataResponse>
          <result>
            <records xsi:type="KnowledgeSettings">
              <fullName>*</fullName>
              <answers>
                <enableArticleCreation>false</enableArticleCreation>
            </answers>
            <cases>
                <defaultContributionArticleType>How_To</defaultContributionArticleType>
                <editor>standard</editor>
                <enableArticleCreation>true</enableArticleCreation>
                <enableArticlePublicSharingSites>false</enableArticlePublicSharingSites>
                <enableCaseDataCategoryMapping>true</enableCaseDataCategoryMapping>
                <useProfileForPDFCreation>false</useProfileForPDFCreation>
            </cases>
			---
      </readMetadataResponse>
    </soapenv:Body>
  </soapenv:Envelope>


The property enableCaseDataCategoryMapping is not available on v37 but Salesforce sends the response treating it as v40. Can this be avoided by having backward compatibility with the responses?
The issue is that this application is deployed on various environments and getting updates for every new version is quite difficult to maintain.
How do we find if a given field is part of a Master-detail or a lookup relationship? Using SOAP API, the describesObjectResult
 has childobjects that does not have the relationship type.

 
I've been trying to download files (Documents, Attachments, ContentVersions, etc.) through Rest API.
The URL is:
https://<baseuri>/sObjects/<objname>/<id>/<bodyfield>


One of the issues encountered was that the ContentVersion files that are large in size (1.5 - 2 GB) are not downloaded completely. Tried testing it through CURL where the file download automatically closes after a certain time (10-15 minutes). This is strange since other files are downloaded and probably aren't as big as the contentversions for the issue to occur. Has anyone encountered such an issue while downloading large files and is there any way to download these files?
Hi,
I am writing an application to ETL data from Salesforce using BULK API into our system. I am able to log in and do all the work without mutual authentication. Since mutual authentication is the added security, we want to implement it. However, I am keep getting time out error when i do the curl command with port 8443 and certificatie. Here is my command:

$ curl -k https://cs32.my.salesforce.com:8443/services/Soap/u/37.0 -H "Content-Type:text/xml;charset=UTF-8" -H "SOAPAction:login" -d @C:/apps/login.txt -v -e fullcert.pem:@C:/apps/pem_cer_cert/cert.cer

On the other hand, if i don't use port 8443 with above url, i able login successfully and get valid session ID. Suprisingly, I can't create any jobs from that session Id. I kept getting invalid session ID error when i try to create a job.

Help is really appriciated if anybody resolve this issue.

Thanks 
Vivek