Editable Grid with dateField not updating due to index.

Question

I am configuring an editable grid. I have a couple readOnly fields that get populated based on what the user selects in one of the other editable fields. 
 In this specific case, if the user selects a specific account number (the dropDownField(), the textfield above this gets updated. This field updates correctly. However, I get an error with that same if() statement for the dateField. How do I resolve this. See attached for code snippet and error.

Mike Schmitt · Accepted Answer

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
)

Mike Schmitt · Answer

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.

Mike Schmitt · Answer

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.

Mike Schmitt · Answer

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()) ".

Mike Schmitt · Answer

Unknown said: how do I get the data displayed in the editable grid to sort 
 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.

Mike Schmitt · Answer

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).

Editable Grid with dateField not updating due to index.

Top Replies