The Welkin Suite Forum

Cant see custom types from managed packages



Cant see custom types from managed packages

  • Please log in to reply

#1

maks

    Posted 05 Aug 2015

    Hi, 


    I get the error: Error 5 Package Visibility: Type is not visible: blah when I am trying to reference a global type from a managed package.


    I think this is related to the tooling metadata api, is there a way to disable that so that managed package types are visible.


    There is a setting in mavensmate that disables this and things will save correctly. I am able to access and save the type from the sfdc ui and mavensmate with the tooling api turned off. Not being able to use custom types from managed packages makes this kind of un-usable.



    6 replies to this topic

    #2

    vlgubanovich

      Posted 07 Aug 2015

      Hi maks,


      Thanks for letting us know. We haven't faced this issue before. We will work on investigating and fixing it withing next week or so.


      Thanks,

      Vladimir


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


      #3

      maks

        Posted 02 Sep 2015

        Hey any word on this? I would really love to use the tool before dreamforce. 



        #4

        vlgubanovich

          Posted 03 Sep 2015

          Hi Maks,


          We're in the process of finding a way to resolve this issue. We can't turn off tooling API as this is not the correct solution - Metadata API works slower and gives less opportunities than Tooling API.


          Sorry for not updating you for a while.


          Thanks,

          Vladimir


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


          #5

          vlgubanovich

            Posted 09 Sep 2015

            Hi maks,


            Can I please ask you to share with us what managed package are you using to get this issue?


            Thanks,

            Vladimir


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


            #6

            ShaunLuttin

              Posted 20 May 2016

              Same problem.



              #7

              vlgubanovich

                Posted 20 May 2016

                Hi ShaunLuttin,


                Can you please check if the metadata file (-meta.xml) for the file which is not building contains information about managed package dependency (as well as the correct version)?

                If this information is not present - please add this manually in the metadata file or from the Salesforce UI, pull changes and try again.


                Please let me know if this helps.


                Thanks,

                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