New answers tagged

0

getting the similar error with CS65 going back to the login page even after entering the correct credentials checked with other Dev instances it is working fine. Checked Connected apps changed IP restrictions to relax ip restrictions for workbench still unable to connect


1

There shouldn't be a payload here: data: { fields: 'Name' }, This is because you can't use GET with a HTTP Body. Remove that and your code should work fine. Edit: Your query is also missing the quotes: 'https://tahina-test2-dev-ed.my.salesforce.com/services/data/v48.0/query?q=SELECT+Product2Id,+Product2.Name+from+Pricebookentry+WHERE+...


0

You can retrieve them as if they were packages. This is as simple as: sfdx force:source:retrieve -n "My Change Set Name" Or sfdx force:mdapi:retrieve -r "outputDir" -p "My Change Set Name" Depending on if you want Source or MDAPI format. Note that the Source format is recommended if you want to later create Unlocked Packages ...


0

Another way to access the Tooling API via Apex is by simply establishing an HTTP connection and sending your query to /services/data/v48.0/tooling/query/?q=Select.... To see a full example of this (as well as deserializing the JSON response to access the data) see Audit Salesforce Org with Tooling API. Here's a general gist of how it will work using an ...


0

Workbench is an open-source free tool and is not officially supported by Salesforce. Streaming API subscription with Workbench is sometimes flaky and salesforce no longer recommends using Workbench. Please use the EMP Connector, which is a Java client tool and also open-source: github.com/forcedotcom/EMP-Connector to fix the issue. Example: https://developer....


Top 50 recent answers are included