A Quick Prelude
This morning, I was blankly staring past my monitors in a strange state of disassociation.
On my screen was the commit history of a substantial git repo.
While clearing out stale branches, I went down the rabbit hole of examining eac...
This pain point resonates with me.While it doesn't do anything to resolve issues with collaboration at scale, know that plenty of us that manage and work with a large number of Interfaces at scale also face similar problems when it comes to Interface...
Ouch. That's rough. If I had to nominate a field to indiscriminately eject from databases and data structures, it would be multiple select fields. In 99% of use cases that have a multiple select field implemented, the better choice would have actuall...
Instead of a formula field, you need to create a rollup field.If you use the rollup field, you can just copy and paste the exact formula I posted; you won't have to change it at all.Here are some screenshots for additional context: After saving the ...
Hey @LeighAnnMoltz! Based on the information you provided, I put together the following example: To do this, I implemented a rollup field with the following formula:IF(
values,
IF(
COUNTALL(values) = 1,
"• " & TRIM("" & values...
Here you go:IF(
{Current due after credits} < 0,
"Your Desired Return Value",
IF(
{Current due after credits} = 0,
"NO CURRENT DUE",
IF(
{Current due after credits} > 0,
"CREATE REMIT"
...
