Saving editable grid

Question

Hello Team, 
 
 I have build an editable grind and now I want to save the values inside my records. I have record table and rule input in my interface the problem is how I can save this data for each request I have. The data is a sample there are around 15 rows which I want the user to be able to save some of them can be null some of them can be filled out. Basically the property is read only, once user enter value we can use a!save to save the property for the respective row, but I always get cannot index rule input records.. 
 rows: {
 a!gridRowLayout(
 contents: {
 a!richTextDisplayField(
 labelPosition: "COLLAPSED",
 value: {
 a!richTextItem(
 text: {"Melting Point"}
 )
 }
 ),
 a!textField(
 label: "Text",
 labelPosition: "ABOVE",
 saveInto: {},
 refreshAfter: "UNFOCUS",
 disabled: false,
 validations: {}
 ),
 a!dropdownField(
 choiceLabels: {"g/cm3", "kg/m3"},
 choiceValues: {"g/cm3", "kg/m3"},
 label: "Dropdown",
 labelPosition: "ABOVE",
 placeholder: "Select",
 saveInto: {},
 searchDisplay: "AUTO",
 validations: {}
 ),
 a!textField(
 label: "Text",
 labelPosition: "ABOVE",
 saveInto: {},
 refreshAfter: "UNFOCUS",
 validations: {}
 ),
 a!textField(
 label: "Text",
 labelPosition: "ABOVE",
 saveInto: {},
 refreshAfter: "UNFOCUS",
 validations: {}
 ),
 a!dropdownField(
 choiceLabels: {"℃", "℉"},
 choiceValues: {"℃", "℉"},
 label: "Dropdown",
 labelPosition: "ABOVE",
 placeholder: "Select",
 saveInto: {},
 searchDisplay: "AUTO",
 validations: {}
 ),
 a!dropdownField(
 choiceLabels: {"Property has not been measured"},
 choiceValues: {"Property has not been measured"},
 label: "Dropdown",
 labelPosition: "ABOVE",
 placeholder: "--- Select a Value ---",
 saveInto: {},
 searchDisplay: "AUTO",
 validations: {}
 )
 },
 showWhen: if(
 or(
 ri!AOS_PhysChem['recordType!{1ddc2dbc-133e-49a3-a416-3e896db0beb4}AOS_Phys_chem.fields.{6862862b-7cbf-4b5d-be70-7944f6a23f5b}PhysicalState'] = "LIquid",
 ri!AOS_PhysChem['recordType!{1ddc2dbc-133e-49a3-a416-3e896db0beb4}AOS_Phys_chem.fields.{6862862b-7cbf-4b5d-be70-7944f6a23f5b}PhysicalState'] = "Solid",
 ri!AOS_PhysChem['recordType!{1ddc2dbc-133e-49a3-a416-3e896db0beb4}AOS_Phys_chem.fields.{6862862b-7cbf-4b5d-be70-7944f6a23f5b}PhysicalState'] = ""
 ),
 true,
 false)
 ),
 a!gridRowLayout(
 contents: {
 a!richTextDisplayField(
 labelPosition: "COLLAPSED",
 value: {
 a!richTextItem(
 text: {"Freezing Point"}
 )
 }
 ),
 a!textField(
 label: "Text",
 labelPosition: "ABOVE",
 saveInto: {},
 refreshAfter: "UNFOCUS",
 disabled: false,
 validations: {}
 ),
 a!dropdownField(
 choiceLabels: {"g/cm3", "kg/m3"},
 choiceValues: {"g/cm3", "kg/m3"},
 label: "Dropdown",
 labelPosition: "ABOVE",
 placeholder: "Select",
 saveInto: {},
 searchDisplay: "AUTO",
 validations: {}
 ),
 a!textField(
 label: "Text",
 labelPosition: "ABOVE",
 saveInto: {},
 refreshAfter: "UNFOCUS",
 validations: {}
 ),
 a!textField(
 label: "Text",
 labelPosition: "ABOVE",
 saveInto: {},
 refreshAfter: "UNFOCUS",
 validations: {}
 ),
 a!dropdownField(
 choiceLabels: {"℃", "℉"},
 choiceValues: {"℃", "℉"},
 label: "Dropdown",
 labelPosition: "ABOVE",
 placeholder: "Select",
 saveInto: {},
 searchDisplay: "AUTO",
 validations: {}
 ),
 a!dropdownField(
 choiceLabels: {"Property has not been measured"},
 choiceValues: {"Property has not been measured"},
 label: "Dropdown",
 labelPosition: "ABOVE",
 placeholder: "--- Select a Value ---",
 saveInto: {},
 searchDisplay: "AUTO",
 validations: {}
 )
 },
 showWhen: if(
 or(
 ri!AOS_PhysChem['recordType!{1ddc2dbc-133e-49a3-a416-3e896db0beb4}AOS_Phys_chem.fields.{6862862b-7cbf-4b5d-be70-7944f6a23f5b}PhysicalState'] = "LIquid",
 ri!AOS_PhysChem['recordType!{1ddc2dbc-133e-49a3-a416-3e896db0beb4}AOS_Phys_chem.fields.{6862862b-7cbf-4b5d-be70-7944f6a23f5b}PhysicalState'] = "Solid",
 ri!AOS_PhysChem['recordType!{1ddc2dbc-133e-49a3-a416-3e896db0beb4}AOS_Phys_chem.fields.{6862862b-7cbf-4b5d-be70-7944f6a23f5b}PhysicalState'] = ""
 ),
 true,
 false)
 ),
 a!gridRowLayout(
 contents: {
 a!richTextDisplayField(
 labelPosition: "COLLAPSED",
 value: {
 a!richTextItem(
 text: {"Boiling Point"}
 )
 }
 ),

Mike Schmitt · Accepted Answer

Depending on your needs, you could do the above initialization either in the process prior to your form, or on your form itself. 
 For the sake of argument I've gone ahead and mocked up this simplified example grid with the first 2 "properties" from my example above, but now displayed on an on-form grid and ready to accept changes to the "value" column (saved into the "lastName" recordtype property since this is still my "personnel" record type). a!localVariables(

local!properties: {
 "freezing point",
 "melting point"
 },

local!initialRowData: a!forEach(
 local!properties,

'recordType!{...}Personnel'(
 'recordType!{...}Personnel.fields.{firstName}firstName': fv!item
 )
 ),

a!gridLayout(
 label: "Items",
 headerCells: {
 a!gridLayoutHeaderCell(label: "Property"),
 a!gridLayoutHeaderCell(label: "Value")
 },
 
 rows: a!forEach(
 local!initialRowdata,
 
 a!gridRowLayout(
 contents: {
 a!richTextDisplayField(
 value: a!richTextItem(
 text: fv!item['recordType!{...}Personnel.fields.{firstName}firstName']
 )
 ),
 
 a!textField(
 value: fv!item['recordType!{...}Personnel.fields.{lastName}lastName'],
 saveInto: fv!item['recordType!{...}Personnel.fields.{lastName}lastName']
 )
 }
 )
 )
 )
)

Mike Schmitt · Answer

Well, being able to initialize an array of RecordType data is really one of the simpler things you should learn about before attempting to do a (imho) somewhat complicated grid operation on them... 
 recordType data offers the unique challenge of not simply being able to create a local dummy and send you an example, however for the moment i've made a VERY rough example while using a generic "personnel" record type from my CE site (and we can pretend the "firstName" field is the one that should store the property, for the purposes of this). Here we start with an array of the various "properties", then merely loop over it, setting the recordType field to the current iteration's value. You can see here the result is a list of that recordType initialized with just that value set in each item.

Mike Schmitt · Answer

Depends on how you've initialized it - if you did it in a PV, simply pass the PV value into your form (and back out into your process again). If you'd rather initialize as a local variable like here (easiest if you want the interface easily testable), then have your Submit button save a copy of the local variable's final state into a Rule Input (set as an array of your record type), to be passed back out into your process.

Saving editable grid

Top Replies