Solution explorer should have an option to manually refresh the directory structure to check if there are any new changes made in the project directory.
Solution explorer should have an option to refresh directory
#1
Posted 01 Dec 2017 and edited 10 May 2018
#2
Posted 01 Dec 2017
Hi Swagat,
Thank you for your request.
The Welkin Suite requires additional information from the organization for files in the project, for example - ID, hashsum, modification date, etc. Without this data some of the essential features of the IDE won't be available, this is why the following workflow is not supported by the IDE in the regular projects.
However, if you are working with SalesforceDX projects - this functionality is already present there.
In the meantime, we will try to find a way to allow importing files from your file system into a project directly.
Thank you,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com
#3
Posted 04 Dec 2017
Hi Kate,
We need a way to do this since there are chances that a project would be connected to a git repository and the files will change external to TWS whenever changes are pulled from a remote repo to a local repo. This is a pretty generic user case that most of the developers might face.
Could you please let me know if there is a workaround for this since this is really hampering my work as of now.
Thanks.
#4
Posted 11 Dec 2017 and edited 11 Dec 2017
Hi Swagat,
Thank you for your response and please sorry for a delay in my answer.
As I've mentioned in the topic on our forum, The Welkin Suite's project file stores a lot of additional information and some of this information is related to a content of files in the project.
This is why the way how The Welkin Suite will allow you to work with Git and how this will work in the best case (of course if not taking into account SalesforceDX) – when you will have the whole TWS project in the Git repository, including the *.sfproj file itself.
In your case, I assume that the project file is not stored as a part of the Git repository or not all team members are using TWS to work with sources in the repository - this causes all of the issues that you've mentioned in your bug reports.
I can suggest you a couple ways how to resolve this situation in the case if it is not possible to include the *.sfproj file to your Git repository:
- this one
- or this
From another point, the suggested best practice solution from Salesforce for your workflow would be to use the SalesforceDX as its exact goal is to simplify the teamwork and collaboration using Git or any other version control system. The Welkin Suite's project type for SalesforceDX strictly follows that pattern and allows you to modify the sources in any way outside of the ide.
Hope this helps.
Best regards,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com
#5
Posted 13 Dec 2017
Hi Kate,
Thank you for your reply. Here is the problem that I am facing and why the solutions you suggested won't work.
Consider this scenario. I have a team of 2 developers who are working on a packaging org. This org has many components that are included in the final package, while there are many that are not a part of the package and were only created for few proof of concepts. This org is linked to a git repository which only contains the components that are part of the final package (and does not contain any files related to TWS since not all developers use TWS).
Now let's say developer 1 added few new files in the package and modified others. Now there is no way in TWS to retrieve only those files that are a part of a particular namespace/package. This will force the other developer to retrieve everything from the org and clutter his local working directory with components that are not even a part of the package. This is not feasible since the git repository should only contain the components that are a part of the namespace/package.
Also, consider this, developer 1 pushed something to the git repository. Now since this repositry only contains the components that are a part of the package, developer 2 pulls them outside of TWS to get the latest changes from git. This messes up TWS configuration and TWS starts to behave abnormally.
So the solution that I am looking for is either of the one mentioned below:
1) Allow TWS to pull only those components that are a part of a particular namespace/package for a packaging org OR
2) Allow TWS to refresh the files even if they are changed outside of TWS by some external application.
I hope I have made the scenario clear enough for you to consider this feature request on priority since my team is practically stuck here and this is really frustrating.
Thanks.
#6
Posted 15 Dec 2017
Hi Kate,
Any updates on this? Not being able to pull files per namespace/package for a packaging org is frustrating for my team here.
Any progress on this would be highly appreciated.
Thanks.
#7
Posted 16 Dec 2017
Hi Swagat,
Thank you for the detailed description of the workflow and scenario.
It's not 100% clear for us, how you are/were handling this scenario with the previous/other development tools, so we'll appreciate if you can share this information, please.
At the same time, it seems that the option to stick to the namespace during pull/creation might looks as a good solution for it, I agree.
We'll work on prioritizing this improvement higher, however as it requires a significant amount of work we might not guarantee that it will be implemented in the next 1-2months.
Thank you,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com
#8
Posted 17 Dec 2017
Hi Kate,
I appreciate your reply on this.
Other IDEs that we used were text file based where any changes outside the IDE were also detected in the IDE when we open that particular file (since it always showed us the local copy of the file). They did not have any concept of local history which made it possible for them to refresh the file in the IDE even if anything else has changed the content outside the IDE. Just like a notepad++ file. So in those other IDEs what we used to do is, pull the files for a particular namespace using CumulusCI/Ant and then open the same file in IDE.
On a side note, TWS does have Ant support and Ant does support pulling files based on a namespace/package name. Is there any workaround that we can use with TWS and Ant to achieve this for the time being till this feature is implemented?
Thanks.
#9
Posted 17 Dec 2017
Hi Swagat,
Thank you for the additional details.
As Kate mentioned previously we really think that sticking to the namespace(s) while working with a project will be a good solution for you, so we will consider implementing it sooner than planned before.
Regarding your question about the Ant support - we support Ant, but we do not use it as the "backend" for our functionality, so this support won't give a way to work just with certain namespaces. I'll try to think over a workaround how we can deal with you case while we'll work on implementing the mentioned functionality.
Thank you for you assistance!
Best Regards,
Vladimir
Vladimir Gubanovich
Head of Product
The Welkin Suite
skype id: vladimir.gubanovich
e-mail: vladimir.gubanovich@welkinsuite.com
#10
Posted 18 Jan 2018
Hello Vladimir,
Any updates on this? This is really getting to be a hurdle for me and I have switched to other IDE for now. Please let me know when can I expect this to be available?
Thanks.
#11
Posted 22 Jan 2018
Hi Swagat,
As discussed before - we believe that proper filtering and sticking to a namespace when creating a project (or doing any other operations with the project) might be a good solution for your case. We have included this into our plan, and we are doing our best to implement this feature within a month +-, together with some other small improvements related to the namespaces handling.
Hope this helps.
Thank you,
Vladimir
Vladimir Gubanovich
Head of Product
The Welkin Suite
skype id: vladimir.gubanovich
e-mail: vladimir.gubanovich@welkinsuite.com
#12
Posted 12 Feb 2018
That helps.
Hoping to see this in the upcoming release.
#13
Posted 15 Feb 2018
Hi Swagat,
Thank you for your post.
This is planned for one of the next versions of the IDE.
I will keep you updated when this functionality will be available in The Welkin Suite.
Best Regards,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com
#14
Posted 23 Feb 2018
Hi Kate / Vladimir,
Any updates on this fix? This is really getting to be in the way of efficiently delivering things for a packaging org with Git.
Any early fix on this would be highy appreciated.
Thanks.
#15
Posted 23 Feb 2018
Hi Swagat,
As Kate early mentioned this update is planned in one of the next releases.
As we've previously discussed with you we do not treat this as a bug, but as a significant change in the usage model. And due to the different (to what's expected by the IDE) usage model different incorrect situations might appear. This is why this topic is not an easy and quick fix - this is a significant change to the whole IDE, that will affect a lot of areas and components. It is impossible to complete it in a quick way and it will require a significant efforts investment from the whole team. At the same time we have a roadmap and we need to find a way to reserve at least 2-3 weeks of the team's work just for this change, while not working on anything else.
I will get back to you once I'll have some interesting updates and I'd be happy to chat with you about the approach that we are going to implement, however we want to prepare everything carefully and in a good manner, so it takes time.
Thank you for your understanding.
Best Regards,
Vladimir
Vladimir Gubanovich
Head of Product
The Welkin Suite
skype id: vladimir.gubanovich
e-mail: vladimir.gubanovich@welkinsuite.com
#16
Posted 19 Mar 2018
Hi Vladimir,
Hope you are doing good.
Not to push you or anything but but is there any updates on this feature request? I work with Managed packages on a daily basis and not having this feature in TWS forces me to go back to MavensMate even though I do not want to.
Hoping for this feature in one of the next releases (before my subscription expires.. at which point I'll have to decide whether to renew or not)
Thanks.
#17
Posted 10 May 2018
Hi Vladimir,
Any updates on this? This is becoming a blocker for us now since we do not have a way to pull only the files that are a part of the package. We have to manually choose all the files while creating a project and that is very time consuming if you have many files in the project.
This is a very important feature for ISVs and should be implemented asap. I believe you even wanted to talk to me about this feature but I haven't heard from anyone yet.
Thanks.
#18
Posted 10 May 2018
Hi Swagat,
Thank you for your post!
We understand how the absence of this functionality can make a working process more complicated, and how easier would be managing files in a project with an ability to add existing ones.
We have news for you!
Our developers have started work on changing the existing approach and some internal processes inside the IDE to implement this functionality.
This work can take some time, however, we believe that in a month (+/-) we will provide you with TWS version where you would be able to add existing files, and, also, you would have an ability to work with all the metadata types in your TWS project.
So the first summer TWS release will bring to you a lot of useful features :)
Best Regards,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com