Skip to main content

This is for a UNIVERSE environment. I've tried setting the account to use in servers.mvbasic.json, as it is using XDEMO by default at the moment which causes the authentication process to fail. I need to manually specify which account is used.

Looking at the logs, it appears this is passed in during the "connect U2 start" stage as accountName, but both this and account seem to have no impact. Is this controllable? 

This is for a UNIVERSE environment. I've tried setting the account to use in servers.mvbasic.json, as it is using XDEMO by default at the moment which causes the authentication process to fail. I need to manually specify which account is used.

Looking at the logs, it appears this is passed in during the "connect U2 start" stage as accountName, but both this and account seem to have no impact. Is this controllable? 

Hi John,

I ran a few tests I see there's no manual override for the default account in the online connection. After consulting with development, I created an enhancement request to have this added to a future release.


This is for a UNIVERSE environment. I've tried setting the account to use in servers.mvbasic.json, as it is using XDEMO by default at the moment which causes the authentication process to fail. I need to manually specify which account is used.

Looking at the logs, it appears this is passed in during the "connect U2 start" stage as accountName, but both this and account seem to have no impact. Is this controllable? 

John, if you don't want to wait for a new release, here is a workaround. You can modify the source code of the extension to override the accountName. It's being set on lines 181 and 183 of online.js. The .vscode directory is usually in your user's home directory. Once you save your change, it should persist until you update the extension to a newer version (whether manually or automatically).

.vscodeextensions ocketsoftware.rocket-mvbasic-2.7.1outonlineonline.js


This is for a UNIVERSE environment. I've tried setting the account to use in servers.mvbasic.json, as it is using XDEMO by default at the moment which causes the authentication process to fail. I need to manually specify which account is used.

Looking at the logs, it appears this is passed in during the "connect U2 start" stage as accountName, but both this and account seem to have no impact. Is this controllable? 

The functionality is available in v2.8.0 due end of next month.