Widget Binding Issues with 1.9.56

[sullen oyster]

Hi Support:

We are experiencing issues with Widget Binding not performing as expected. On a page event, the data binding is no longer accessible even thou it the API call was successful. Simple code inside an input widget {{some_other_input_widget.slice(6).toString || ""}}, will just return undefined, and log that the value is not a strong. We rolled back to 1.9.46 (our previous stable version) but now get this error message (see image) when trying to edit?

Any suggestions or am I going to have to restore a back-up image?

[full python]

Hello! I'm AppySmith, your support bot with an affinity for all things Appsmith.
Regarding the issue with widget binding, it's possible that the error might be
attributed to recent changes or updates to the platform or your codebase. If the
API call was successful, but the data binding is returning undefined for
widget properties that should be accessible, here are a couple of suggestions:

1. Verify the correctness of the widget name. Ensure that
   some_other_input_widget is the correct name of the other input widget from
   which you are trying to slice data. 2. Check if the property you're trying to
   access, slice, exists and is applicable for the data type of
   some_other_input_widget. It should be a string for slice to work. 3. Perhaps
   toString should be toString() if you are trying to convert a value to a
   string, but this method cannot be called on undefined. 4. Check for any
   changes in the Appsmith version between 1.9.46 and your current version that
   might affect widget binding or the availability of certain functions. 5. Look
   for error messages in the Appsmith editor or the browser console for any
   additional insight into what might be causing the binding to fail. Regarding the
   error message from the screenshot, since the screenshot is not directly
   accessible to me, I'd need the error message detailed text to analyze the issue
   further. If you have a detailed error message or log output, please provide it,
   as well as confirm if any changes were made prior to when the issue was first
   noticed. In case of complicated issues or if none of the suggestions help, you
   might consider a backup restoration as a last resort, but I'd recommend waiting
   for a more detailed analysis before taking that step. If there's any urgency or
   the problem persists, let me know and I can escalate this to a human team
   member. If you don't find my response helpful, you can request to speak to a
   human agent

[sullen oyster]

Can you please escalate this to support.

[full python]

Someone from our team will reach out to you on this thread. If you change your
mind, you can ask to speak to an AI agent at any time.

[sullen oyster]

Support - you can ignore this.... we had managed to change a function at the same time as this update and we where reseting the widget after the database call.