Dropdown Option Change Fails in Deployment Mode, Works Perfectly in Production

[static gulch]

I am using Appsmith version 1.58 (self-hosted). I have a dropdown menu where customer names are listed as labels and their IDs as values. On onOptionChange, I expect the value of Selected_Kunde_List.selectedOptionValue to be stored in a store variable named selectedKunde.

While this works fine in the production window, it doesn't function as expected in the deployment mode.

Steps to Reproduce:

Use a dropdown menu in Appsmith.
Set the label to customer names and value to customer IDs.
Use onOptionChange to store Selected_Kunde_List.selectedOptionValue in the selectedKunde store.
Observe that it works in production mode, but does not work in deployment mode.
Expected Behavior:

The value of Selected_Kunde_List.selectedOptionValue should be stored in the selectedKunde store variable in both production and deployment modes.

Actual Behavior:

It works in production mode but fails in deployment mode.

Version: 1.58 (self-hosted)

[proud sluice]

Hello! I'm AppsmithBot, here to assist you with your Appsmith queries.

It seems like you're experiencing an issue with the storeValue function not working as expected in deployment mode. This could be related to how the storeValue function is being used or a potential bug in the deployment setup.

Here are a few steps you can try to troubleshoot and resolve the issue:

1. Check the storeValue Function: Ensure that the storeValue function is correctly implemented in the onOptionChange event of your dropdown. It should look something like this:

storeValue('selectedKunde', Selected_Kunde_List.selectedOptionValue);

2. Verify Deployment Configuration: Make sure that your deployment environment is correctly configured and that there are no discrepancies between your production and deployment setups. This includes checking environment variables and ensuring that all necessary ports are open?5:0?Appsmith Documentation.md?.

3. Inspect Browser Console for Errors: Open the browser's developer tools and check the console for any errors or warnings that might give more insight into what's going wrong during deployment.

4. Check for Known Issues: There might be known issues with the version you are using. You can check the Appsmith GitHub repository for any reported issues related to storeValue or deployment mode?5:10?email-support1.json?.

5. Logs and Support: If the issue persists, consider checking the server logs for any errors that might be occurring during deployment. You can also reach out to Appsmith support for further assistance?5:0?Appsmith Documentation.md?.

If these steps do not resolve the issue, please let me know, and I can assist you further!

If you don't find my response helpful, you can request to speak to a human agent.

[static gulch]

Production environment:

[proud sluice]

It seems like you're facing an issue with the storeValue function not working in deployment mode. Here are some additional steps you can take to troubleshoot this issue:

1. Ensure Correct Event Binding: Double-check that the onOptionChange event is correctly bound to the dropdown widget. Sometimes, re-binding the event can resolve issues.

2. Check for JavaScript Errors: Make sure there are no JavaScript errors in your code that might be preventing the storeValue function from executing. You can do this by checking the browser console for any errors.

3. Test with Console Logs: Add a console.log statement before and after the storeValue function to ensure that the function is being called and to check the value being stored:

console.log("Selected Value: ", Selected_Kunde_List.selectedOptionValue);
storeValue('selectedKunde', Selected_Kunde_List.selectedOptionValue);
console.log("Value stored in selectedKunde");

4. Review Deployment Logs: Check the deployment logs for any errors or warnings that might indicate why the storeValue function is not working as expected.

5. Update Appsmith Version: If possible, consider updating to a newer version of Appsmith, as the issue might have been resolved in a later release.

If none of these steps resolve the issue, it might be a specific bug with the version you are using. In that case, reaching out to Appsmith support with detailed logs and steps to reproduce the issue would be the best course of action.

If you don't find my response helpful, you can request to speak to a human agent.

[static gulch]

Could you please provide a human agent this problems is caused by appsmith system and the system cant correct it self.

[proud sluice]

Someone from our team will reach out to you on this thread. In the meantime, you can have a look at our documentation to try & resolve your query https://docs.appsmith.com?utm=bot

[proud sluice]

Hello! Please share a loom.com screen recording showing the exact steps you take and the behavior in edit vs deployed mode.

[static gulch]

https://www.loom.com/share/5bd993717c1b4a0fa857df6edc855917?sid=753594cf-bd01-47cc-8fb5-42223faf6bc2

[proud sluice]

Hey @static gulch,

This behavior is working as expected for me on the latest version. Can you try updating to 1.59 and let me know if this issue still persists? If so we may need to take a closer look at your app to debug this.

[static gulch]

Update was successful **but **the issue still remains

[static gulch]

After experimenting a bit, I found out that the dropdown works fine in deployed mode when it's outside the list. But i need it inside the List Widget what can i do?