Legacy API has been refactored in Sugar 12.0.0

Hi Jeff,
I agree there’s a problem here with the documentation and the file you mentioned.

The functionality has been re-written from 11.2 to 11.3 to comply with Security scans and code readiness for future releases.

Our team is considering a hotfix to rename the file to lowercase as it was before.

Good deal you found a workaround to add your custom code to this SOAP API, however, we do not want anybody to use SOAP webservice any longer much less extending it. We have been advocating to move away from SOAP we will continue to do so until it is completely removed from our product.

Therefore our message to the community is: Stop using SOAP.

Sugar’s REST API is the recommended path for integrations, performant, secure and easily extendable, instructions can be found here.

Having said that, we’ve decided to remove that Extending SOAP guide from our documentation.

One further note Rafael Fernandes -

I'm in the process of migrating a customer from SuiteCRM to Sugar 12.0.0; they have a few hundred integrations that use the custom/service/v4_1_custom/rest.php integration. It's going to take them a while to migrate to the v11 API.

Rafael Fernandes using Sugar 13.0.0 Preview 1 I'm receiving an error while trying to use the /service/v4_1/rest.php class. I receive an error 

Thoughts?

 PHP Fatal error:  Uncaught Error: Object of class SugarWebServiceUtilv4 could not be converted to string

Jeff Bickart,

Let's keep working on the other thread you opened.

Jeff Bickart,

Let's keep working on the other thread you opened.