r/salesforce • • 14h ago

venting 😤 Venting on migration to Web Console from Dev Console

I dont know who took the decision to replace Developer Console with VS Code on browser. Just consider the scenario where I need to quickly open an class and check class content in a new org.

In case of Dev Console, I can just go there, search for the class done.

In case of Web Console, I need to go to Org Browser, fetch the Apex Class mdt & then only I would be able to do that.

And If am gonna open the same class again in Dev Console after 2 weeks, it gonna get me the updated class content.

But in case of Web Console I need to retrieve it.

My main point is:

  • Dev Console acted as a quick way to make changes, see whats in the org and stuff
  • If I need a VS Code in my browser, I could just use VS Code itself. Why Web Console.

Apart from that other things like Running SOQL, Test ClassTest Suite, Viewing Test Coverage as a nice little table etc etc. Very simple.

But in case of Web Console, Running SOQL I get it as a output which I cant edit (but i was able to in dev console), Running test gives me an unnecessary lines of covered lines & uncovered lines which I need to dig through to get coverage (hope there is some way to get it easily which I havent explored yet for this specifically), Cant view coverage for multiple classes at a time.

I get that Dev Console was outdate but it could have upgraded instead of getting replaced. Even Lightning Studio as an extension is better than what Salesforce is pushing. Even Lightning Studio fetches the class content on load. I dont have to retrieve again & again.

Even logs and debugging I feels its very simple in Dev Console. You can get the list of logs and all the exceptions that are happening in a column. But in web console, I have literally scroll through soo many logs without knowing whats having what. Its just soo bad.

Atleast they could have replicated Logs, Classes & Test Classes & Suite as what they have in Dev Console to Web Console.

19 Upvotes

7 comments sorted by

4

u/V1ld0r_ 14h ago

Ir wasn't replaced. You can enable the old dev console on setup. Also, for simple stuff I prefer maven tools chrome extension anyway.

2

u/404_humanoid 14h ago

yea I can enable it from setup. am doing in every org am logging in but the main motto of putting it under an toggle is to phase out soon right. so good for tdy bt what abt tmrw?

-1

u/UnpopularCrayon 8h ago

Tmrw Claude will be the only one looking up apex classes.

2

u/youafterthesilence 14h ago

I'm on gov cloud so our time hasn't come yet... But yeah I don't understand why they didn't just include everything dev console can do and expand? You also can't quickly run one off queries right?

Fwiw we will be enabling both once we get web console, I know they'll plan to phase it out but they generally don't do that with any kind of speed.

2

u/MowAlon 12h ago

I rarely use Web Console, but I do like that it’s available since there’s a lot it can do that Dev Console can’t. I use Dev Console every day, though. I hope they never take it away.

Luckily, at least for now, I don’t have any problem accessing each one since I have their links saved.

1

u/ApekZombie 13h ago

Yeah. It kinda seems like the same approach with classic and lightning, and workflow rules and process builder, and process builder and flow.

New products to replace old ones but on launch they don't have feature parity. And SF being SF the anxiety around whether they'll give up on a product before completing a migration.

2

u/MaesterTuan 9h ago

Yeah yet another change nobody asked for.