Last night this was not an error. This morning my Appsmith was acting up, then it started working but several things I coded last night were throwing errors. This is the latest.
#select Widget setOptions is not a function. Just appeared.
untold stump
I'm not sure what the recommendations might be. I'm wanting to restart Appsmith, but that would probably disrupt the field personnel.
autumn quartzBOT
Hello, I'm SmithBot, your Appsmith support assistant. It sounds like you're
experiencing some instability or errors with your Appsmith instance after some
changes you made last night. Before recommending a restart, which could indeed
disrupt the field personnel, let's try to investigate the issue and see if it
can be resolved without downtime. Could you please describe the errors you're
encountering or share any relevant error messages? Also, let me know if there
have been changes to the environment or application that might correlate with
the issues you're facing. If you don't find my response helpful, you can request
to speak to a human agent
untold stump
I just sent a screenshot of one of the relevant errors. Take a look.
autumn quartzBOT
I'm sorry, but I cannot directly view images or screenshots. However, if you
could describe the error message or copy the text of the error here, I'll be
able to help you troubleshoot the issue. If the error message is in the logs or
somewhere you can copy from, that would be most helpful. If you don't find my
response helpful, you can request to speak to a human agent
untold stump
I worked through some issues I had within a JSObject that worked last night but failed to work this morning so I don't really have screenshots for that. It was weird though. It kept telling me I already had a function named to the the non-working function. I ended up copying the code, deleting the JS Object and creating a new JS Object.
Give me a minute to copy the Error message and the code that no longer works.
Error message: sel_FromCompany.setOptions is not a function
code that errors: sel_FromCompany.setOptions(null);
autumn quartzBOT
It appears that the error message is indicating that setOptions is not a
recognized function for the sel_FromCompany object. This might happen if the
object in question is not properly initialized or if the method does not exist
for the object type you are working with. In Appsmith, if sel_FromCompany is
supposed to be a widget (like a Select widget), then normally you would not call
setOptions on it directly in your code. Instead, you would update its options
by binding data to it from your application's state or a query. To resolve this,
you should ensure that you are interacting with your widgets and components in a
way that is aligned with the Appsmith platform's paradigms. For a Select widget,
you would typically bind the options by setting them in the widget's property
pane or by dynamically setting them through a query or API call. If you believe
sel_FromCompany should have this function based on your prior usage or
existing Appsmith documentation, please double-check the spelling,
capitalization, and that you are not trying to call this on a different kind of
object or due to some scope issues. If there was a recent update to Appsmith or
if you have changed any relevant code or configurations, it may also be
worthwhile to verify if any breaking changes occurred. Let me know if this
helps, or if there are other details or snippets you can provide that would help
me understand your setup better. If you don't find my response helpful, you can
request to speak to a human agent
untold stump
Thanks... I just quit trying to setOptions... we'll see if I need to again later.
autumn quartzBOT
@untold stump Is sel_FromCompany a query? It wouldn't have a
setOptions method. Can you elaborate on your use case and what you're trying to
accomplish?