Saving editable grid

RE: Saving editable grid

Shwapx — Tue, 09 Jul 2024 15:33:19 GMT

I have a text field above the grid which user need to select and it has 3 options based on what user selected the grid should show only certain properties. So essentially i need to have 3 different grids with different properties. I can hide the grid initially and when user select something in the text field to show proper grid.

RE: Saving editable grid

Mike Schmitt — Tue, 09 Jul 2024 13:50:12 GMT

[quote userid="234483" url="~/discussions/f/general/35402/saving-editable-grid/137785"]hide specific rows based on selection from text field.[/quote]

i'm still fuzzy on what "text field" you mean. I'd point out that you can always utilize the "showWhen" parameter within the a!gridRowLayout() rule, inside the a!forEach() call, naming whatever logic you need to show or hide that row depending on what the current row's value contains. I'd caution that showing/hiding a row based on an input in that row, though, can be troublesome since you could find yourself in a situation where a user accidentally selects a value that causes the row to be hidden, then the row goes away, and they have no way to bring it back (since it's now hidden). But as long as this is carefully managed then it should be able to be used fine.

RE: Saving editable grid

Shwapx — Tue, 09 Jul 2024 00:09:14 GMT

I think I was able to achieve what I need. Thank you for the help! The only thing left is how to hide specific rows based on selection from text field.

Maybe the easiest way would be to have 3 different local variables and based on the field use that in the grid not sure if i can have if function after the for each where i define the localvariable.

RE: Saving editable grid

Mike Schmitt — Mon, 08 Jul 2024 22:42:38 GMT

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.

RE: Saving editable grid

Shwapx — Mon, 08 Jul 2024 22:23:24 GMT

It's working in local!variable, but i need to pass this to rule input so i can pass that data in my other interfaces.

RE: Saving editable grid

Shwapx — Mon, 08 Jul 2024 21:33:07 GMT

Okay did that and now I need to pass that to my rule input?:

RE: Saving editable grid

Mike Schmitt — Mon, 08 Jul 2024 21:03:16 GMT

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']
          )
        }
      )
    )
  )
)

RE: Saving editable grid

Mike Schmitt — Mon, 08 Jul 2024 20:52:52 GMT

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.

RE: Saving editable grid

Shwapx — Mon, 08 Jul 2024 20:43:04 GMT

Yes this is exactly what i need, but there is the issue I have never done that and i'm not quite sure how to:

"You would therefore initialize the rows in advance, setting each row to one of your desired "property" settings (i assume this is "melting point", "freezing point", etc)"

RE: Saving editable grid

Mike Schmitt — Mon, 08 Jul 2024 20:41:43 GMT

[quote userid="234483" url="~/discussions/f/general/35402/saving-editable-grid/137776"]If you can give me an idea how to do that would be great![/quote]

It sounds as if you mean to have 17 rows of data in that particular record type. You would therefore initialize the rows in advance, setting each row to one of your desired "property" settings (i assume this is "melting point", "freezing point", etc). Then your grid could merely call a!forEach over all 17 rows of initialized data and display the needed rows. Further logic could discern whether any given row (or individual fields within it) should be treated differently depending on what the given property is, or other settings saved within that row's data per what the user's filled out.

RE: Saving editable grid

Shwapx — Mon, 08 Jul 2024 19:58:12 GMT

If you can give me an idea how to do that would be great!

"Why isn't the property stored in the array-row's data and displayed there"

RE: Saving editable grid

Mike Schmitt — Mon, 08 Jul 2024 19:35:12 GMT

[quote userid="234483" url="~/discussions/f/general/35402/saving-editable-grid/137774"]they have to be hardcoded[/quote]

Why?

[quote userid="234483" url="~/discussions/f/general/35402/saving-editable-grid/137774"]that means I need to have 17 tables linked[/quote]

I'm pretty sure nobody's suggesting you break this out into 17 different tables.

[quote userid="234483" url="~/discussions/f/general/35402/saving-editable-grid/137774"]So the property can be hardcoded visually for the user (read only) [/quote]

Why isn't the property stored in the array-row's data and displayed there, as opposed to hardcoding 17 separate GridRows? Something is very much not making sense with your implementation.

RE: Saving editable grid

Shwapx — Mon, 08 Jul 2024 19:29:02 GMT

These are hardcoded properties for each request, they have to be hardcoded.. So once user let's say fill out first row in the records in the property filed they will see Melting Point and rest of the information.

If I have separate record table for each property that means I need to have 17 tables linked.. which sounds insane.. So the property can be hardcoded visually for the user (read only) and then if they fill out unit with a!save to save the unit and also the property from that row that was the intention..

RE: Saving editable grid

Mike Schmitt — Mon, 08 Jul 2024 19:23:07 GMT

[quote userid="234483" url="~/discussions/f/general/35402/saving-editable-grid/137772"]just property is different[/quote]

I'm still not sure how to make sense of this. What is the "property"? How is it determined? Why does it require hardcoding completely separate grid rows, wherein most of the fields in each aren't actually editable at all as they don't point to source data and don't have a save target?

RE: Saving editable grid

Shwapx — Mon, 08 Jul 2024 18:31:42 GMT

no 17 exactly the same just property is different. And based on selection of text field on top some of them hide.

RE: Saving editable grid

Mike Schmitt — Mon, 08 Jul 2024 17:30:13 GMT

So just 2 rows?

RE: Saving editable grid

Shwapx — Mon, 08 Jul 2024 16:53:52 GMT

You can see it here

RE: Saving editable grid

Mike Schmitt — Mon, 08 Jul 2024 16:24:57 GMT

Again, just manually add the field(s) you need to a section (etc). You are free to use whatever logic you need in order to relate them to each other. Nothing about this, at least as far as your example code above is structured, requires any sort of grid whatsoever - since you're not using the grid rows to each act on a different member of an array of data, but instead hardcoding each row to look at an individual property (which is unnecessarily difficult and adds unnecessary complexity). I guess it *can* work as an editable grid (after sorting out the issues with properly addressing data, etc), though I honestly can't see the benefit it provides you.
On a side note: do you have a mock-up of any sort, for what you're hoping your form/grid to eventually look like? I honestly can't even tell.

The age-old advice in cases like this, is to learn to crawl before you try to run. You should step back and familiarize yourself with how editable grids work, overall, and in a bit simpler of a setup - as well as multi-field forms that don't have/use grids. Only after you understand these fundamendals intrinsically, should you be attempting what you're trying here.

RE: Saving editable grid

Shwapx — Mon, 08 Jul 2024 16:12:54 GMT

Yes, and then how do you save multiple things in the same column. You can see my record i and the grid i will have the user enter 15 times the value but for different property which need to be written as well in the property record. How do i specifically say to the rule input that the first value is for first property.. this is the reason grid is used.

RE: Saving editable grid

Mike Schmitt — Mon, 08 Jul 2024 15:08:00 GMT

[quote userid="234483" url="~/discussions/f/general/35402/saving-editable-grid/137752"]but how do you save the multiple fields in same record[/quote]

add multiple fields to a form?

RE: Saving editable grid

Shwapx — Mon, 08 Jul 2024 14:53:14 GMT

Sounds good, but how do you save the multiple fields in same record?

RE: Saving editable grid

Mike Schmitt — Mon, 08 Jul 2024 14:44:03 GMT

The use case for an editable grid is, generally, multiple rows of the same property. As Stefan mentioned a few times before, this does not sound like the use case for a grid at all. Why not just have multiple fields that the user fills out?

RE: Saving editable grid

Shwapx — Mon, 08 Jul 2024 14:32:55 GMT

What would be the best way to save that when each row should be unique row and should have unique property. Somehow I need to initialize the rule input with already field out rows for the property. And at the same time i need to hide some of the rows based on what user have selected in another field.

RE: Saving editable grid

Mike Schmitt — Mon, 08 Jul 2024 14:13:06 GMT

Echoing others, I'm completely perplexed as to what you're attempting to do here. Why are you manually declaring multiple a!gridRowLayout() calls in your code? That's not a standard pattern for Editable Grids at all.

RE: Saving editable grid

rishabh982812 — Mon, 08 Jul 2024 12:23:01 GMT

As per your requirements, You can club multiple conditions on this.