Visual Builder

Get Involved. Join the Conversation.

Topic

    Harsha S Kaundinya
    Table's first-selected-row event is not firing by...
    Topic posted October 9, 2019 by Harsha S KaundinyaGreen Ribbon: 100+ Points, last edited October 9, 2019, tagged Action Flows, Layout, UI 
    43 Views, 7 Comments
    Title:
    Table's first-selected-row event is not firing by default in VBCS Version: 19.3.1.2
    Summary:
    Table's first-selected-row event is not firing by default in VBCS Version: 19.3.1.2. This was working in earlier version 19.1.3
    Content:

    Hi,

    I was using VBCS with version 19.1.3 and now it has been upgraded to version 19.3.1.2. Some of the features like first-selected-row event is not firing for the first time. 

    There is a master-detail table in a page. When user provides search parameters and clicks on search, the page displays data in the master table. A first-selected-row event is added on the table to call the service and populate the data in the detail table. But this event now is not firing when user clicks search for the first time. Subsequent search or if another row is clicked, this event fires. The selection-required property on the table is set to true. I was not facing this issue with the earlier version 19.1.3.

    Is there any other property to set on the table in the 19.3.1.2 version for this to work?

    Version:
    19.3.1.2

    Comment

     

    • Sunil Polineni

      Hi Harsha,

      There is know issue can you please open SR let me know the SR# so that we can get fix for this issue.

      Regards,

      Sunil

    • Preetesh Dongre

      Hi Harsha,

      Did you get any fix from Oracle on this? Even I have an SR open for this issue.

      This is one of the many issues we faced after VBCS upgrade.

      Regards,

      Preetesh

      • Harsha S Kaundinya

        Hi Preetesh,

        We havent received a fix yet. No update on the SR too. Eagerly waiting for them.

        Can you also please let know what are the other issues you see after the upgrade? This will be helpful for us.

        Thanks,

        Harsha

        • Preetesh Dongre

          Hi Harsha,

          You would need to add below code wherever you are having a variable assignment(with reset) tagged to your table, assuming you are using ADP variable in table mapping.

          "mapping": {
          "$target.data": {
          "source": "$source.data",
          "reset": "empty"
          }
          }

          So, typically your variable assignment would look like

          "PopulatePODetailADP": {
               "module": "vb/action/builtin/assignVariablesAction",
               "parameters": {
                "$page.variables.poDetailADPVar": {
                 "source": {
                  "data": "{{ $chain.results.GetPODetails.body.items }}"
                 },
                 "reset": "toDefault",
                        "auto": "always",
                        "mapping": {
                        "$target.data": {
                        "source": "$source.data",
                        "reset": "empty"
                        }
                        }
                }
               }

          Hope this helps in resolving your issue.

          Issues that we faced.

          1) Table selection even for 1st row stopped firing.

          2) Variable assignment(having hierarchical structure) were failing, SaaS RESTs response payload structure was changed that we were using in assignment.

          3) Popup started behaving weirdly.

          4) Issues with Role creation/assignment. and few others.

          Regards,

          Preetesh

          • Harsha S Kaundinya

            Hi Preetesh,

            This did not work for me. Did this solve your table 1st row selection issue? 

            Our code looks like below on assignment.

            "assignOrderSearchTypeADP": {
                      "module": "vb/action/builtin/assignVariablesAction",
                      "label": "Assign to Order Search Type ADP",
                      "parameters": {
                        "$page.variables.getOrderSearchTypeADP": {
                          "source": {
                            "data": "{{ $chain.results.callManagerSearchEndPoint.body.items }}"
                          },
                          "reset": "toDefault",
                          "auto": "always",
                          "mapping": {
                          "$target.data": {
                          "source": "$source.data",
                          "reset": "empty"
                          }
                          }
                        }
                      },
                      "outcomes": {
                        "success": "fireSuccessNotification"
                      },
                      "description": "Assigning the search results to getOrderSearchTypeADP."
                    },
            

                            ...........

            Regards,

            Harsha

            • Preetesh Dongre

              Hi Harsha,

              Code looks correct to me, and yes it did work in my case. Just make sure you don't have assignment at any other place where similar change is required, also check if you are resetting this variable by 'Reset' action somewhere in Action chain.

              Just for sake of it may be create a sample page with a variable assignment and check if adding removing the extra code makes any difference.

              If nothing works you might have to wait for Oracle to come back.

              Regards,

              Preetesh