Hi Lisa,

Thank you for bringing this issue to our attention.

Since all your custom objects have references to a Global Value Set, the Global Value Sets files are required for the deployment to another organization as dependent files together with your objects.

Currently, the IDE doesn't support Global Value Set metadata type and this is why the error appears. 

We will work on adding the support for this metadata type in future versions of The Welkin Suite IDE, and I will let you know when we will implement this.

Right now, there is no ability to deploy objects which have references to a global value set directly from TWS IDE.

Regards,

Kate

Thanks, Kate.  I created a change set in SF with just the Global Value Sets and uploaded that to my testing sandbox and then was able to deploy using TWS.

Lisa

Hi Lisa,

Thank you for your response and for sharing with us the workaround which you have used.

I will let you know when the support for the Global Value Set metadata will be implemented.

Also, if you have any other questions, please contact us. We will be happy to assist.

Regards,

Kate

Any update on this? Is it on the roadmap? This will be important for us.

Hi Bob,

Thank you for your post.

We are going to work on implementing the support for additional metadata types in several months, and the Global Value Sets metadata type is included in these plans.

I will keep you updated when you will be able to include them to your TWS project.

Regards,

Kate

FYI I am running into this issue on a project also. Deploying Global Value Sets/Picklists with TWS would have prevented us from needing to use Change Sets in Salesforce.

Thanks

Hi Allen,

Thank you for your post.

Right now we are working on ETA for the additional metadata types support and Global Value Sets are also present in this list.

May I please clarify with you some details so that we could understand what is the most usable cases? 

in the case of Global Value Sets/Picklists, do you need them to make an ability to deploy your objects and related files to an organization, use them for analyze and search options, or you work on their xml files, edit them, and need to keep these files up to date during all you working process?

We would greatly appreciate this information from you.

Thank you,

Kate

Hi,

I'm running into the same issue here.

To make the global value sets editable as an XML file would be a nice addon, but for us the first important step would be to have the ability to simply move global value sets from one ORG to another so that we could also move object definitions without creating the value sets manually in the target ORG. (This applies only to ORGs that are not connected ofc, because otherwise we could use the standard change sets)

Best,

Steve

Hi Steve,

Thank you greatly for your response.

I believe we will implement this feature request within the nearest 1-2 months - we already have some ideas how to work on this and we should select the most proper way to do this.

Regards,

Kate 

Has this been implemented in release 1.18.5.4? I can't find the Global Value Sets in the project metadata.

Greetings,

Thank you for your question!

Our developers are working on adding the support of Global Value Sets right now, and you will be able to add them to your TWS project already in the next version of the IDE.

If you have any other questions, please let us know - we'll be happy to answer them.

Regards,

Kate

Looking forward to this, an editor that helps one easily create / manipulate global value sets (even better one that allows import from CSV) would rock.

Hi Martin,

Thank you for your post.

This is present in our plans for one of the nearest versions of the IDE.

I will let you know when we will add the editor for Global Value Sets.

Regards,

Ihor