Editable Grid with dateField not updating due to index.

RE: Editable Grid with dateField not updating due to index.

judym598 — Wed, 22 Jul 2020 14:27:44 GMT

Unfortunately, that didn't work for sorting the local!selectedRows. I'm moving on from here - at least the data is correct! in all likelihood, the selections would be made in order.

RE: Editable Grid with dateField not updating due to index.

Mike Schmitt — Mon, 20 Jul 2020 13:18:03 GMT

Hi - As I mentioned in an earlier reply (which i think you may have missed), having a "saveInto" in a Read Only field will literally do nothing, as the saveInto parameter only executes upon user interaction with that field. You need to add your extra save information into the saveInto parameter of the Account Number field, if it's by interaction with that field that you want the date in question to get updated.

RE: Editable Grid with dateField not updating due to index.

judym598 — Mon, 20 Jul 2020 02:39:23 GMT

Got another question here on my date field. I don't want the user to edit the value (which i why it is readOnly), but I want it updated if the user changes the account number to 'today()'. What I have below displays the correct date in the form but it does not save it to the local variable - therefore, it does not get saved once I leave the form. How do I get the local variable to update? I tried using a!save (see last line) to force it to save to the local variable, but it's not.

a!dateField(
label: "Effective Date "& fv!index,
value: if(fv!item.accountNum = ri!newAccount_cdt.accountNum, today(), ri!newArngmt_cdt.effectiveDate),
saveInto: fv!item.effectiveDate,
readOnly: true
)

Tried this for the saveInto - but it didn't work:

saveInto: a!save(fv!item.effectiveDate,local!newArngmt.effectiveDate)

RE: Editable Grid with dateField not updating due to index.

judym598 — Fri, 17 Jul 2020 19:32:17 GMT

Thank you Mike. I think that will work. I will update this thread on Monday if it does - maybe it will help others out.

RE: Editable Grid with dateField not updating due to index.

Mike Schmitt — Fri, 17 Jul 2020 18:53:23 GMT

Basically I just mean moving the "data:" field from your read-only grid into a local variable above the grid definition. I could give you pointers on executing the save in an order-preserving manner if you got that part taken care of.

Alternatively, the one supported method for sorting a CDT (i.e. in your grid's saveInto), would be to call toDataSubset on it and pass in paging info with sorting on the column you'd want to sort by. The result of this would be that the ri!newArngmt_cdt data would be sorted by that column regardless of the selection order OR current sorting of the paging grid (which i suppose is probably what you want).

For this, and bear with my guesswork here, but I assume you could replace this

a!save(ri!newArngmt_cdt, local!selectedRows)

with something like this (assuming for example's sake that you want it to be sorted on "accountNum") --

a!save(
  ri!newArngmt_cdt,
  todatasubset(
    local!selectedRows,
    a!pagingInfo(
      startIndex: 1,
      batchSize: -1,
      sort: a!sortInfo(
        field: "accountNum",
        ascending: true()
      )
    )
  ).data
)

RE: Editable Grid with dateField not updating due to index.

judym598 — Fri, 17 Jul 2020 18:46:28 GMT

Wow....are there instructions on how to do that in the documentation? I take it there's no way to 'sort' on a local!variable..

RE: Editable Grid with dateField not updating due to index.

Mike Schmitt — Fri, 17 Jul 2020 18:42:41 GMT

That's a tricky one. Since you're querying the data for the read-only grid directly within the read-only grid, the one idea i had is basically out the window. In that, every time the user did a selection, you'd build the array of selected row data by iterating over the original data set and adding every member that corresponded with the index of the new selection (keeping the ordering consistent regardless of additions or deletions).

RE: Editable Grid with dateField not updating due to index.

judym598 — Fri, 17 Jul 2020 14:47:27 GMT

Please see the attached. Note that it is not complete. I've added comments at the top to explain what my intentions are.community.appian.com/.../gridUpdates.txt

RE: Editable Grid with dateField not updating due to index.

Mike Schmitt — Fri, 17 Jul 2020 14:31:42 GMT

How are you currently assembling the array of data used for the editable grid, based on the user's selections from the read-only grid? Mind sharing a snippet of the relevant code? I'd guess you could likely keep the editable lines in the original order pretty easily but again it sorta depends on the specifics.

RE: Editable Grid with dateField not updating due to index.

judym598 — Fri, 17 Jul 2020 14:26:24 GMT

I was afraid you'd say that. What I'm doing is

1) Displaying data in a read only grid (from an expression rule the uses an a!queryEntity) - and allowing the user to select the items to edit which then gets stored into another rule input.

2) The editable grid then displays with the data selected. if the user selects them in order - they will display correctly, but if the user selects the bottom one first, then the 2nd one - they will display in the order selected on the first grid.

I have to keep the data 'local' until the updates are approved - before committing the changes to the database. Is there a way to sort the data in the rule input that is selected in the first grid?

RE: Editable Grid with dateField not updating due to index.

Mike Schmitt — Fri, 17 Jul 2020 14:20:46 GMT

[quote userid="2799" url="~/discussions/f/user-interface/19271/editable-grid-with-datefield-not-updating-due-to-index/75435"]how do I get the data displayed in the editable grid to sort[/quote]

Effectively the only way I'd recommend attempting to sort an editable grid is to sort the data ahead of time - if you're querying the underlying data on-form, for example, just sort by whichever field you want in the initial query. If you're using a passed-in rule input, then you could attempt to massage the data before rendering it on the grid, but this gets super messy and cumbersome; if at all possible i'd recommend editing the process model to either query the data in a sorted manner or perhaps sort it for you before entering the task. Again this all depends on how and when you're querying/assembling the data used for the grid.

RE: Editable Grid with dateField not updating due to index.

judym598 — Fri, 17 Jul 2020 14:12:15 GMT

Good catch Mike! I should have had ri!newArngmt_cdt.effectiveDate! Once I changed that - it worked. THANK YOU!!!

a!dateField(
label: "Effective Date "& fv!index,
value: if(fv!item.accountNum = ri!newAccount_cdt.accountNum,
today(),
ri!newArngmt_cdt.effectiveDate),
saveInto: fv!item.effectiveDate,
readOnly: true
)

One other question on this - how do I get the data displayed in the editable grid to sort by the id?

RE: Editable Grid with dateField not updating due to index.

Stewart Burchell — Fri, 17 Jul 2020 14:06:31 GMT

Doh! That'll teach me to read the code properly...yes, I agree..

RE: Editable Grid with dateField not updating due to index.

Mike Schmitt — Fri, 17 Jul 2020 14:06:21 GMT

Why are you filling out the saveInto parameter for a Read Only date field? This is not needed and won't do anything. Any chance the error goes away if you comment it out?

If you still get the error after commenting that out, then replace "ri!selectedAccount_cdt.effectiveDate" with "property(ri!selectedAccount_cdt, "effectiveDate", null())".

RE: Editable Grid with dateField not updating due to index.

Mike Schmitt — Fri, 17 Jul 2020 14:03:32 GMT

It could also be ri!selectedAccount_cdt that doesn't have the 'effectiveDate' property - in fact that would be my first guess over fv!item based on the current setup.

RE: Editable Grid with dateField not updating due to index.

judym598 — Fri, 17 Jul 2020 14:00:08 GMT

items: local!updatedArngmt - which is used to update records in a rule input associated with a data entity. The data entity does have a datefield called 'effectiveDate' If I leave it as an edited field - I can update the date just fine. For some reason - it won't update based on the selection made in the previous instance. Does the Data Entity have to have an index on the date field? I know the other text field does. I also thought that if I could have the data displayed in the editable grid sorted by id - it might help too.

RE: Editable Grid with dateField not updating due to index.

Stewart Burchell — Fri, 17 Jul 2020 13:50:21 GMT

The error suggests that your fv!item object does not have a property called 'effectiveDate' - are you able to share the data type that is associated with an instance of fv!item?