0

Salesforce web api GET and POST both were working OK before. Suddenly from today started giving following error. Noticed in the API setup API version is changed but after updating newer version code still same error.

https://XXXX.salesforce.com//services/data/v59.0/sobjects/Order_Product_Shipment__c/XXXXXXXX?_HttpMethod=PATCH

[ { "errorCode": "NOT_FOUND", "message": "The requested resource does not exist" } ]

5
  • Double check the Id that you've obscured through the normal web ui. This would be the message to expect if that particular record is deleted.
    – Derek F
    Commented Nov 6, 2023 at 22:35
  • Yes, I reverified it. Issue is still there. We are using version API call version 49.0 but app has version 59.0. Tried both version numbers but not solving the problem. Is there any specific settings needed on the server after version changed to newer version? Commented Nov 7, 2023 at 0:41
  • You have ...//services... - is that a typo? If not, that is your issue
    – cropredy
    Commented Nov 7, 2023 at 16:59
  • It has found that web api url changed not sure how come as salesforce did not send any email. New url looks like "MyDomainName.my.salesforce.com/services/data" but the original link was "otherdomainName.salesforce.com/services/data" Commented Nov 7, 2023 at 19:11
  • You should post this as an answer instead of a comment. Yes, you can officially answer your own questions! Commented Nov 7, 2023 at 19:51

1 Answer 1

0

It has found that web api url changed not sure how come as salesforce did not send any email. New url looks like "MyDomainName.my.salesforce.com/services/data" but the original link was "otherdomainName.salesforce.com/services/data"

After connecting with salesforce customer support for the url change issue, following is salesforce reply.

"As your org has been migrated to hyperforce due to which your instance has changed. Earlier it used to be "bbbb" now it has been changed to "aaaa" which caused this API call to break." It is recommended to use the my domain name instead of instance-specific url so you don't have to face any similar issue in future.

1
  • 1
    Hard-coded references to instance names (xxx.salesforce.com) are a bad practice. Migration to Hyperforce exposes this bad practice. In many notices and warnings related to migration that were sent to customers, all of them referred to How to Prepare for Org Migration doc . The doc talks about this issue in the very first 'What do I need to do' question
    – identigral
    Commented Nov 7, 2023 at 21:17

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .