Everything works fine, except in the WSDL (e.g. https://dockerhost/devsoap/WS/CRONUS%20DE/Codeunit/WorkflowActionResponse) in this case a different WorkflowActionResponse_Port at the end is listed: https://dockerhost:7047/BC/WS/CRONUS%20DE/Codeunit/WorkflowActionResponse
This confuses Visual Studio if you what to utilize this SOAP Web Service. (You must set the soapclient.URL = "https://dockerhost/devsoap/WS/CRONUS%20DE/Codeunit/WorkflowActionResponse".) It would be nice if these addresses would be correct.
Comments
Sorry, the title is wrong. It should be "WSDL should contain the correct PublicSOAPBaseUrl".
But OData has the same issue:
If you use the NAVContainerHelper with Docker and Traefik, the NAVContainerHelper sets the PublicODataBaseUrl to https://dockerhost/devrest/odata.
Everything works fine, except in the AtomFeed (e.g. https://dockerhost/devrest/OData/Company('CRONUS%20DE')/SalesDashboard) and the JSON (e.g. https://dockerhost/devrest/ODataV4/Company('CRONUS%20DE')/SalesDashboard) have wrong references. In this case https://dockerhost/BC/OData/ and https://dockerhost/BC/ODataV4/$metadata#Company('CRONUS%20DE')/SalesDashboard
This confuses consumer of this OData Web Services. It would be nice if these addresses would be correct.
Category: Tenant Administration
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team