Why is the result of this bool transform not replacing the current value? The output is of the transform is false, yet the current value is true. The variable is used for the conditional rendering of a button.
1 Like
I attempted to reproduce the error, but unfortunately am getting the intended interaction out of the transform. Any chance you could try changing “ALL” to “ANY” to test the interaction changing? Alternatively change your “Is not” to “Is”? This is just to see that as the state changes the variable output is changing as well to further test the issue.
As an initial troubleshooting step that typically solves 80% of my problems, I personally always save my work and refresh the page as sometimes it could be a local issue.
The Bennie Response variable is set to refresh only when triggered by an event. The boolean var in questions is set to refresh automatically. Could that be the issue? IE because my expression is using a variable that is only recalculated based on event I also have to recalculate this var manually? I would not expect that behavior but maybe it will help you reproduce.
1 Like
Yes, absolutely! That’s super helpful, thank you.
I’m able to reproduce it now, but this seems like the workflow is now working as intended. The definition should continue to update as you continue making changes in the logic, where the output value will remain static until variables are updated. This is because the input variable is event based updating for the value, impacting the output but not the logic. Hopefully that explanation makes sense.
For my reproduction testing, as I toggled between automatically updating, and event based updating, the value updated immediately. Give that a try and let me know if you’re seeing the same thing!
This doesn’t make a lot of sense to me. Can you elaborate more with a screenshot or a video? From a developer’s perspective, this is 100% a platform defect. Automatic update should continue to update the variable value when the referenced variable value changes, even if that variable value is recalculated manually via an event. The expectation is that an automatic update will implement observers to detect changes in the referenced variables and recalculate when those values change, regardless of how that value was derived.
Absolutely! I should have started with screenshots.
So what I’m talking about is in relation to your event based variable update. The definition, indicated in the screenshot below with the red rectangle with the number 1, functions independently of the output, indicated in the screenshot below with the red 2. Because you have an upstream dependency (in this case the Bennie Response Variable) that is triggered by an event, you would need to trigger the event in order for the downstream automatic update to take effect. This is because each variable functions independently, and “Bennie Response” only functions as a reference to an event based updating variable in your automatically updating transform downstream.
In the second image below, you’ll see that changing the variable to automatically update will allow me to see the changes at the output to show the proof of concept in the test.
Stated differently, the area in the screenshot below marked “1” is for your development to construct a transform. The area marked with a “2” is just the output. 1 will continue to be fluid because this is your development window for constructing the variable transformation, 2 will be dependent on the values and show the current state, based off conditions in your module, of the transform with the configuration.
