User Interface - Recent Threads

RE: Image is not rendering in billboardLayout

Shubham Aware — Thu, 16 Apr 2026 06:43:18 GMT

Re-save the JPG as a fresh image and upload again, because Appian a!billboardLayout renders only a valid a!documentImage() and can fail when the file was renamed or converted incorrectly.

Image is not rendering in billboardLayout

kl0001 — Wed, 15 Apr 2026 20:49:06 GMT

I'm running through the spaceX integration demo as practice, and when the step got to the end and I'm supposed to upload an image to the billboard layout, but it didn't render. The document is jpg file, and it does end up rendering in the a!imageField (only when it's set to size = FIT) as you can see in the corner there. I can get other jpgs to render, but not this one. I'm wondering if it might be because it's too big (size = 20.12kb) or because it downloaded as a web file and I had to manually change extension to jpg (but it loads fine in the file preview when I click on the doc).

Anyone know why it might not be rendering? Thank you!

Unable to take properties into a forEach() for a fv!item

francescagulinelli — Wed, 15 Apr 2026 09:56:59 GMT

I'm having some issues understanding how to use indexes into a forEach taking the items from a expression rule.

I'll explain my problem a little bit deeper; I'm trying to get some of the properties from the RecordType "Anomalie", i would like to use the expression rule with get me all of the anomalies linked to a specific pension by the pensionid, and get the description, the name, the action related to it. But i'm having trubles indexing these properties once I call the expression rule. When I try to use fv!item.description into the description rich text field it seems like it doesn't recognize the object as a record type.

I pasted the code snippet for the forEach i have in the interface, does anyone had some similar issues and may give me suggestions on what to try to make it work? Thank you so much!!

(my finished product should be a card for each anomaly found linked to the record Beneficiary, each with their description, name and related action)

a!forEach(items: rule!SRI_AnomaliePensione(pensioneId: ri!record['recordType!SRI beneficiario.relationships.pensione.fields.chiavePensioneCorrente']),
expression: a!cardLayout(
contents: {
a!richTextDisplayField(
labelPosition: "COLLAPSED",
value: {
a!richTextItem(text: { "Anomalia" }, style: { "STRONG" })
}
),
a!richTextDisplayField(
labelPosition: "COLLAPSED",
value: { "Descrizione anomalia" } */should be fv!item.description/*
),

a!sideBySideLayout(
items: {
a!sideBySideItem(
item: a!tagField(
labelPosition: "COLLAPSED",
tags: {
a!tagItem(
text: "Aperta", */should be fv!item.status/*
backgroundColor: "#cc0000"
)
}
)
),
a!sideBySideItem(
item: a!buttonArrayLayout(
buttons: {
a!buttonWidget(
label: "Sana anomalia", */should be the recordActionField "sana anomalia" with identifie: fv!identifier /*
size: "SMALL",
width: "MINIMIZE",
style: "SOLID"
)
},
align: "END",
marginBelow: "NONE"
)
)
}
)
},
height: "AUTO",
style: "#efefef",
shape: "SEMI_ROUNDED",
marginBelow: "STANDARD",
borderColor: "#1155cc",
showShadow: true
))

RE: Unable to take properties into a forEach() for a fv!item

Harsha Sharma — Thu, 16 Apr 2026 06:29:24 GMT

The datatype of the list of items within a!foreach() might impact the indexing behaviour.

In your case you can check the output data type of this rule - rule!SRI_AnomaliePensione() - It can return a list of record types or a map.

For me, both the square brackets and index() are working so I coulnt replicate a scenario where index() works but square bracket doesn't! May be if you share the output data type of the Anomalie rule, I can try to reproduce the same and respond better.

RE: Unable to take properties into a forEach() for a fv!item

Mike Schmitt — Wed, 15 Apr 2026 13:45:01 GMT

Whoops, it appears I'm slightly wrong - apparently at least for RecordType data, it does make a difference to leave out the ".data" in either the "items" parameter or "value" parameter of the forEach loop. I believe traditional CDT-style queried data did not work this way, but now I'll have to go back and double check.

So you have the choice, you can either add ".data" in the "items" parameter or the "expression" parameter - in this example i've added it in the "expression" parameter and we can see it works.

Edit: the data array is better off if you do it with the ".data" in the "items" parameter, as you get a cleaner list of data.

RE: Unable to take properties into a forEach() for a fv!item

francescagulinelli — Wed, 15 Apr 2026 13:40:49 GMT

thank you for answering!

I tried with just fv!item[RT.field] but i didn't work, I got it to work just with the index function. Whould you know how to explain to me the difference between the two options? Why does it seems that one actually get the object inside the expression rule and the other doesn't?

Thank you so much!

RE: Unable to take properties into a forEach() for a fv!item

francescagulinelli — Wed, 15 Apr 2026 13:37:07 GMT

Thank you for answering!

One question: if this is the case what is wrong that i can't see or reference the properties of the dataSubset from the fv!item inside the forEach?

As people suggested with the index( fv!item,'recordType!{SRI anomaliepensione.fields.description'," "), the forEach is working, is there another way to avoid using the index function?

RE: Unable to take properties into a forEach() for a fv!item

Mike Schmitt — Wed, 15 Apr 2026 13:30:19 GMT

[quote userid="299046" url="~/discussions/f/user-interface/40338/unable-to-take-properties-into-a-foreach-for-a-fv-item/154280"]The rule returns a DataSubset, not a plain list.
[/quote]

FYI, a!forEach() can inherently handle a simple array OR a dataSubset, and the properties are accessed via fv!item inside the forEach loops just the same.

EDIT: it appears this is somewhat outdated info at least in the case of recordtype data queries - the ".data" is needed either in the "items" or "expression" parameter of the a!forEach() in order for the properties to index properly.

To confirm, what I described above is how CDT / data store style queried DataSubsets work in a!forEach(), apparently there's an inconsistency with the behavior of a dataSubset that contains recordtype data...

Final note: I just remembered, the cause of this is because queryRecordType() returns a map, not a dataSubset (it's just dataSubset-shaped). This causes all sorts of "fun" issues 🤦

RE: Unable to take properties into a forEach() for a fv!item

Shubham Aware — Wed, 15 Apr 2026 11:04:46 GMT

francescagulinelli

The rule returns a DataSubset, not a plain list.
Add .data after your rule call to get the actual rows(rule!SRI_AnomaliePensione(...).data).
Use bracket notation fv!item[recordType!...] instead of fv!item.description.

RE: Unable to take properties into a forEach() for a fv!item

Stefan Helzle — Wed, 15 Apr 2026 10:51:00 GMT

Try this page in the documentation:

https://docs.appian.com/suite/help/26.3/reference-records.html

RE: Unable to take properties into a forEach() for a fv!item

Harsha Sharma — Wed, 15 Apr 2026 10:39:30 GMT

yes you need to type the record type name then fields then the field name. so it looks like a record field rather than fv!item.description.

 fv!item[recordType!Anomalie.fields.description]

In Interface it would look something like below with the record type icon.

So first configure the desctiption field properly. SImilar you need to do for 'status' as well. If you have 3 items in the record list, 3 cards should be visible as per your code.

RE: Unable to take properties into a forEach() for a fv!item

francescagulinelli — Wed, 15 Apr 2026 10:30:58 GMT

Thank you so much for the answer!

I tried doing as you told me but received error like my RT anomaly.description is not of type text but Record Field, like it's not getting the value filtered by the pensionID.

My expression rule (when giving a value to the rule input "pensionID: 7839158") returns a List of SRI anomaliepensione - 3 items.

Do you think i'm referencing the right object or is the construct wrong? How would you advise to build the card component for the needs explained?

Thank you so much for your help!!

RE: Unable to take properties into a forEach() for a fv!item

Yashwanth Akula — Wed, 15 Apr 2026 10:27:50 GMT

Hi Francescag5899,

What is the data type of the data that you are passing to foreach items?
you need to index with the record type fields if the fv!item is of record type

Refer to this:

RE: Unable to take properties into a forEach() for a fv!item

Harsha Sharma — Wed, 15 Apr 2026 10:21:18 GMT

Instead of using fv!item.description use record type reference for the field description. E.g. fv!item['recordType!Anomalie.fields.description']

If the rule rule!SRI_AnomaliePensione(pensioneId: ri!record['recordType!SRI beneficiario.relationships.pensione.fields.chiavePensioneCorrente']) returnds a record type then fv!item need to have proper record type reference for the field involved, dot (.) notation simply wont work as it is not a dictionary, cdt or list of vairant.

RE: views and action security refresh

alex.acosta — Tue, 14 Apr 2026 16:38:09 GMT

I would recommend changing the a!recordActionField() to use either the "MENU" and "MENU_ICON" with securityOnDemand set to true, this way the security evaluates when the user clicks to open the menu. Keep in mind that a!refreshVariable() with refreshAfter: "RECORD_ACTION" only controls when a local variable’s value is recalculated after a record action dialog completes; it does not control when the record action’s own visibility/security is re‑evaluated.

views and action security refresh

saisaran31 — Wed, 08 Apr 2026 21:11:22 GMT

Hello Everyone,

In my record view interface, I have a child interface that contains a related action. I recently added another related action whose only purpose is to refresh the data. In the parent interface, I’m using a!refreshVariable() so that local variables are refreshed after a record action completes.

The related action in the child interface has visibility logic defined both:

in the record type (Views and Actions → action security/visibility), and
inside the child interface itself.
When I click my refresh-related action, all the data and components in the interface are refreshed, but the visibility condition defined in Views and Actions is not re-evaluated. As a result, when I refresh to load the latest data, the related action does not appear on the screen unless I do a full browser refresh.

i tried to have a start form in my related action's process model even at that time screen was not refreshed. Pretty much tried everything still record level security was not evaluated without manual browser refresh

RE: views and action security refresh

saisaran31 — Thu, 09 Apr 2026 08:47:35 GMT

Thanks for your reply Shubham Aware and Stefan Helzle . Now i came up with the solution that to have a refresh related action in the record header so that when a user clicks the entire record get reloaded similar to a browser refresh

RE: views and action security refresh

Stefan Helzle — Thu, 09 Apr 2026 05:51:23 GMT

To refresh data, I typically use some local variable. Then, I wrap all the queries I want to trigger into a refresh variable referencing this local. Then, I modify that local using a button or link.

RE: views and action security refresh

Shubham Aware — Thu, 09 Apr 2026 05:16:07 GMT

Record action visibility defined in Views & Actions is evaluated at page load time, not on a!refreshVariable(). Even with a start form or refresh action, Appian does not re-evaluate action-level security mid-session without a full page reload.
You can try to move the visibility logic entirely into the child interface using a local variable that refreshes with your data. Remove it from Views & Actions.

RE: Loading one interface immediately after another

Chris — Tue, 07 Apr 2026 14:15:49 GMT

Unfortunately we cannot use a!startProcessLink() inside of a!buttonWidget().

Loading one interface immediately after another

Vladislav Morozov — Wed, 01 Apr 2026 10:45:21 GMT

Consider blue path only! I used activity chain to start "Choose policy" interface immediately after the main interface. The process is started by a startProcess inside a saveinto of a buttonWidget. After clicking the button the process starts, but the interface isn't automatically loaded. The owner of the task is set as pp!initiator. What could I miss?

Appian Grid

Gaurav Kataria — Tue, 07 Apr 2026 05:07:52 GMT

We are encountering the following error in our Appian application:

ERROR com.appiancorp.record.service.visitor.DiscoverAllRecordBindings - 
Exception encountered in grid field tree visitor, falling back in try catch.
java.lang.NullPointerException

This issue appears while working with a grid component (record-based or interface grid). There are no obvious breaking changes, but the error is being logged intermittently.

We suspect it may be related to:

Null values in grid field bindings
Record type relationships
Nested field references in grid columns

However, we are unable to pinpoint the exact cause.

What typically causes this DiscoverAllRecordBindings NullPointerException?
Are there recommended best practices to avoid this issue in grid configurations?
How can we effectively debug which field or binding is causing the problem?

Any guidance or suggestions would be greatly appreciated!

RE: Appian Grid

Stefan Helzle — Tue, 07 Apr 2026 05:33:37 GMT

Do you see this message in log files only? Does the grid work? If both is true, I suggest to either ignore it, or open a support case to make Appian aware of this minor issue.

RE: Appian Grid

Shubham Aware — Tue, 07 Apr 2026 05:29:31 GMT

Wrap relationship field references in if(isnull(...), "", ...) or use a custom record field with null-safe expressions instead of referencing relationship fields directly in grid columns.
After any Record Type schema change, verify all grid column fieldConfigs still point to valid fields.

Also you can try debug,
Temporarily remove grid columns one by one and reload - when the error stops, the last removed column is the culprit.

Styled Text Editor

Vaishal — Mon, 03 Nov 2025 08:09:57 GMT

Hello Everyone,

I’m using a Styled Text Editor for my comment thread component. If the character count exceeds 500 characters, I need to trim the text and display a "Show more" link outside the Styled Text Editor.

The problem I’m facing is that the Styled Text Editor stores values with HTML tags, so when I trim the content directly, it can cut through tags and break the markup. This results in invalid HTML and rendering issues.

Has anyone implemented an approach to safely truncate HTML without breaking tags? Any suggestions or best practices would be appreciated.