# UFM fallback values

**URL:** <https://forum.umbraco.com/t/ufm-fallback-values/7678>\
**Category:** Questions\
**Tags:** extending, v17\
**Created:** [March 12, 2026, 5:02pm UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678 "2026-03-12T17:02:38Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![mayhemcreates](https://forum.umbraco.com/user_avatar/forum.umbraco.com/mayhemcreates/32/5072_2.png) [@mayhemcreates](https://forum.umbraco.com/u/mayhemcreates)\
**Post date:** [March 12, 2026, 5:02pm UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/1 "2026-03-12T17:02:38Z")

</div>

Hello, first-time poster here hoping I can pick some of your big brains.

I have just updated my project from v13 to v17, and need to update the labels for my block list items from angular to UFM. I am wanting to render the heading property in the label, however where this is a non-mandatory field I need a fallback to another property, which in my current case has the alias bodyCopy.

The docs show that a fallback filter exists, which is great, however I CAN’T FOR THE LIFE OF ME work out what kind of data it will accept? I’ve referred to the docs, the forums and [Joe Glombek’s super useful](https://24days.in/umbraco-cms/2025/template-for-success/) blog (this particular issue aside…) , and have tried a variety of values as follows:

Just the alias name:

`#ImageAndContentComponent_${ $index } - ${umbValue: heading | fallback: bodyCopy }`

Alias name as js expression:

`#ImageAndContentComponent\_${ $index } - ${umbValue: heading | fallback: ${ bodyCopy } }`

Alias name as a umbValue (with ref to [Trying to be clever with UFM fallbacks](https://forum.umbraco.com/t/trying-to-be-clever-with-ufm-fallbacks/4533) ):

`#ImageAndContentComponent\_${ $index } - ${umbValue: heading | fallback: {umbValue: bodyCopy} }`

I then gave up with the fallback filter and tried a js expression (again going off Søren’s responses, I’m guessing is a relatively new feature) :  
`#ImageAndContentComponent_${ $index } - ${ heading.length > 0 ? heading : bodyCopy }`

All to no avail. I’m hoping someone is going to tell me I’m doing something really stoopid, and I can get this working in no time, but any thoughts / suggestions would be much appreciated! 🫶

p.s. I will be extra happy if you tell me I don’t have to create my own filter.

---

<div class="post-metadata">

**Author:** ![mistyn8](https://forum.umbraco.com/user_avatar/forum.umbraco.com/mistyn8/32/671_2.png) [@mistyn8](https://forum.umbraco.com/u/mistyn8)\
**Post date:** [March 12, 2026, 6:03pm UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/2 "2026-03-12T18:03:41Z")

</div>

(umb 17.2.2)  
I did get it to work in a collection view… (with ufm and not ufm expression though)

 ![image](https://forum.umbraco.com/uploads/default/original/2X/a/ac8a37a922cec2536bfaaf6a496fdc799a80662f.png)  
 ![image](https://forum.umbraco.com/uploads/default/original/2X/1/1a218091b2e862b89795fd864b16eea9f1aa6699.png)

I wonder if it’s that the fallback filter is only available on ufm and not ufm expressions?

for ufm expressions.  
`${ value.length > 0 ? value : "N/A" }`

works.. but can’t seem to have it fallback to another property like you are after.

---

<div class="post-metadata">

**Author:** ![mistyn8](https://forum.umbraco.com/user_avatar/forum.umbraco.com/mistyn8/32/671_2.png) [@mistyn8](https://forum.umbraco.com/u/mistyn8)\
**Post date:** [March 12, 2026, 6:19pm UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/3 "2026-03-12T18:19:15Z")

</div>

So with blocks…  
again with ufm.. not expresssions- fallback to text working  
but again only if a constant string and not another property

 ![image](https://forum.umbraco.com/uploads/default/original/2X/e/e953bd149ddc014689412e16a5b9e6ce32fe29f0.png)  
 ![image](https://forum.umbraco.com/uploads/default/original/2X/b/b6b427b602e9a27fe9ca29b7e46c38bc29a4674d.png)

Seems to work with expressions though..

 ![image](https://forum.umbraco.com/uploads/default/original/2X/1/1ea012625fcbe66568358d98d175f1d29236fd64.png)  
 ![image](https://forum.umbraco.com/uploads/default/original/2X/b/b096e8c0e99b30911df59f45825837b87ebee8db.png)  
 ![image](https://forum.umbraco.com/uploads/default/original/2X/e/ee85b5ecb1a58fc06bca8777cd2b15201155fff2.png)

---

<div class="post-metadata">

**Author:** ![mayhemcreates](https://forum.umbraco.com/user_avatar/forum.umbraco.com/mayhemcreates/32/5072_2.png) [@mayhemcreates](https://forum.umbraco.com/u/mayhemcreates)\
**Post date:** [March 13, 2026, 9:29am UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/4 "2026-03-13T09:29:37Z")

</div>

Thanks so much for looking into this for me @mistyn8! Interesting that you were able to return a property using the expression, I’ll have another play and see if I was doing something silly.

Would defo be useful for the fallback filter to accept doctype properties, but from talking to my colleague @OwainWilliams it sounds like it might not be a priority at the mo.

Thanks again!

---

<div class="post-metadata">

**Author:** ![OwainWilliams](https://forum.umbraco.com/user_avatar/forum.umbraco.com/owainwilliams/32/4540_2.png) [@OwainWilliams](https://forum.umbraco.com/u/OwainWilliams)\
**Post date:** [March 13, 2026, 10:47am UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/5 "2026-03-13T10:47:11Z")

</div>

Seems like I’m also now running to similar issues and limitations or maybe even a bug.

Trying to get the value of a MemberPicker and no matter what I try, I always just get the member key e.g.

**umbValue:** {umbValue:person} - person is the alias of the MemberPicker

 ![image](https://forum.umbraco.com/uploads/default/original/2X/4/49fe0645b360a0a85472b348381133ba7e42922a.png)

I thought maybe {umbValue.person.firstName} or {umbValue.person.name} might work but it doesnt.

According to the docs {umbContentName:person} should work with Memberpickers

"Content Name

The Content Name component will render the name of a content item, (either Document, Media or Member), from the value of a given property alias. Multiple values will render the names as a comma-separated list.

**The alias prefix is `umbContentName`. An example of the syntax is `{umbContentName: pickerAlias}`, which would render the component as `<ufm-content-name alias="pickerAlias"></ufm-content-name>`.**

The Content Name component supports content-based pickers, such as the Document Picker, Content Picker (formerly known as Multinode Treepicker), and **Member Picker**. Support for the advanced Media Picker will be available in an upcoming Umbraco release."

But I don’t even get a value back when I do use {umbContentName:person}

Frustrating to say the least.

---

<div class="post-metadata">

**Author:** ![mistyn8](https://forum.umbraco.com/user_avatar/forum.umbraco.com/mistyn8/32/671_2.png) [@mistyn8](https://forum.umbraco.com/u/mistyn8)\
**Post date:** [March 13, 2026, 12:47pm UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/6 "2026-03-13T12:47:15Z")

</div>

sounds like it’s failing to find the correct entity type.. and falling back to the default which is document..

```auto
	#getRepository(entityType?: string | null) {
		switch (entityType) {
			case UMB_MEDIA_ENTITY_TYPE:
				if (!this.#mediaRepository) this.#mediaRepository = new UmbMediaItemRepository(this);
				return this.#mediaRepository;

			case UMB_MEMBER_ENTITY_TYPE:
				if (!this.#memberRepository) this.#memberRepository = new UmbMemberItemRepository(this);
				return this.#memberRepository;

			case UMB_DOCUMENT_ENTITY_TYPE:
			default:
				if (!this.#documentRepository) this.#documentRepository = new UmbDocumentItemRepository(this);
				return this.#documentRepository;
		}
	}
}

```

` **Member** {umbValue:member} {umbContentName:member} **Content** {umbValue:content} {umbContentName:content} **Media** {umbValue:media} {umbContentName:media}`

resolves for content and media, but not member..

 ![image](https://forum.umbraco.com/uploads/default/original/2X/e/e0c35d75c91d23d4be2f75dab4e01a90b3824e3b.png)

---

<div class="post-metadata">

**Author:** ![mistyn8](https://forum.umbraco.com/user_avatar/forum.umbraco.com/mistyn8/32/671_2.png) [@mistyn8](https://forum.umbraco.com/u/mistyn8)\
**Post date:** [March 13, 2026, 1:08pm UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/7 "2026-03-13T13:08:23Z")

</div>

yep entityType is resolved as `document` for the `member guid`.

 ![image](https://forum.umbraco.com/uploads/default/original/2X/b/bcfdfe02a2e498b48863b09cdfdcdb7a71620e81.png)

Works for media as we get an object..

 ![image](https://forum.umbraco.com/uploads/default/original/2X/5/51274c8ed62421399183d822efd00a5d1fc0392c.png)

but can’t possible distinguish between document and member.. as it’s just a plain guid.

Prob needs to do a we didn’t find the guid in member repository, so now default to documentrepository ??

---

<div class="post-metadata">

**Author:** ![OwainWilliams](https://forum.umbraco.com/user_avatar/forum.umbraco.com/owainwilliams/32/4540_2.png) [@OwainWilliams](https://forum.umbraco.com/u/OwainWilliams)\
**Post date:** [March 13, 2026, 1:19pm UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/8 "2026-03-13T13:19:48Z")

</div>

Loving seeing your working and thought process on this Mike. Thanks for the details - never thought about firing up DevTools and digging around that to hit breakpoints etc.

I’m currently looking at a custom extension to try and get member details that way. If I get it working I’ll share a link to the code.

---

<div class="post-metadata">

**Author:** ![mistyn8](https://forum.umbraco.com/user_avatar/forum.umbraco.com/mistyn8/32/671_2.png) [@mistyn8](https://forum.umbraco.com/u/mistyn8)\
**Post date:** [March 13, 2026, 1:29pm UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/9 "2026-03-13T13:29:34Z")

</div>

ps you can get at the compiled js to play in situe too.. (rather than just dev tools)

from the project folder

```auto
dotnet publish --configuration Release --output ../../PublishedSite
cd .\..\..\publishedSite
dotnet www.dll --urls=https://localhost:44315/ --configuration Release --environment Development

```

gets you a running site at [https://localhost:44315/](https://localhost:44315/)

and  
`PublishedSite\wwwroot\umbraco\backoffice\packages\ufm\content-name.component-CZi6jNIr.js`

---

<div class="post-metadata">

**Author:** ![glombek](https://forum.umbraco.com/user_avatar/forum.umbraco.com/glombek/32/2089_2.png) [@glombek](https://forum.umbraco.com/u/glombek)\
**Post date:** [March 13, 2026, 6:34pm UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/10 "2026-03-13T18:34:46Z")

</div>

[All filters that take parameters currently only work with components, not expressions.](https://github.com/umbraco/Umbraco-CMS/issues/20744) Unfortunately I believe this one is causing some headaches to solve!

---

<div class="post-metadata">

**Author:** ![glombek](https://forum.umbraco.com/user_avatar/forum.umbraco.com/glombek/32/2089_2.png) [@glombek](https://forum.umbraco.com/u/glombek)\
**Post date:** [March 13, 2026, 6:38pm UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/11 "2026-03-13T18:38:07Z")

</div>

This looks like a bug at the moment, so worth raising an issue and/or getting a PR in. Generally HQ have been quick at fixing these oversights!

What I suspect won’t be a part of core (yet) is rendering properties from a picked member other than name. So if you need to do that, a [custom UFM Component](https://24days.in/umbraco-cms/2025/template-for-success/) would be the way to go!

---

<div class="post-metadata">

**Author:** ![OwainWilliams](https://forum.umbraco.com/user_avatar/forum.umbraco.com/owainwilliams/32/4540_2.png) [@OwainWilliams](https://forum.umbraco.com/u/OwainWilliams)\
**Post date:** [March 16, 2026, 3:28pm UTC](https://forum.umbraco.com/t/ufm-fallback-values/7678/12 "2026-03-16T15:28:04Z")

</div>

So went down the custom UFM component and made it a package

> **[GitHub - OwainWilliams/OC.UFMMemberLookup: An Umbraco Flavoured Markdown Extension for Member...](https://github.com/OwainWilliams/OC.UFMMemberLookup)**
>
> An Umbraco Flavoured Markdown Extension for Member lookup

Sent it to the marketplace but still waiting for that to load.

This does the Member lookup which I couldnt get to work in Core. I’ll see if I can make a PR in to Core too but this was needed for a client. 🙂

O.
