The Welkin Suite Forum

Change api version



Change api version

  • Please log in to reply

#1
windows version welkinsuite

sturev

    Posted 21 Oct 2017 and edited 20 Feb 2018

    How can I change the api version for a project? On the project properties, it shows me the ApexVersion as being 39, but in this specific project, I need to downgrade it to 36. In others, I need it to be the latest which is 41.



    13 replies to this topic

    #2

    vlgubanovich

      Posted 24 Oct 2017

      Hi Evan,


      Thank you for this question. May I please clarify if you really need the project version to be changed or you only need it to be different for some of the files?

      TWS supports changing ApiVersion for Apex files in the corresponding "-meta.xml" files.

      In case if you'd need to change the api version for the whole project we need to understand what are the use cases so we can implement this functionality or provide you with different ways of achieving the result.


      Best regards,

      Vladimir


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


      #3

      sturev

        Posted 24 Oct 2017

        In my use case, it's the whole project. We have a ci/cd tool that was stuck on 36, and with the metadata structure changes w/picklists in 37, it couldn't process our commits. In another use case, we need to use 41 to get access to some of the new Lightining features. I tried changing it in the project.xml but it keeps getting reset to 39. I would think that you'd default to the api version of the org and not hard code it?

        Thanks



        #4

        vlgubanovich

          Posted 25 Oct 2017

          Hi Evan,

          Unfortunately in this case there is no option for now to do such kind of configuration for API version for the project. I am also not sure that we will implement such functionality in the future, as such significant changes in the API (picklists changes) are significantly affecting some of the IDE's functionality (for example - fields editor in the sObjects inspector). This means that in order to support any (or both) versions it will require a significant amount of additional efforts from our team.

          As a side note - it might be interesting for you to try using SalesforceDX CLI  as a tool that's used by your CI. It'll be supported by Salesforce itself and you can use it for deployments to regular orgs as well.


          Hope this helps,

          Vladimir


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


          #5

          sturev

            Posted 25 Oct 2017

            Vladimir,

            That makes sense with the downgrade of the version and what that would mean for the IDE.

            What are the prospects of use being able to use the latest version that's in production? (41)

            Good thought on the DX CLI... I'll test that next week.

            Thanks,

            Evan



            Post deleted by author.

            #7

            vlgubanovich

              Posted 02 Jan 2018

              Hi sturev,


              It seems that somehow I've missed your post - please sorry for that.

              While being a while, since you've asked, anyway - we'll switch to the v41 on the next version for Windows.


              Thank you,

              Vladimir


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


              #8

              Artem.Sedov

                Posted 27 Jan 2018

                Is there a way to switch *.anonymous and *.soql files to execute with the most recent API version? As it seems like it takes the version from the project settings and doesn't see some of the new standard fields (ex. StockKeepingUnit on the Product2 object).


                Thanks :)

                -Artem



                #9

                kate.dulko

                  Posted 30 Jan 2018

                  Hi Artem,


                  Thank you for your questions.

                  We are going to release updated versions of The Welkin Suite for Windows and for Mac the nearest days, and both of them will contain support of the latest API v.41 provided by Salesforce. So you will have an ability to work using all the benefits of the most recent API version like new fields and etc.

                  Right now, there is no ability to change this version manually in the IDE.


                  Regards,

                  Kate


                  Kate Dulko
                  Customer Relations

                  The Welkin Suite

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

                   

                    


                  #10

                  stevecook324

                    Posted 01 Feb 2018

                    I'm glad to see the 41.0 update (for Apex at least)! On our project we try to keep any new classes, lighting component bundles, etc... on the latest released API versions when we know it will get released on an org that has that version. The "Project Properties" dialog allows you to change the API Version for the project (or seems to). I was hoping that was maybe an attribute that was setting what to use for "New" items. I'm seeing now that it says "APEX Version" not "API Version" so I'm gathering from this discussion that I need to tweak my metadata still for non APEX items like Lightning Component Bundles? 


                    Thanks!




                    #11

                    vlgubanovich

                      Posted 01 Feb 2018

                      Hi Steve,


                      Thanks for your question.

                      Being honest with you - we need to remove the API/Apex version optionfrom the project properties as it changes nothing. The IDE switches to the new API version all at once, so everything done in the IDE will use the new API version - all new items, SOQL queries, Anonymous apex, etc.

                      And I also doubt that we'll add an option to "downgrade" the API version for a certain project - this is related to the significant overhead from the development point of view. In such case we'd need to support multiple API versions for the IDE at the same time. Taking into account that sometines things are changing very significantly - this will add a lot of monkey-work for us and it will slowdown the development process.


                      P.S.: We might keep this topic open as we'd need to update to the v.42 in the next TWS release :)


                      Thanks,

                      Vladimir


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

                      • 1

                      #12

                      stevecook324

                        Posted 01 Feb 2018

                        Thanks for the quick response Vladimir!!



                        #13

                        marc.behr

                          Posted 19 Feb 2018

                          Vlad,


                          Is there a way to change the version of a Lightning component bundle from TWS (Bloom (ie Mac) release)? I know I can change the meta file for Apex classes, but I am not seeing a way to update the version for Lightning component bundles.


                          Marc



                          #14

                          kate.dulko

                            Posted 20 Feb 2018

                            Hi Marc,


                            Thank you for your post.


                            Right now, there is no ability to configure manually API version for Lightning bundles directly in the IDE

                            If you looking for a way to change the API version to the 42nd one, we are going to move the IDE to this Salesforce API version within the nearest month.


                            Best Regards,

                            Kate




                            Kate Dulko
                            Customer Relations

                            The Welkin Suite

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

                             

                              





                            Boost Your Productivity. Get Started Today

                            Try Free Trial