In the WSDL there are parameters that start with an uppercase. But after importing the WSDL the first letter of the parameter is modified to a lower case.
Select McsBillingServices - BasicHttpBinding - BillingBlockService as interface.
Select SOAP to Rest as import method.
Click on the button create.
Select the imported API.
Select 'GetBillingBlock' in all operations.
Select 'GetBillingBlock' in defintions.
In the schema you see:
In the WSDL it's 'EAN'.
Expected behavior
Keep the WSDL as-is and don't modify the first letter of a parameter to lower case.
Is your portal managed or self-hosted?
Managed
Release tag or commit SHA (if using self-hosted version)
API Management service name
McsTestApiManagement
Environment
Operating system: windows
Browser: Google Chrome
Additional context
The WSDL is auto-generated by a Dynamics 365 Finance environment.
We're using azure API management to document the API.
We're exporting the documented APIs via yaml files.
We're sending the yaml files to one of our customers.
The tool that our customer is using, is case sensitive. And now there is a mismatch between the WSDL and the documented API.
Bug description
In the WSDL there are parameters that start with an uppercase. But after importing the WSDL the first letter of the parameter is modified to a lower case.
Reproduction steps
In the WSDL it's 'EAN'.
Expected behavior
Keep the WSDL as-is and don't modify the first letter of a parameter to lower case.
Is your portal managed or self-hosted?
Managed
Release tag or commit SHA (if using self-hosted version)
API Management service name
McsTestApiManagement
Environment
Additional context
The WSDL is auto-generated by a Dynamics 365 Finance environment. We're using azure API management to document the API. We're exporting the documented APIs via yaml files. We're sending the yaml files to one of our customers. The tool that our customer is using, is case sensitive. And now there is a mismatch between the WSDL and the documented API.