Issue with Editable Grid

RE: Issue with Editable Grid

nageswararaoa3344 — Tue, 25 Feb 2020 07:02:42 GMT

Hi Subhar,

I too faced the same issue.

In the above code, instead of a!refreshvariable use load and with.

It seems there is an issue with a!refreshvariable function.

RE: Issue with Editable Grid

Peter Lewis — Mon, 03 Feb 2020 12:35:54 GMT

Ah that might be the issue then - I'd suggest opening a ticket with Appian support

RE: Issue with Editable Grid

subhar — Mon, 03 Feb 2020 02:34:47 GMT

Hi Peter,

Thanks for looking into it.

Can you check the hotfix version of 19.3 environment where you tested.Because it seems some bug fix applied on the HotFix Package D.I have tested in the version 19.3 without any hotfix.

AN-144662 - Medium
Fixed an issue where a row on a grid layout incorrectly appeared selected.

If this is the issue,Is there any fix can be done on 19.2 version other than upgrading?Can anyone please suggest on it?

Regards,

Subha

RE: Issue with Editable Grid

Peter Lewis — Fri, 31 Jan 2020 14:14:19 GMT

I just tried in 19.3 and it works fine for me there too. I'm assuming this is just test data that you used to share on Community - maybe it's an issue with your actual data? I'm sorry, but I don't see anything obvious that is incorrect.

RE: Issue with Editable Grid

subhar — Fri, 31 Jan 2020 14:07:53 GMT

Hi Peter,

Thanks for looking into the issue.This has been included to remove nulls if any for testing purpose.Sorry for the confusion here. Even the result is same if the code snippet is as below.

selectionSaveInto: {
local!selectedIndex
},

Regards,

Subha

RE: Issue with Editable Grid

Peter Lewis — Fri, 31 Jan 2020 14:04:08 GMT

It's a little hard to tell because I am currently on 19.4 and it works for me. However, I'm confused by this section:

selectionSaveInto: {
  local!selectedIndex,
    a!save(
      local!selectedIndex,
      reject(
        fn!isnull(
          _
        ),
        a!flatten(
          save!value
        )
     )
  )
},

Why are you saving into the same variable twice? Also, why do you need the reject() and a!flatten() functions applied to the selected index()? I'm wondering if this behavior is causing the index to be updated to an incorrect value, which makes your first row always seem selected.