on 01-03-2024 10:48 AM
Bug Detected in Adobe Livecycle. Logic behaves in a weird way when excecuted in Event Calculate instead of other Events like Intialize or Validate.
I need to execute logic after intialize since I need to access a value which doesn't exist yet. When using the Events to solve this, i ecountered a bug.
Let's take a look:
say you create a subform containing 2 fields
We add this logic to Textfield 1
Now this works completely as intended, same if you would use the event Validate(this is what i currently do, so i can still get my logic working but yeah it took me a while to figure it put,so why not reduce the pain of debugging for future devs)
Now what happens when we use that logic on the Event Calculate
What? Exactly!
Now lets do something even Crazier:
We all Agree that both fields should have the value 2311 right? And the code inside the condition shouldnt be excecuted
Apparently not.
Adobe LiveCycle Designer Version: 11.0.9.20220218.1.3.0
I struggled a bit trying to fix this and checked multiple times, debugged my whole huge Form to find some sort of logic of mine that could've caused it but no. After i reproduced this issue in an otherwise empty form (as seen in the screenshots) I was certain that this seems to be an issue with adobe livecycle designer.
Since it isnt hindering me from any work any more than it already did ( since i found a workaround) i didn't create a Ticket. But maybe just maybe this will be fixed sometime in the future?
Cheers and a Happy New Year
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.