Greetings

Thank you for your post.

The reason for the failed pull from Salesforce in your case is creating duplicated files in your TWS project.

May I please clarify with you what version of TWS you are using? 

Also, I kindly ask you to send us a bug report directly from the IDE. You can find this option in the menu Help -> Report a Big. This way we will receive your TWS log files. These files can help us to find a reason for this and solve the issue, or at least find a workaround so that you could continue your working process while we are working on the issue.

Thank you,

Kate

Nova R2

And I have sent the log.

Thank you for the bug report with the attached log files.

 

The creation of duplicated files in your case is related to Dashboards, Reports, Email Templates, or other folder metadata. This can be caused by existing of files of the same or different metadata types which have the same name, and they are located in one folder. If you can check this on your Organization, we will appreciate your help greatly.

While our developers are working on this issue, you can disable the 'Subscribe' option in the 'Project metadata components' wizard for Dashboards, Report, and Email template metadata types and please pull after this without updating these files.

 

Please let me know if this helps to solve the failed pull for you.

I will keep you updated know when we will have any results on our investigation or solving this issue.

 

Thank you,

Kate

 

Okay so it appears this was caused by the changes recently that pull declarative data down now.  Since I was still auto pulling down with Ant scripts it was creating duplicates.  I had to scrap and rebuild each solution.

Hi.

Thank you for your response with the update.

Also, may I please ask you to check if there are files with the same name in one folder on your Salesforce Organization? This applies to the same metadata which I've mentioned. Looks like the duplicated files were not created locally, however, they were detected during loading them from the server.

This information will help us to understand how we can handle the case you were faced with.

Thank you,

Kate

Yeah this is definitely broken since the newest patch.  I completely deleted my solutions, rebuilt them all, they worked for a short time.  I removed all ANT scripts, so the metadata is all straight from Welkin.  Now it's broke again with same error.  I have to again wipe everything out and rebuild entire solution every time. Surely that is not the intended operation.  Any ETA on a fix for this?

Hi,

Thank you for your update.

According to the log file which you sent to us, the reason for the issue is the same as previously. This means that your Ant tasks are not related to the issue, and this is caused by files on your Salesforce Organization.

I kindly ask you to open your Org on Salesforce and please check which files have the same names and are located in one folder. You can check this for Dashboards, Reports, and Email Templates. However, I want to draw your attention that the files with a duplicated name belong to the same metadata type.

TWS detects these files on the first stage of pulling when Salesforce returns the list of available files. The pull process itself doesn't start because of this.

Exactly this information will help us to understand how we can solve the issue and, as a result, we will be able to tell you when we could do this.

The issue appears on the Nova R2 version of The Welkin Suite because we implemented the support for dashboards, Reports, and Email Templates in this version.

We will appreciate your help greatly.

Thank you,
Kate

We do not have ANY data with duplicate names or API names in the reports, dashboards or email template folders.  Nothing at all.  I have even completed removed them from the metadata downloaded and the same error persists. 

Even when unsubscribed from those items and the past meta data deleted the error is still there.  Have to rebuild the solution and re-init the git in the folder and reinstall ant assets einto directory EVERY single time I want to use a solution/instance.

Hi Shane,

Thank you for your response.

Currently, I kindly ask you to create a new TWS project without these metadata types and check if the issue would be reproduced on it.

Please let us know about the results. At the same time, we will be working on reproducing the issue.

Thank you,

Kate

I will in a moment, waiting for previous operation to complete.

It seems fine without those data types.  But I won't know until there are some changes and stuff to sync.

Thank you for your quick response.

You can keep us updated if the issue would be reproduced after changes or stuff sync.

We will continue t investigate the reason for the issue.

Regards,

Kate

Hi Shane,

May I please clarify with you one more possible reason for the issue?

Is it possible that files with the same metadata type and with the same name can be related to different namespaces on your Salesforce Organization? 

Thank you,

Kate

Welkins Team...

We are seeing the same issue as reported here, did we have a resolution to this issue. I have created a bug report and sent to Ihor Zhabolenko, waiting for a response. The "An item with the same key has already been added" error pops up and duplicate metadata is downloaded from Salesforce Org to Welkins project. Please advise.

Scenarios:

1. Create New Project In Welkins.
2. Check in the changes to Git.
3. Check out the salesforce project from Git.
4. Open the checked out project in Welkins.
5. Make some page layout changes on salesforce.com org.
6. Pull the page layout changes from salesforce.com using welkins.

@shanejayhayes was this issue resolved, would you be kind enough to share the resolution ?

I am facing the same issue. Any update?

Hello Adriano. 

Thank you for your post.

I kindly ask you to reproduce this one more time and please send us a bug report with attached log files directly from the IDE - you can find this functionality in the menu Help -> Report a Bug, please specify your email and enable the 'Attach Log File' checkbox.

This way we would receive your TWS log files which could help us to find a reason for the error.

Regards,

Ihor

What is the resolution for this issue? As far I know the Salesforce protects duplication wherever it's supposed to be. As TWS an exclusive IDE for Salesforce, I was not expecting that kind of issue.

Is the final resolution recreate the project every time the problem happens?

I am keep getting this error when I am doing Full Pull from Salesforce. I tried to send a Bug report, however that seems to be broken too. It keeps telling me that there was an error sending the bug report. Can you please help on this one? Thanks

Want a discount? Sounds perfect, but too good to be true? Be the first to know the best selections. https://Newchic.vip/Zt6N https://Newchic.vip/Zt76