# Value processor for String-type data fields

**URL:** <https://community.appfarm.io/t/value-processor-for-string-type-data-fields/1615>\
**Category:** Feature requests\
**Created:** [January 31, 2025, 9:54am UTC](https://community.appfarm.io/t/value-processor-for-string-type-data-fields/1615 "2025-01-31T09:54:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![oyvind.byhring](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/oyvind.byhring/32/1060_2.png) [@oyvind.byhring](https://community.appfarm.io/u/oyvind.byhring)\
**Post date:** [January 31, 2025, 9:54am UTC](https://community.appfarm.io/t/value-processor-for-string-type-data-fields/1615/1 "2025-01-31T09:54:53Z")

</div>

Just a small request: I would love to have value processors for String values. Suggested scope for 1st version:

- Concatenate
- Replace
- Extract Substring
- Convert to upper/lowercase

This would make it much easier to create localized apps, as any string manipulation has to be done inside a function today. A simple example for when this is useful is when making labels e.g. “Order nr: 453187”. In this case I’d want to have the “Order nr” part as a string that can be localized, and then concat it first with “:” and then with a data bound property for the order number.

---

<div class="post-metadata">

**Author:** ![lbj](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/lbj/32/82_2.png) [@lbj](https://community.appfarm.io/u/lbj)\
**Post date:** [January 31, 2025, 10:21am UTC](https://community.appfarm.io/t/value-processor-for-string-type-data-fields/1615/2 "2025-01-31T10:21:31Z")

</div>

Agree. I had a similar request last year about allowing the use of %s string substitution.  
[Support for simple (%s) string substitution](https://community.appfarm.io/t/support-for-simple-s-string-substitution/1038)

---

<div class="post-metadata">

**Author:** ![emma](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/emma/32/1649_2.png) [@emma](https://community.appfarm.io/u/emma)\
**Post date:** [February 3, 2025, 8:02am UTC](https://community.appfarm.io/t/value-processor-for-string-type-data-fields/1615/3 "2025-02-03T08:02:07Z")

</div>

Thank you for your input! This is something we have on our roadmap:)

---

<div class="post-metadata">

**Author:** ![lbj](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/lbj/32/82_2.png) [@lbj](https://community.appfarm.io/u/lbj)\
**Post date:** [September 12, 2025, 11:40am UTC](https://community.appfarm.io/t/value-processor-for-string-type-data-fields/1615/4 "2025-09-12T11:40:33Z")

</div>

Hi, any updates on this?

If not, I’d really suggest adding **localization** as a dedicated feature in the function editor. Without it, the text becomes impersonal. For example, I’d prefer to write:

`Assign %s to one or more roles in projects`  
so it becomes:  
`Assign John to one or more roles in projects`

Instead of being stuck with just the static version. `Assign the user to one or more roles in projects`

Breaking sentences into substrings doesn’t really work either, since different languages may use completely different structures. That makes translating isolated strings very hard without full context.

String substitution is a very basic feature in most programming languages, so it feels like it should be supported here too.

---

<div class="post-metadata">

**Author:** ![emma](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/emma/32/1649_2.png) [@emma](https://community.appfarm.io/u/emma)\
**Post date:** [September 12, 2025, 12:35pm UTC](https://community.appfarm.io/t/value-processor-for-string-type-data-fields/1615/5 "2025-09-12T12:35:57Z")

</div>

Hi!

Thanks for following up on this and the good suggestion. I don’t have a specific date I can share right now, but we will let you know when it is ready!