Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discard edits message not showing when I make a change in a record then without clicking update button select another record #970

Open
azizaparveen opened this issue Oct 18, 2024 · 12 comments
Assignees
Labels

Comments

@azizaparveen
Copy link
Collaborator

Describe the bug

Discard edits message not showing when I make a change in a record then without clicking update button select another record.
It is not showing the Discard edits message

Expected Behavior

It should show the discard edits message since we are getting away from the Editing state without committing the edit.

Reproduction Steps & Sample

Test app: https://solutions.mapsdevext.arcgis.com/apps/instant/manager/index.html?appid=fddd9b183ae14ffb9621b3fa51f852b8

  1. Launch the test app
  2. Select a record
  3. Click Edit button
  4. Make some changes
  5. Instead of clicking on Update, select another record (key step)

Other Relevant Info

No response

@azizaparveen azizaparveen added 1-BUG Something isn't working Manager component labels Oct 18, 2024
@azizaparveen azizaparveen added this to the 2024.R03 milestone Oct 18, 2024
@azizaparveen
Copy link
Collaborator Author

cc @sarahmcdonald7

@sarahmcdonald7
Copy link
Collaborator

@azizaparveen Just a heads up, I don't think this is a regression. I was able to reproduce this on production. We should show that discard edits message if the app leaves an open edit form.

@azizaparveen
Copy link
Collaborator Author

@sarahmcdonald7 you are right, it is not a regression. John is working on it.

@azizaparveen azizaparveen modified the milestones: 2024.R03, 2025.R01 Nov 5, 2024
@azizaparveen
Copy link
Collaborator Author

Pushing this next release @sarahmcdonald7 @jmhauck @skrishn

@jmhauck
Copy link
Collaborator

jmhauck commented Dec 16, 2024

@azizaparveen you will notice an issue when you are editing a feature and change layers and choose to continue editing. The layer selection in the layer picker is not showing the correct state. I will revisit this after the migration to calcite 3 is complete.

@azizaparveen
Copy link
Collaborator Author

@azizaparveen you will notice an issue when you are editing a feature and change layers and choose to continue editing. The layer selection in the layer picker is not showing the correct state. I will revisit this after the migration to calcite 3 is complete.

@john I can't repro this issue anymore

Image

@jmhauck
Copy link
Collaborator

jmhauck commented Feb 25, 2025

@azizaparveen your video is showing a new issue that we should fix in a patch. If you choose to continue editing the other layer should not be loading. Rather the layer the was initially loaded should still be loaded and the editor should remain active with any temp edits you have made. We have been using a method that was recommended by dev but I believe something in the editor has changed recently. I have followed up with dev about this but after some digging I see that we could potentially call another method that would trigger the expected behavior for this new issue.

@jmhauck
Copy link
Collaborator

jmhauck commented Feb 25, 2025

In regards to

@azizaparveen you will notice an issue when you are editing a feature and change layers and choose to continue editing. The layer selection in the layer picker is not showing the correct state. I will revisit this after the migration to calcite 3 is complete.

The problem is that the state of the layer picker shows both the layer that was initially selected and being edited as well as the other layer that was selected that caused the discard prompt to show are both shown as selected:

Image

@azizaparveen
Copy link
Collaborator Author

Sounds good @jmhauck , is it a small change, can we do it in Patch A?

@jmhauck
Copy link
Collaborator

jmhauck commented Feb 25, 2025

@azizaparveen yes...would like to get confirmation from dev before making the commit but we should be good for patch A I believe.

@sarahmcdonald7
Copy link
Collaborator

Sounds good @jmhauck , is it a small change, can we do it in Patch A?

@azizaparveen If this is going to be patched for A can you create an issue in the templates repo?

@azizaparveen
Copy link
Collaborator Author

Sounds good @jmhauck , is it a small change, can we do it in Patch A?

@azizaparveen If this is going to be patched for A can you create an issue in the templates repo?

Yes, will do it in a min.

@azizaparveen azizaparveen reopened this Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants