Hi Victor,

Thank you for your suggestions.

I've added both of them to our Backlog.

I'll contact you when this will be available in The Welkin Suite, but I cannot tell exactly when.

Regards,

Kate

Visual Studio currently supports the "Add => Existing Item..." and I was hoping this would be available in TWS.

I've had the same need that the above user brought up.  This would be a nice addition.  Having the ability to save Anonymous Apex and SOQL statements is a great thing and I've shared these files with other developers, but we need this ability to easily add these files to our projects.

Thanks!

Hi John,

Thank you for your comment.

We understand that adding of existing items is the useful option, and our developers are going to implement this in one of the nearest versions of The Welkin Suite.

I'll keep you updated when this will be available inside the IDE.

Regards,

Kate

How is this still not a feature after a year and a half? We have multiple developers working in independent dev environments sharing codet through Git. If a new class is pulled down through Git there's no way to add the file to project. If a file is pulled before adding the file to Welkin, then file has to be deleted, a blank file is added to Welkin, then file is pulled again. 

Hi dhetesi,

I completely understand your critics and appreciate your feedback!

The reason why this functionality is not yet implemented - the regular Salesforce project in TWS is tied up directly with the organization, thus a lot of additional information is stored from a Salesforce organizaiton. For example - hashsum and "remote" modification date for all items. In this way we can ensure that you get the smooth experience with builds/pulls.

At the same time having SalesforceDX there's a great alternative to the old approach - SFDX allows really smooth teamwork, but yes, it requires some initial investment of time to migrate.

We are now looking for different ways how we can make life easier for those who use Git without SFDX - once we'll finalize a good user-friendly approach that won't require huge changes in TWS codebase and logic we'll definately include it into our sprint asap.

Thank you,

Vladimir

Its unrealistic to expect all organizations to adopt DX.  If the company or client does not use DX and hands you a sandbox you cant use DX.   

The only way around this it to open the project in the eclipse app and move you stuff around 

Hi Bruce,

You've pointed to an interesting topic - usage models. To be honest I've rarely seen cases when a client provided a sandbox for a long-running project where I'd need to allocate a team of developers and use Git. In case if it's not a long-running project, or if there's no "team" that works on a project - I'm not sure that I see and understand the exact flow that you apply and how you'd use the discussed feature in your flow. I'd really appreciate if you can shed some light on it so we'll understand the case better and will keep it in mind, when we'll get to the question of additional metadatas/adding existing files/unlinking projects from orgs.

At the same time there's a good option (for long-running projects, of course), to use own DevHub to spin-up scratch orgs for clients projects development and testing. But, of course, it's also not always possible and won't work for every case.

Regarding workarounds - I've posted another workaround, that involves Ant migration tool, here on the forum. Pull from Git -> deploy with ant task -> Open TWS project -> Pull from your organization -> develop -> push to the org -> retrieve with ant task -> commit & push to Git. I know that it's a workaround and not a completely straightforward way, but there's no straightforward way (without a lot of caveats) to work nicely with Git and regular SF projects. It might look as a complex workaround, but in terms of time required to "prepare" and "execute" it - looks not very bad (i.e. 30 minutes to prepare 2 ant tasks for your specific needs with package.xml + 1-3 minutes on every pull/push to execute Ant).

Finally, we already have some interesting ideas how to resolve a bunch of cases at once - as I've mentioned above it's "additional metadatas/adding existing files/unlinking projects from orgs". As such solution will be a significant update to a concept of a project, as it will also require changes to the build & pull processes and as a migration for existing projects will be needed - we're analyzing it carefuly right now and trying to find any gaps in the logic and in the nice flow that we've built for most of the cases. If all will be good on the stage of detailed analysis - we'll do our best to implement this soultion as soon as we can.

Hope this answers.

Thank you,

Vladimir

Hey just wanted to pick up this topic again. 

Since the latest release with "create from sources" it has been very satisfying to combine Git and WelkinSuite. Except this feature here. It is the only thing that prevents this combination to be really good. Because it just feels very clunky right now (even/especially with Ant-Scripts).

So are there any news here?

Hi mkoch86,

Thank you for pointing out these items.

I believe that we can separate this situation into three different cases (please correct me if I'm wrong):

1. Automatically handling new (deleted) Salesforce items, that were added (deleted) to your local folder (e.g. after Git pull)
2. Handling "additional" Salesforce items - SOQL queries and Anonymous apex files
3. Automatically handling all other handy files that you might have in your project folder (ant scripts, documentation, etc.)

I'll start from the end  - support for the third case is not yet planned by our team and we are not sure if we will implement such functionality in the nearest future.

Handling SOQL queries and Anonymous apexl will be added in the next release of the IDE - at least an ability to manually add existing SOQL and Anonymous Apex files to your project. We'll do our best to add there automated handling of cases when SOQL and Anonymous gets added to the project folder, however we might release this part of funcitonality later.

Any "normal" Salesforce metadata that was added or removed to/from your local project folder can be reflected in the project in the semi-automated way using the "Refresh from sources" functionality - you can read a bit more about it in our Release Notes here.

Please let me know if this helps or if I've missed something.

Thank you,

Vladimir