The Welkin Suite Forum

Select object fields to deploy to org



Deploy to organisation a custom object

  • Please log in to reply

#1
windows version welkinsuite

gafsi.manuel@gmail.com

    Posted 25 May 2017

    Hi,

    Me again with another question laughing

    I want to deploy Lead object changes to another org; is it possible to choose which fields I want to deploy ?

    My problem is that this object has managed package fields which are differents between the two orgs. I don't want to include them.

    Thank you.



    3 replies to this topic

    #2

    kate.dulko

      Posted 26 May 2017

      Hi Manu,


      Thank you for your questions :)

      We really appreciate them and they are interesting for us.


      We are going to improve the deployment functionality but these changes will be related to comparing of local and remote organizations.

      Right now we have no plans to implement an ability to deploy separate fields of an object, however, I've added this to our backlog, and we will consider adding this feature.


      May I please ask you to describe your use-case how you handle such deployment with any other tools? This will help us to understand how we can manage this process.


      Thank you for your collaboration.

      Regards,

      Kate


      Kate Dulko
      Customer Relations

      The Welkin Suite

      twitter: @KateDulko
      skype id: d_katerina
      e-mail: kate.dulko@welkinsuite.com

       

        


      #3

      gafsi.manuel@gmail.com

        Posted 27 May 2017


        Of course.

        I have added custom fields to the Lead object on my development sandbox.

        I want to deploy these custom fields to my qualification sandbox.

        I use the welkin suite deployment tool which correctly detects differences on the Lead object and shows me the override option.

        The problem is that my Lead object has managed package fields, and another developer working on the development sandbox has updated the managed package.

        Managed package fields are different between the orgs so the deployment tool tries to apply these changes which result in error: "Cannot modify managed object".

        For the moment I handle this problem using salesforce changeset to apply only selected fields changes.

        Maybe a simple solution could be to skip managed package fields.

        However it could be nice to choose which fields to deploy.

        I hope my explanations are clear.

        Thanks.

        Regards.

        Manu.




        #4

        vlgubanovich

          Posted 01 Jun 2017

          Hi Manu,


          Thank you for sharing your ideas with us and thanks for the detailed description of the situation you are facing.

          Right now we don't have such option in our plans as it is not a very common case and, to be honest, we're not sure yet how we can resolve such kind of situation. Because in general if deploying changes with API's and not with the changesets the whole object is treated as a single item without further breakdown to fields, so we're not able to "simply" strip out some of the fields and deploy. This why we'll need to investigate possible workarounds, so I can't promise that we'll implement such functionality in the nearest future.

          From another point of - we are thinking about providing functionality for working with Changesets directly from the IDE, so in case we'll do this option earlier it might be a good workaround in your case :)


          Thank you,

          Vladimir


          Vladimir Gubanovich
          Head of Product
           
          The Welkin Suite
          skype id: vladimir.gubanovich
          e-mail: vladimir.gubanovich@welkinsuite.com





          Boost Your Productivity. Get Started Today

          Try Free Trial