SOAP webservice not exposing the functions in April Release of Business Central

(0) Share

Report

Posted on by Mohsin Abbas

525

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>

Categories:

Documentation

Other

Business Central

I have the same question (0)

All responses (16)

Answers (1)

Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

You are right, you can see all the functions marked as external in C/AL.

This was signalled to MS, waiting for a response.

Was this reply helpful? Yes No
Mohsin Abbas 525 on at

Like (0)

Report

Hi Stefano

Thanks for prompt response. Are you saying that its a bug in new release? Or do I need to change something?

Thanks

Was this reply helpful? Yes No
Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

If your codeunit comes from C/AL, set the functions as External. We’re waiting a response to know if it’s a bug or a wanted behavior.

Was this reply helpful? Yes No
Mohsin Abbas 525 on at

Like (0)

Report

The codeunits are part of my app written in AL. Couldn't find any reference in docs on how to set this property for procedures in AL.

Was this reply helpful? Yes No
Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

Functions created in AL are all external as default (you don't have this property), so the problem continues... I've asked MS to give us a response.

Was this reply helpful? Yes No
Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

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?

Was this reply helpful? Yes No
Mohsin Abbas 525 on at

Like (0)

Report

I'd really appreciate if you could update me whenever you get a response from MS.
Thank you :)

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

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.

Was this reply helpful? Yes No
Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (2)

Report

All is explained here, and confirmed by MS officially:

demiliani.com/.../dynamics-365-business-central-cu04-and-soap-web-services-changements

Was this reply helpful? Yes No
JSebastian on at

Like (0)

Report

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?"

Was this reply helpful? Yes No