Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

  • #16
    Hi Isomorphic,

    thanks. Yes, not important anymore as a serverside validator can handle this.
    Thanks for having a look at the generated XML. This will definitely move the limit of rows the BatchUploader can handle.

    @All: I opened a thread here on best practice for background processing if the amount of data becomes to much to handle by BatchUpload (or as I assume in general for user triggered background processing) here.

    Best regards
    Blama

    Comment


    • #17
      Hi Isomorphic,

      did you have a look at the 4 four BatchUploader issues linked in #14? They all sat there about a week and you did not reply if you could reproduce, yet.

      Thank you & Best regards
      Blama

      Comment


      • #18
        All of those are assigned, but none have high enough priority to have risen to the top of the queue so far.

        Comment


        • #19
          Are all of these issues being reported against the release, SGWT/SC 12.0? No branch was mentioned in any of the posts above.

          Comment


          • #20
            Hi Isomorphic,

            yes, all with 12.0p.

            Best regards
            Blama

            Comment


            • #21
              The duplication of records into "oldValues" has been eliminated for BatchUploader commit in SGWT 12.0p and newer releases. There's currently an issue blocking our nightly releases, but the next nightly builds of the mentioned branches should have the fix.

              Comment


              • #22
                Hi Isomorphic,

                thanks a lot. We'll try soon. As we do not want to roll out new nightlies without thorough manual testing, I'd like to wait for the others from #14 as well.
                Did you already look into them? All of them sat now for almost a month.

                Best regards
                Blama

                Comment


                • #23
                  As we previously covered: these are assigned, but they do not have much priority as you are the only affected user, the only user who is likely to be affected possibly ever, and they don't block functionality. So while they are assigned, please expect an extended wait.

                  At the moment we are dealing with regressions in the latest Firefox related to alignment and regressions in recent Chrome related to being able to detect keypress events on Mac. For obvious reasons, these kinds of issues take precedence, and there is no way for us to avoid them, as this is the browser vendors introducing bugs, as they do regularly.

                  Comment

                  Working...
                  X