over 3.5 years ago and still nothing. also one of the top voted on ideas. this is the reason we are switching to flow and/or building apps our selves because we cant get a simple length function in a workflow.

I think Nintex has been already give up this product, as you can see this useful feature is "missing" over 3 years, and we cannot see what is the progress on it. Thanks Nintex, and GBY!

We are in the same boat. As a medium sized company we struggle with the cost of Nintex in O365 compared to on prem, as well as it's significant limitations without functions,not being able to code in a best practice way of multiple workflows without outrageous cost. Even migration with Sharegate forces us to basically rework most of the actions as they don't work online as configured on prem, we have been forced to go to Flow. For most of our basic functions flow is a free and more powerful alternative. I have been a user and Nintex consultant for over 10 years and gave the directive to convert all possible Nintex workflows to Flow as part of our SharePoint online migration. It is a shame.

Now starting to think about migrating/building workflows from on-prem to O365... but MISSING functions like this is a show stopper. Over to Flow we go...

Well???
How many votes do we need?! :-)

Hey there,
I would love to be able to use the "Power of" in a calculated field.

I can do this calculate formula, " =1.38*(([CL1 - mm]/1000)^2.5*60000)" in SharePoint however in Nintex I cannot use the Power of (^) in a formula in a Nintex calculated field.

a workflow without the ability to use inline functions is as useful as an ashtray on a motorcycle....

Please allow me to use inline functions in a workflow. I cannot convert a string to all upper case without using 26 regular expression actions. Before I could use fn-toupper() when building a string.

I can't do something as simple as converting a string to upper case! Without inline functions, I will have to write 26 regular expressions to accomplish the same thing. Why can't inline functions be used?

Why no comments from Nintex on this.. It's been over 2 years now... customers are desperate to have the features that already exist onPrem!

We just switched from on Prem and I built a small part of this huge workflow, using YYYY for the current date as part of a confirmation number after an item is created. Just spent two hours trying to figure out why my bit won't work and finally realize it's because it doesn't exist? This seems crazy.

Nintex it is ridiculous that this is not available in your workflow app BUT DOES EXIST IN YOUR FORMS

Needed very bad. How can this have been missed or overlooked?

This is needed!

needed too

This is badly needed! We can not build anything intuitive without those functions.

Come on Nintex, this is really essential part of workflow to be able to build strings.

I'm beginning to wonder if this is a deliberate act by Nintex, with workflows under 5 actions being 'free' without inline functions it is virtually impossible to do anything useful... therefore you have to work around the issues with multiple actions...

2.5 years ago I saw an update from the community manager saying watch this space...well??

If I'm reading the very uninformative help correctly, inline functions are only available in forms? Is that correct?
If so, come on Nintex, you can't expect people to migrate from onPrem with these feature, to Online where the useful/critical bits are missing.