Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
As you already knows, Microsoft has rolled up in these days the Cumulative Update 4 for Dynamics 365 Business Central.
Unfortunately, there’s an (actually) undocumented breaking change that has affected lots of customers: if you have previously published some codeunits as SOAP web services, after this update if you try to reference your previously published web services you can’t see any methods!
Because Microsoft has decided that (for security reasons) from now if you publish a SOAP web service from Dynamics 365 Business Central, you can see only methods declared as External.
If you’re using C/AL (or you’ve previously created a codeunit by using C/AL), you can see that the default visibility of a public function (FunctionVisibility property) is set to Internal:
In this way, you will not see your functions in a SOAP web service anymore!
To fix that, you need to explicitly set with FunctionVisibility = External all the methods that must be exposed as web services:
Remember that this affects also the Microsoft’s base application: if you’ve published a Microsoft object as web service, when adding the WS reference you will see only the methods declared as External.
This behaviour does not affects pure AL codeunits, where procedures not declared as local are External as default.
Start fixing your C/AL code…
Business Applications communities