Is there a way to import the current AccountConfig...
# sdf
m
Is there a way to import the current AccountConfiguration using the WebStorm SDF plugin (I only see instructions for the Eclipse plugin)?
c
Hello Miquel, we do not have that functionality in our official WebStorm plug-in
Could you tell me about what do you need? (why do you need to Import Account Configuration)
m
awww. that sucks @Carlos Olivares (NS DevTools PM). But it’s no big deal. I have a repo that sets up core account configuration for each environment and wanted to easily have a features.xml file with the current state. for the time being I manually created the file and added the most pertinent features to it instead.
c
Would you like to have a call with me this week to understand your needs and get a better idea of the use cases you want to cover?, I am not familiarize with that functionality and is the first time I hear someone asking for it.
m
sure. you have any free time Thursday?
a
Just as another data point, I also would like to see it in Webstorm (or even an expanded version of it). When I'm using SDF to transfer a client from sandbox to production for go-live (so we've likely been making a ton of configuration changes in Sandbox that haven't yet been pushed to production), I have to pull up SB & production in two different monitors and manually compare the account configuration settings and change them one by one. Granted, there are still settings like accounting preferences where I have to do that anyway (and it would be cool if those could also be part of SDF!), but it saves me some time/effort. It'd be easy to accidentally mess up if you do it manually so I prefer to automate it as much as possible.
💯 1
n
We would use it in the same scenario as @amy 🙂
m
I agree @amy and @Nikola Gavric. That situation is one of our primary use cases. Luckily we’ve moved to an “extension” format where each feature is self-contained to a project so it actually could be responsible for maintaining an account configuration file on its own. However, I’d prefer a master account configuration where we could document which “extensions” depend on the feature so that we had visibility.