Repository navigation
[FEATURE REQ] Support renaming named values #837
Description
Please describe the feature.
If a named value with the same displayName but a different name does already exist in APIM while publishing the following error is emitted
##[error]System.Net.Http.HttpRequestException: HTTP request to URI https://management.azure.com/subscriptions/***/resourceGroups/***/providers/Microsoft.ApiManagement/service/***/namedValues/MyNamedValue?api-version=2023-09-01-preview&asyncId=69c299e5f0b6541b0829f74c&asyncCode=201 failed with status code 400. Content is '{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"name","message":"Property with the same name already exist."}]}}'.
Currently this requires manual deletion of the existing named value before publishing succeeds. Would be nice to automatically such cases within the publisher client.
Activity
github-actions commentedon Mar 24, 2026
guythetechie commentedon Apr 1, 2026
Konrad Windszus (@kwin) - I'll add this to our list to investigate. Note that this is an APIM limitation: the portal won't let you create a named value with an already existing display name.
Can you tell me more about your use case? Are you running the publisher with a commit where the named value has been renamed? Or is this a publish all scenario (no commit id)?
kwin commentedon Apr 1, 2026
This is initial publish all after previously manually maintaining the config. The different environments had different names with same display names which leads to errors during publishing.