Try taking a look at the System Management Portal under System Administration > Security > Applications > Web Applications. Confirm that /api/atelier is enabled. You may also want to look at your web server and CSP/Web Gateway settings. A CSP/Web Gateway log and ISCLOG should provide more information here as well.

The VS Code docs on IntelliSense and Code Snippets should help provide more information:

You may want to take a look at the IntelliSense features you have enabled in VS Code now. You can do that by searching your User and Workspace preferences for 'IntelliSense'. You can also hit Ctrl+Space while coding to get autocomplete suggestions.

Do you have a more specific example of the autocomplete feature you are looking for? When I am working in a routine that has been compiled with a HelloWorld entry point, I can see the following as I'm writing ObjectScript code:


After I set a variable I can see autocomplete options including that variable:


Hi Scott, You will only see the ObjectScript icon in the Activity Bar after you've opened a folder in VS Code (File > Open). See a previous post about this here.

When I do the Atelier XML import and run into files that are different from the server version, the resulting prompt has a checkbox for "Apply to Remaining":


If I check that then I can click "Finish" and my selection for Save Local Copy/Skip/Save Server Copy is applied to all files where there is a conflict.

Atelier still only works with Eclipse Photon. Eclipse changed some underlying mechanisms with newer versions of their product, and InterSystems has not had the dev cycles to find the root cause + make the necessary corrections to the Atelier plugin.

Atelier is technically only supported with Java 8. I have heard about other versions of Java working just fine, but these have not been tested by InterSystems' QD team. If you have other Java-based apps that you would like to be using a later version of Java with, you can have multiple Java installs and configure Eclipse to look at Java 8. You should be able to Google to find out more to about how to configure that for your OS.

The answer to this question really depends on the context and where in the process you are at. If you would like to have a more in-depth discussion with someone about that, I would suggest that you reach out to your InterSystems account team or Support.

Typically when you are sending SOAP requests from an InterSystems product, you would get a WSDL from the SOAP service endpoint and use our SOAP Wizard to generate client classes. Then those client classes can be used at the object level to send requests. You can find documentation on the SOAP wizard here. To use the generated SOAP client classes, see our documentation here. Then this section in the documentation discusses how to add security elements to your SOAP request.

If you would just like a more object-friendly way to build up XML you can consider using the %XML.Writer API's, documented here and here.

I would suggest enabling the Caché SOAP log to capture inbound, outbound, and security information - "ios" - then reproducing the error. (Be sure to disable the SOAP log by killing the ^ISCSOAP global when you are done.) This will print the error message in a more readable format, show the outbound message sent by your Caché SOAP client, etc.

If you are having trouble understanding the data in the SOAP log I would suggest opening a new case with the InterSystems Support staff, either by calling into +1 617-621-0700 or emailing

This is a setting of any EnsLib.File.PassthroughService, found in the Additional Settings section:

The different options in the drop-down are described in the documentation that Marc linked to (here).

The two most common problems when we see behavior like this are:

  1. An unsupported version of Eclipse is installed - Eclipse Photon is the only supported version for Atelier. You can check your Eclipse version by going to the "About Eclipse" menu.
  2. An unsupported version of Java is installed - Java 8 is the only supported version for Atelier. You can check your Java version by entering "java -version" in an OS command prompt.

If you are still having trouble feel free to comment here in the Developer Community, or open a new WRC case (by emailing to investigate with InterSystems Support.

Dave is working with InterSystems Support on this one. An update on the investigation:

This error is thrown when trying to import a file that is not UTF-8 encoded. Starting with Atelier 1.3.144 (the current beta version), the error message in this case is clearer:

com.intersystems.atelier.utils.CheckedExceptionWrapper: Failed to decode as UTF-8

Atelier requires that all files not stored as globals on the server be in UTF-8 format. Examples include HTML, CSS, TXT, and JS. So the solutions are either to convert files to UTF-8 encoding so that they can be synchronized using Atelier, or to modify the files directly on the file system.