Path Variables aren't supported when used in parentheses

[MattJenko]

Is there an existing issue for this?

• [X] I have searched the tracker for existing similar issues and I know that duplicates will be closed

Describe the Issue

When trying to interface with Microsoft Dynamics API's they like to use the following notation for REST API's GET /path/to/company(companyId)

If I create a request that attempts to use the format as the following then I don't get path variables to be able to set per request. GET /path/to/company(:companyId)

This is true even if I URL encode the parentheses GET /path/to/company%28:companyId%29

Steps To Reproduce

1. Create New Request
2. Add URL with path variable in above format: `GET https://example.com/:tenancy/companies(:companyId)/invoices

Screenshots or Videos

Operating System

macOS

Postman Version

11.1.13

Postman Platform

Postman App

User Account Type

Signed In User

Additional Context?

No response

[GauntletPL]

I'm backing this up. I also have a frequent necessity to be able to define path variables that do not directly follow the forward slash character:

{{baseUrl}}/path/to/the/resource/code=:entityCode

Being able to start your variable anywhere in the path would be a welcomed feature.

On a separate note - this is definitely not a macOS specific issue - shouldn't be flagged as such.

[MGREMY]

This could be a good feature since some public api like IFS Cloud is using this format {{BASE__URL}}/main/ifsapplications/projection/v1/UserHandling.svc/Users(Identity='Identity') When changing to {{BASE__URL}}/main/ifsapplications/projection/v1/UserHandling.svc/Users(Identity='/:Identity/'), it work but the final result looks like this {{}BASE_URL}/main/ifsapplications/projection/v1/UserHandling.svc/Users(Identity='/:Identity/'), so with the remaining /

[Xriuk]

Came across this today, a bit annoying

[nwelchbauer-disney]

+1. This used by Salesforce B2C Commerce Cloud OCAPI Shop API

/shop/products/(1234,5667,93482)

[LanaCCHP]

+1. I Too have an API that uses (), like {{baseurl}}/HSPMemberServices/Member(#)/FullProfile. Without the ability to pass parameters into the URL, my ability to automate flows in Postman will be severely limited.

[jshakya]

OData using path variables inside parentheses is not supported for me