The Welkin Suite Forum

record limit reached. cannot submit more than 200 records into this call



record limit reached. cannot submit more than 200 records into this call

  • Please log in to reply

#1
windows version welkinsuite

cristian.cocioban

    Posted 07 Apr 2017

    When I'm building the project it fails with the following error:

    Error 1 ; nested exception is:
    common.exception.ApiException: record limit reached. cannot submit more than 200 records into this call; nested exception is:
    common.exception.ApiException: record limit reached. cannot submit more than 200 records into this call 1 1





    6 replies to this topic

    #2

    kate.dulko

      Posted 07 Apr 2017

       Hi Cristian,


      Thank you for contacting us with this issue.

      The reason for the error is the Salesforce limitation in 200 files for one updating operation.


      May I please clarify how many files you edited before building your TWS project? 

      Also, please tell me how many files are present in the Pending changes panel. If you didn't use it previously, please open it in the menu View -> Pending changes.


      One more question currently: did you pulled your TWS project from a Git repository?


      All this information will help us to understand the reason for the issue which you are faced with.


      Thank you,

      Kate



      Kate Dulko
      Customer Relations

      The Welkin Suite

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

       

        


      #3

      cristian.cocioban

        Posted 07 Apr 2017

        Hi Kate,


        There are several hundred files in the pending changes. You're right I've pulled the files from git repository.



        #4

        kate.dulko

          Posted 10 Apr 2017

          Hi Cristian,


          Thank you for your response.



          The reason for the issue you are faced with is related to the Windows line-endings inside the files which you pulled from your Git repository. The files inside TWS have UNIX line-endings. This is why all the files with Windows line-endings are present in the Pending changes list and are going to be built.


          Here is the article with the detailed information related to detecting line-endings in your Git repository and how to change these line-endings for your further work.
          I kindly ask you to follow the steps which are described in the 'Refreshing a repository after changing line endings' paragraph.

          After this, please reopen your project in TWS and check the Pending changes list. 


          Please let me know if the issue would be reproduced when you build your changes to Salesforce.


          Thank you,

          Kate



          Kate Dulko
          Customer Relations

          The Welkin Suite

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

           

            


          #5

          cristian.cocioban

            Posted 13 Apr 2017

            I've made the changes with line-endings in git but the issues are still there - api limit exception on build. I've decided to switch to eclipse as the other developers are using eclipse and this also seems to have a negative impact on the project (using eclipse and welkin for the same project).

            Eclipse seems to work fine and doesn't see any changes, while in welkin there are several hundred pending changes.

            I've tried to use Dismiss all but it doesn't  do anything.

            Welkin is also changing the package xml when I'm pulling from salesforce - just rearranging sections in the file.



            #6

            kate.dulko

              Posted 19 Apr 2017

              Hi Cristian,


              Thank you for your response.


              The way how the IDE detects if the file has any changes is that TWS compares hash sums for each file inside a project. Since the line-endings affect these hash sums, the IDE detects the files which were pulled from a Git repository as changed ones and this is why TWS include them to the build.


              We are considering how we can change this mechanism to avoid the similar issues. 

              I will let you know about the results of our investigation.


              Best Regards,

              Kate


              Kate Dulko
              Customer Relations

              The Welkin Suite

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

               

                


              #7

              vlgubanovich

                Posted 19 Apr 2017

                Hi Cristian,

                Can I please ask you for some more details so we can recheck this situation once more and find out a good solution for your and similar cases.

                If I understand correctly you have a repository with metadata that is used by your teammates with Eclipse and you are using TWS with the same repository. Can you please describe in details the process how you've created a TWS project from/for this repository and what where your actions after creating a TWS project? Any additional details and steps like creating/cloning the repository, etc. are very appreciated.


                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