Bug (??) API - post map in a solution with wrong OrgId
There seems to be a bug in the "POST map in a solutionID" endpoint ("Creat an advanced map"). If the OrgId is incorrect it still finds the way to the solution (provided the user has access to the given Org). I don't think this is WAD, as it makes a real action from an incomplete/incorrect request.
I agree this is unexpected behavior. I would expect to see an error response that the SolutionId does not exist in that Organization provided in the request.
I've opened a ticket (Case #00058232) to have our engineering team take a look into this, and add a fix to avoid unexpected results. Thanks for finding this and sharing, Nacho!
Actually, I think I see what you mean.
From what I recreated, the API is returning 200 that the call was successful to the Org# I provided in the Request URL, however, the map was actually created in the organization that owns the Solution (which is in a different Org).
Can you confirm that's what you are seeing?
Can you share any relevant code or equivalent HTTP/cURL/Postman, including the request body?
I'd like to recreate a test on my end with the same type of Solution/Map.
Help others find useful posts by selecting the best answer to your question. Click "Like" to highlight great replies.