Local variables in form segments are no longer accessible

I have a Form Segment with some local variables. I have a button on that form segment that will assign some values to those variables. That was fine in 9.0.1 In 9.0.2, validation blows up (although deployment does not, oddly), and the 'Local' variables are no longer accessible, and just throw an exception when I try to set or access them.

We have seen there have been a few changes to the way form segments work, focing renaming of form segment fields to avoid clashes, for example. This fault is making a great many form segments fail now, however.

Is this recognised yet, and if so, is a fix due?

Find more posts tagged with

BPM

Comments

Jerome_Pearce

No feedback on this one? Seems like a pretty serious fault IMO.

Rob Vignerot

Jerome,

I'm not aware of any issues with this. Have you raised this with Customer Support?

Rob

Jerome_Pearce

I've been trying to crack this all day, and have just isolated it. It was in fact that a date field in a grid accessed with UserInput causes a 'object not available' error.

I had to make it all on a normal form before the segment was proved not to be an issue.

Still a massive pain, but I can ignore it for now.

Lee Lee

Jerome

Just ran into this issue too. How did you resolve?

Jerome_Pearce

commenting out that line of code!

No resolution, sorry.

Jerome_Pearce

Just to explain why we though the issue was regarding local variables: Because the Validation tells us that 'Local' does not exist when this form segment is used on a form.

So the real fault that caused this is that you cannot access a date field form a selected row in a grid.

The other issue is that the validation bombs (but deployment works) when you have Local variables in a form segment and use that form segment on a form.