Return "no-entity" from a formula

I’d like to create a formula that links a field from an Outcome to a Proposal through a Project.
[Outcome] One ↔ One [Project] One ↔ Many [Proposals]
This is relatively simple: I can create a formula inside of Proposals

Project.Outcome.[Over vs Under Resourced]

However, I’d only like this information to bubble through to the proposal if the proposal was the one that was approved.

In this case, I’d like to use something like

If(Proposal.Status.Name="Approved", Project.Outcome.[Over vs Under Resourced], *Blank*)

However, I’m not sure what I can do to return nothing. [Over vs Under Resourced] is a single-select entity (and I’d like to return the whole entity, rather than the name for UI purposes), but something like “” doesn’t work, because it is string-typed.

Is there a way to return a blank that shares a type with [Over vs Under Resourced]?

Thank you!

It’s an interesting use case.
I don’t think it’s possible with formulate.
However, you can kinda hack it.

  1. Use text field instead of formula.
  2. Create rule for update of status.
  3. Filter to only approved
  4. On Update of Status to Approved set the text field “[Over vs Under Resourced]” using formula
Project.Outcome.[Over vs Under Resourced]

If you want to clear it you would need another rule:
2. Create rule for update of status.
3. Filter to NOT approved
4. Update “[Over vs Under Resourced]” using “Clear field value”

This has been requested before!
There is an ugly way to hack it, which is to filter for an entity that will never be found:

Project.Outcome.Filter(Name = "!LOL!").Sort().First()

2 Likes

That is brilliant but alas it doesn’t seem to like it:

Perhaps you cannot filter on a one-to-one relation?

If you want to return a specific field like [Client Temperature] from the Formula, you must add that field to the bogus search result as well, because all potential (conditional) Formula results must return the same data type:

Project.Outcome.Filter(Name = “!LOL!”).Sort().First().[Client Temperature]

It seems it’s the filter method itself it has a problem with

Yep, you can’t filter on a to-one relation.
AFAIK there’s no easy way to do this using field formulas only :disappointed:

Some day :roll_eyes:

Related:

2 Likes