Announcements
Hi
I've been working on exposing a couple of codeunits through SOAP webservice in Business central using the XML file in AL project. It was working perfectly in all previous versions but when we tested it in April Release of Business central(14.0.29531.0-DK), it does not expose any of the public methods in the codeunits. What could have possibly gone wrong?
Following is one of the XML files being used to publish the web service in BC:
<?xml version="1.0" encoding="utf-8"?> <ExportedData> <TenantWebServiceCollection> <TenantWebService> <ObjectType>5</ObjectType> <ServiceName>ImportData</ServiceName> <ObjectID>55000</ObjectID> <Published>true</Published> </TenantWebService> </TenantWebServiceCollection> </ExportedData>
Due to the confusion this early swtich to fall image caused, the master image has now been changed to "Spring 2019+1". "Fall 2019" image will be restarted in May 2019 along with some documentation which explains what happens.
Thanks, the issue has been resolved :)
Hi Mohsin
The error we made was pulling the "next major" version - which apparently is not the next, but the Next-Next.
Try pulling this image, that is the coming Spring/April image. That works like it use to, everything is exposed as External
bcinsider.azurecr.io/bcsandbox:base
Hi Stefano
Have they preovided some hotfix for this? I am trying to expose non-local procedures but no luck.
This issue appears to be solved in latest daily build. Web services is now again exposed from extension written in AL.
To recap:
... exposing web service from *AL* extension did not work work (as per 2019-03-27) in:
master insider
bcinsider.azurecr.io/bcsandbox-master:base
Version: Platform 14.0.29487.0 + program 29581 (W1 14.0)
... but is solved for *AL* in:
daily insider
bcinsider.azurecr.io/bcsandbox:base
Version: Platform 14.0.29501.0 + Application 29551 (W1 14.0)
Checked and confirmed as in my post.
Thanks alot.
The answer you've got below, do you have a tracking ID for that?
I need to raise this with MS as we cannot continue.
Our WS are not being exposed anymore ;(
"Official MS response: if you create a codeunit in AL, you can see only the methods target as External now. In AL all should work as before (you should see all non local methods).
Can you check this please?"
All is explained here, and confirmed by MS officially:
demiliani.com/.../dynamics-365-business-central-cu04-and-soap-web-services-changements
Can confirm we got same issue. An AL extension that works in Update23 is broken in April Release, as it no longer exposes procedures in the exposed codeunit. Procedures is declared as "procedure XYZ" i.e. non-local.
I'd really appreciate if you could update me whenever you get a response from MS.
Thank you :)
André Arnaud de Cal...
294,261
Super User 2025 Season 1
Martin Dráb
232,996
Most Valuable Professional
nmaenpaa
101,158
Moderator