Skip to content

Releases: k-capehart/go-salesforce

v2.1.2

20 Sep 16:36
3496b09
Compare
Choose a tag to compare

What's Changed

  • feat: handle 300 response for when multiple matches are found for a single salesforce external id by @k-capehart in #63

Full Changelog: v2.1.1...v2.1.2

v2.1.1

16 Sep 13:59
3c494e3
Compare
Choose a tag to compare

What's Changed

  • fix linting error: printf-style function with dynamic format string and no further arguments should use print-style function instead by @k-capehart in #60
  • fix(deps): bump k8s.io/apimachinery from 0.30.3 to 0.31.0 in the dependencies group by @dependabot in #59
  • fix(deps): bump k8s.io/apimachinery from 0.31.0 to 0.31.1 in the dependencies group across 1 directory by @dependabot in #61

Full Changelog: v2.1.0...v2.1.1

v2.1.0

05 Aug 21:07
5096c4d
Compare
Choose a tag to compare

What's Changed

  • fix(deps): bump k8s.io/apimachinery from 0.30.2 to 0.30.3 in the dependencies group by @dependabot in #57
  • Refresh when Invalid Session error occurs by @k-capehart in #58
    • Shoutout to aishmuru for bringing this idea up in #56
    • When any operation fails with an Error Code of INVALID_SESSION_ID, then go-salesforce will attempt to generate a new access token by resubmitting the same credentials used during initialization
    • This fixes issues where the token would expire and require manual re-initialization

Full Changelog: v2.0.1...v2.1.0

v2.0.1

23 Jul 18:58
96fac97
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.0.0...v2.0.1

v2.0.0

23 Jul 18:43
08e9683
Compare
Choose a tag to compare

What's Changed

  • InsertOne and UpsertOne now return an instance of SalesforceResult which contains record IDs for newly created records
  • Collection and Composite methods now return an instance of SalesforceResults which contains an array of SalesforceResult and a boolean HasSalesforceErrors
  • The BulkJobResults type has been updated to include new properties: SuccessfulRecords and FailedRecords
  • If Salesforce returns a 2xx response but includes record related errors, then do not return an error in the function
    • These errors should be handled by the client by parsing through SalesforceResult
    • There is a notable exception in that if a record related error is encountered for InsertOne, UpdateOne, UpsertOne, or DeleteOne, then a 4xx response is returned by Salesforce
  • These changes allow users to easily access record IDs of newly created records and better handle record related errors

New Contributors

Huge shoutout to @0cv for submitting #42 and doing the preliminary work, as well as to @ccoVeille for always being willing to review and make recommendations.

Full Changelog: v1.0.6...v1.0.7

v1.0.6

01 Jul 14:26
32f00cf
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.0.5...v1.0.6

v1.0.5

27 Jun 20:32
a92950b
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.0.4...v1.0.5

v1.0.4

19 Jun 15:52
709b5b7
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.3...v1.0.4

v1.0.3

07 Jun 20:25
28cf9e8
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.2...v1.0.3

v1.0.2

10 May 21:22
b03426b
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.1...v1.0.2