Announcement

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

    ListGrid mass Update response message format

    I am configured List Grid to perform mass Update.

    when Update Button pressed, using following command
    to perfirm saveAkkEduts

    gridItem.saveAllEdits(null,callBackFunctionName)

    If only one line is upated, it works perfectly.

    But two or more lines are updated, callback function is not
    fired.

    I suspect that when two or more line are required update, response message contents should be changed.

    I can't find out document for response of these cases.

    request payload seems different when two or more lines like below.

    { transaction: { transactionNum: 8, operations: [{
    "dataSource":"isc_RestDataSource_2" ......

    Please help me.

    mikeshimura

    #2
    Ditto - I have the same issue. Only one record is sent and saved. My server returns a response in the same format as if updated from a form, but the callback doesn't fire, no error event is fired, and no more changed listGrid rows are sent.
    Last edited by gwque; 17 Nov 2012, 14:38.

    Comment


      #3
      The format for saving multiple records is extensively documented under RestDataSource. It is not specific to the ListGrid, it is used for all multiple record updates.

      If you're using a server-based DataSource with the Server Framework provided in Pro+ Edition, you don't need to know the format, everything is automatic. This is described in detail in the QuickStart Guide, Server Framework chapter.

      For any other type of DataSource you would need use the clientCustom data protocol to collect multiple DSRequests into one network request.

      Comment


        #4
        Thank you very much for your quick reply

        I could not locate subject information by myself.
        It explain detailed information what I want.

        Best regards

        Comment


          #5
          Solved

          I'm not using any server components - it is a custom .NET back end. My responses were formatted per the docs and still didn't work.

          I finally saw in the forums you folks mentioned an undocumented setting for the RestDataSource, "disableQueuing". I added the following and it now works:

          disableQueuing:true;

          Again, not in the docs so what's the deal with this - why is this required to make a listGrid send all row changes in LGPL and why is it not in the online docs (at least not using the search nor in the RestDataSource API)?

          It's working now, but like every other issue I've had to figure out with this platform I've burned an entire day to discover the simplest of workarounds.
          Last edited by gwque; 17 Nov 2012, 21:20.

          Comment


            #6
            The disableQueuing setting is documented.

            The same document covers the format for responses where multiple records are saved. Other users are not having trouble with this and automated tests are passing.

            If you think you're providing a correct response and the framework has a bug, please provide a test case.

            Comment


              #7
              Documentation Location

              I can't find the documentation on it. I use the online docs since I assume they are the latest:

              http://www.smartclient.com/docs/8.2/...RestDataSource

              Attached is a screen shot of API docs - the setting is not in there...

              If you could post a URL or the menu selections to find it, that would be appreciated.

              Thanks.
              Attached Files
              Last edited by gwque; 19 Nov 2012, 13:37.

              Comment


                #8
                You need the 8.3 docs. They are in your SDK.

                Comment


                  #9
                  Not using 8.3 - not released production yet, correct?

                  Using 8.2, and it is not in the docs.
                  Last edited by gwque; 19 Nov 2012, 13:42.

                  Comment


                    #10
                    8.3 is in final RC and you may as well be using it now.

                    The format for multiple responses has been exhaustively documented since 8.2. disableQueuing is also doc'd in 8.2, but the docs were added in a patch shortly after release, and you seem to be using older docs.

                    Bigger picture, you should not be using disableQueuing unless you need temporary backwards compatibility for a server-side RestDataSource implementation that doesn't support queuing. Using queuing is always better.

                    You previously seemed to be having trouble providing a response for a multi-update request. Rather than set disableQueuing, you should try to fix the problem in your response (or create a bug report if you think its a framework issue).

                    Comment

                    Working...
                    X