One thing I noticed while using the Logic App Standard Designer is how it wrongly handles the PathTemplate when you’re working with an APIM connector.
When you choose an operation—let’s say CapitalCity—it comes with a predefined PathTemplate. For example, /CapitalCity. That part works fine. But here’s the catch: if you start with one operation and then later change to another (like CountriesUsingCurrency), the PathTemplate doesn’t automatically update. It still points to the original one.
Here’s a simple example to illustrate.
I’ve got a Logic App workflow using an API Connector with the CapitalCity operation. I pass in the country code PT (for Portugal)
Now the response tells me that the capital is Lisbon. Perfect!
But let’s say I realize this isn’t the operation I actually want. Instead, I need to use CountriesUsingCurrency to find out which countries use Euro.
So I go back into the Designer and select the new operation.
Now here’s where the problem comes in: if I save the Logic App and look at the Code View, I can see that the PathTemplate still says /CapitalCity, even though I’ve clearly switched to a different operation.
If I run the Logic App like this, the run might still be marked as successful (which can be misleading), but the result won’t make sense. In this case, it says the country wasn’t found, because it’s still trying to hit /CapitalCity instead of /CountriesUsingCurrency.
How can we solve this?
There is a simple solution, you just need to change your PathTemplate into the correct one, If you’re unsure what the correct path is, you can always go to your APIM instance, open the operation details, and copy the right PathTemplate.
In this case, it’s literally just /CountriesUsingCurrency.
So all you need to do now is change this in your Logic App Standard workflow, you can enter into the code View and remove the template name /CapitalCity.
And replace it with /CountriesUsingCurrency
Once you make that change, save the Logic App and run it again
Now you’ll get the correct result—the list of countries that use the Euro because the operation and the path are finally aligned.
It’s a small detail, but it can really throw things off if you don’t catch it. So any time you switch operations in an APIM connector, it’s worth double-checking the PathTemplate in Code View to make sure it matches.
Hope this helps avoid a bit of head-scratching!
Is This a Bug?
In my opinion, yes—this feels like a bug. When changing an operation in the Logic App Standard Designer, the associated PathTemplate should update automatically to reflect the new selection. The fact that it doesn’t can lead to misleading behavior, especially since runs can still appear as “successful” even though the request hits the wrong endpoint, and even if it has failed can cause you a headache trying to find the solution. Hopefully, this is something Microsoft will address in a future update.
Hope you have enjoyed this Friday Fact!
To lazy to read? We’ve got you covered! Check out our video version of this content!
Hope you find this helpful! If you enjoyed the content or found it useful and wish to support our efforts to create more, you can contribute towards purchasing a Star Wars Lego for Sandro’s son!
