If it works when you 'hard-code' the id but does not when you 'pull' the value in from a different step, then I can only think something about the second way is wrong.
@richie mentioned that the error number looked odd, e.g. you usually expect a 500 if you pass in an invalid value/payload. The error is actually a Swagger error. Now, I have haven't used Swagger beyond creating an account, but it's Swagger saying "No resource that matches the OpenAPI definition". In other words, it looks like your request is malformed, incorrect, or calling the wrong method etc. when you pull the value in.
Did you try what I suggested above? SoapUI request steps have a 'raw' tab which shows exactly what SoapUI sent to the API. Compare what is in the raw tab after sending hard-coded value against what is in the raw tab when you automate.
@ChrisAdams: Thanks for your time. Yes, I looked into the raw request. You were right the value in the URL is not passing correctly but the question is why it is not passing correctly? I am attaching the raw request with hardcoded and with the selecting property both. So, now our aim is why it is not sending the correct values when we are selecting from the post method.
The screenshots you attached look like theyre for different APIs (the uris differ). I agree with @ChrisAdams, but if you provided screenshots of the RAW for both requests and responses as well as logging details for any property transfer we mighe be able to help. However without this we're not gonna be able to help.
If you can supply screenshots foe everything we can probably help
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta