Have you considered making each task an individual record instead of including tasks in a long text field?
Especially with the new List view, it should work quite well, and then you can have another table link to the tasks (records), roll them up, and run calculations.
I've built many task managers, and can't say I've ever used long text fields to track tasks. Just checkbox fields and individual records/nesting records.
+1 for what Joseph suggested
If operational requirements don't allow for it and you really need to use a long text field, try creating a formula field with this:
(
LEN(
{Tasks}
) -
LEN(
SUBSTITUTE(
{Tasks},
"[x]",
"[]"
)
)
)/
(
LEN(
{Tasks}
) -
LEN(
SUBSTITUTE(
{Tasks},
"[ ]",
"[]"
)
)
+
LEN(
{Tasks}
) -
LEN(
SUBSTITUTE(
{Tasks},
"[x]",
"[]"
)
)
)
+1 for what Joseph suggested
If operational requirements don't allow for it and you really need to use a long text field, try creating a formula field with this:
(
LEN(
{Tasks}
) -
LEN(
SUBSTITUTE(
{Tasks},
"[x]",
"[]"
)
)
)/
(
LEN(
{Tasks}
) -
LEN(
SUBSTITUTE(
{Tasks},
"[ ]",
"[]"
)
)
+
LEN(
{Tasks}
) -
LEN(
SUBSTITUTE(
{Tasks},
"[x]",
"[]"
)
)
)
OMG, that worked. Thank you so much! Thank you also Joseph. I will keep that in mind and may even try this for this project when I have more time. However, this worked for me to present to my team as an immediate resolution. Thanks everyone. This community is very helpful:)
