Appian UI Error: getfontawesomefriendlynamebyid_appian_internal Invalid Icon ID

Hello ramanadhat267687    ,

During the second iteration of the a!forEach() loop, the icon value is either:

• not a valid  icon name ,

• incorrectly formatted (e.g., "fa-home" instead of "home"), or

• null/empty, which Appian cannot process.

To fix this issue 

• Validate all icon names used in the list. - refer this link: docs.appian.com/.../Appian_Icons.html

• Ensure no null, empty string, or unsupported icon identifiers are included.

• Use proper icon names

Hello ramanadhat267687    ,

During the second iteration of the a!forEach() loop, the icon value is either:

• not a valid  icon name ,

• incorrectly formatted (e.g., "fa-home" instead of "home"), or

• null/empty, which Appian cannot process.

To fix this issue 

• Validate all icon names used in the list. - refer this link: docs.appian.com/.../Appian_Icons.html

• Ensure no null, empty string, or unsupported icon identifiers are included.

• Use proper icon names

The actual issue for ramanadhat267687 he was able to access other application but when he was trying to access one specific application, he is getting the above error we can understand the above fix but in which expression we have to fix this we have tried by global search with expression, but we couldn't figure out the culprit. 

Hi karthikeyanp2283 — thanks for clarifying the context that the error only happens for one specific application.

• The error getfontawesomefriendlynamebyid_appian_internal → “invalid icon id” means that somewhere in that app’s UI code (interface, rule, site, or dashboard), there’s an icon component referencing an invalid or unsupported icon ID.

• Because other applications work fine, the invalid icon reference is local to that one application — maybe in a landing page, site page, record view, or a nested component.

• Try doing a global search inside that application for icon:, richTextIcon, or any variable like iconName. If search doesn’t reveal anything, open the interfaces one by one — the wrong icon reference will trigger the error when that interface loads.

  Once found, replace the invalid icon name with a valid one (as per Appian’s icon list), or add fallback logic to prevent invalid or null icon values.