gridField - fv!row vs fv!identifier

RE: gridField - fv!row vs fv!identifier

Mike Schmitt — Thu, 09 Mar 2023 15:26:23 GMT

[quote userid="82813" url="~/discussions/f/new-to-appian/28023/gridfield---fv-row-vs-fv-identifier/109103#109103"]I usually use a local variable and look at the local variable panel or simply add a 'text field'[/quote]

Those work well too - just not necessarily for grid data, which the example I provided handles reasonably well. In the old days there was no "local variables preview pane", so we *always* had to add a "debug" paragraph field in random spots on our forms to verify the values of local variables in question. These days it's much easier, luckily!

RE: gridField - fv!row vs fv!identifier

Komal Jain — Thu, 09 Mar 2023 14:56:14 GMT

Great. I assumed the data is improper dictionary structure and so you are facing issue while using .number.

RE: gridField - fv!row vs fv!identifier

MaNa — Thu, 09 Mar 2023 14:45:08 GMT

Komal
The issue was my incorrect usage of syntax to access the data field. I was originally using it as shown in the image below.

As Mike Schmitt pointed out (and as your example shows), I was using fv!row as an index to the data ".number[fv!row]" which is incorrect. I should have used "fv!row.number".

I am not sure what you mean by 'data structure is incorrect'. The local variable I am using is as shown in the earlier image I had sent.

Thanks for your help.

RE: gridField - fv!row vs fv!identifier

Komal Jain — Thu, 09 Mar 2023 14:25:38 GMT

I tried this

a!localVariables(
local!data:{{number:301,name:"Calcium"},
{number:303,name:"Calcium"}},
a!gridField(
data: local!data,
columns: a!gridColumn(
label: "Number",
value: fv!row.number
)

)
)

and it worked

Are you using a!localVariables if yes could you please share the data of you local variable from the local variable data section

I strongly feel your data structure is incorrect

RE: gridField - fv!row vs fv!identifier

MaNa — Thu, 09 Mar 2023 14:14:27 GMT

Mike,

Thank you for that hint. I usually use a local variable and look at the local variable panel or simply add a 'text field'. Is there any better way to do debugging?

Thanks.

RE: gridField - fv!row vs fv!identifier

MaNa — Thu, 09 Mar 2023 14:09:15 GMT

Mike,

Quite possible I am confusing the two - but I am also wondering why I went down the variable.fieldname[fv!...] path. I have been using various interface recipes as the starting point for my learning process, so could be from one of those example - which I misunderstood.

But I will keep my eyes open if I come across it.

RE: gridField - fv!row vs fv!identifier

Mike Schmitt — Thu, 09 Mar 2023 13:42:33 GMT

[quote userid="82813" url="~/discussions/f/new-to-appian/28023/gridfield---fv-row-vs-fv-identifier/109096#109096"]examples where they use ".fieldname[fv!row]"[/quote]

Can you link me to where examples are written in this way? I've never seen anything like that. Off the top of my head I wonder if you might be getting this confused with how rows are written when using RecordType data, which is more like "value: fv!row[recordtype!RecordName.Fields.property]", maybe?

RE: gridField - fv!row vs fv!identifier

Stefan Helzle — Thu, 09 Mar 2023 13:40:46 GMT

Just follow the error message to solve this.

Check out this example from the documentation of how to use fv!row.

docs.appian.com/.../read-only-grid-configuration.html

RE: gridField - fv!row vs fv!identifier

Mike Schmitt — Thu, 09 Mar 2023 13:39:41 GMT

As an additional hint: sometimes i'll add a debug column where i just set the value to fv!row by itself - it displays the value of the entire row and helps me remember what properties i have available to add columns for (and to verify that the values look correct). You just need to comment it out, or set its showWhen parameter to false when not in use.

RE: gridField - fv!row vs fv!identifier

MaNa — Thu, 09 Mar 2023 13:36:18 GMT

Mike,

That makes so much more sense. I always wondered why I had to provide the variable name if the data-attribute already defined the data-source.

This worked.

Guess I have to review examples where they use ".fieldname[fv!row]" to access individual values to determine what is the difference by example and their example.

Thank you!

RE: gridField - fv!row vs fv!identifier

MaNa — Thu, 09 Mar 2023 13:30:31 GMT

HI Komalj

If I understand your request correctly, this is the information you information you are seeking.

RE: gridField - fv!row vs fv!identifier

Mike Schmitt — Thu, 09 Mar 2023 13:27:55 GMT

The main issue is you're not using fv!row correctly at all -- fv!row is the row value, it's not something that you'd use to access a positional index of the original array, which is what you're trying to do here for some reason.

The proper syntax is:

value: fv!row.number  /* or whatever property of the original dictionary you want to access here */

RE: gridField - fv!row vs fv!identifier

Komal Jain — Thu, 09 Mar 2023 13:20:37 GMT

Could you please share the data store in local variable currentProductNutrients

RE: gridField - fv!row vs fv!identifier

MaNa — Thu, 09 Mar 2023 13:20:04 GMT

Hi Harshit:

Thank you for your response. I tried various combinations. I am trying to create a grid layout with the following columns:

Number | Name | Amount | Unit

Here is my data: output I am starting with:

I get errors when I tried to move the '.number' to the data-attribute.

I also get errors when I tried a couple other variations of fv!row and .number.

RE: gridField - fv!row vs fv!identifier

MaNa — Thu, 09 Mar 2023 13:15:25 GMT

Hi Stefan:

Thank you for your response. I tried datasubset variations too. Those led to errors too.

RE: gridField - fv!row vs fv!identifier

Stefan Helzle — Thu, 09 Mar 2023 07:29:03 GMT

The grid field expects a datasubset as the datasource. It iterates on the items and make each individual item available as fv!row and the corresponding identifier (datasubset.identifiers) as fv!identifier.

RE: gridField - fv!row vs fv!identifier

Harshit Bumb (Appyzie) — Thu, 09 Mar 2023 06:40:19 GMT

The problem is with the ".number" in value. If you add the same on the data parameter, then fv!row should work.