Hi Joanne,
are you testing in preview mode? This is the same behaviour for task outcomes in task forms. While being in preview mode, evaluating the outcome field will always result in -1. Haven't worked with mobile forms yet, but I think that could be the problem.
Cheers
Philipp
oh aha! I'll check that out.
I also have this issue when using O365. Maybe this runtime function has issues on mobile. I'll contact support.
Hey - did you ever get a response from support on this?
Yes, at the time, currentRowNumber was not supported in the mobile app. There have been general bug fixes in the last two versions. I could followup.
In testing, I no longer get -1, but no number at all.
I'm getting a different outcome from your most recent test, Andrew. I'm getting -1 for every currentrownumber() in mobile, still.
Has this been logged as a bug?
This function is actually listed in their not supported list for mobile. So it wouldn't be a bug, just a feature not available that we need really bad!
Oh heck! Yes, definitely need this one badly.
Hoping this has been fixed? Will update Nintex servers soon and keep fingers crossed. Multiple mobile specific forms waiting on this unless there is a simple workaround i'm missing with repeating sections on mobile..