AppFlowy-IO/AppFlowy

Fork 0

mirror of https://github.com/AppFlowy-IO/AppFlowy.git synced 2026-03-24 04:46:56 +00:00

[GH-ISSUE #7545] [Bug] Updating field type destroy database entries without option to undo #3352

New issue

Closed

opened 2026-03-23 21:29:31 +00:00 by mirror · 6 comments

mirror commented

2026-03-23 21:29:31 +00:00

Owner

Originally created by @SoFMeRight on GitHub (Mar 14, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7545

Describe the bug
Selecting a field like Taskslist and toggling it to a different field type immediately destroys all database entries without any potential for undo.

To Reproduce

Expected behavior
I'd expect to be able to do an undo, or that if I put it back to the checklist option I would see the same data I'd entered before. Or Id expect the application would have incremental backups every soo many minutes with snapshots or... something?! I got really lucky and the moment I realized what had happened with things I actually wasn't keeping other logs of I cut mobile data and wifi to my phone and made a copy of the data then and there otherwise id have lost all of the sub-tasks 🤣

I think the best thing that could be patched here in the meantime is ASAP if I were the dev I would put a transitional warning pop-up that asks the user if they wish to continue as it will be destroying data. Otherwise I was able to quickly destroy a ton of data in one swoop and in a collaborative setting thats a really risky business to be that easy to accidentally break everything 🤣 Will I do this again? No! Can it be avoided? Yes! Is it a good feature? No, I think this should be resolved in some way as a priority item but thats just me.

Desktop (please complete the following information):

OS: Windows 11 all of the recent updates as of 10:13 AM PST 03/14/2025 I have it set to download all updates ASAP including feature updates.
Desktop client. The latest as of yesterday.

I am pretty sure this is the standard operation of this app.

Originally created by @SoFMeRight on GitHub (Mar 14, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7545 **Describe the bug** Selecting a field like Taskslist and toggling it to a different field type immediately destroys all database entries without any potential for undo. **To Reproduce** ![Image](https://github.com/user-attachments/assets/bed14a49-85f9-4d14-838f-c3a431fa3c59) ![Image](https://github.com/user-attachments/assets/8f912854-74d4-497c-85c4-393cf321f91d) ![Image](https://github.com/user-attachments/assets/6fb41143-fd9e-424d-8cb6-24f2ffcecb98) **Expected behavior** I'd expect to be able to do an undo, or that if I put it back to the checklist option I would see the same data I'd entered before. Or Id expect the application would have incremental backups every soo many minutes with snapshots or... something?! I got really lucky and the moment I realized what had happened with things I actually wasn't keeping other logs of I cut mobile data and wifi to my phone and made a copy of the data then and there otherwise id have lost all of the sub-tasks 🤣 I think the best thing that could be patched here in the meantime is ASAP if I were the dev I would put a transitional warning pop-up that asks the user if they wish to continue as it will be destroying data. Otherwise I was able to quickly destroy a ton of data in one swoop and in a collaborative setting thats a really risky business to be that easy to *accidentally* break everything 🤣 Will I do this again? No! Can it be avoided? Yes! Is it a good feature? No, I think this should be resolved in some way as a priority item but thats just me. **Desktop (please complete the following information):** - OS: Windows 11 all of the recent updates as of 10:13 AM PST 03/14/2025 I have it set to download all updates ASAP including feature updates. - Desktop client. The latest as of yesterday. I am pretty sure this is the standard operation of this app.

mirror

2026-03-23 21:29:31 +00:00

closed this issue
added the
Q3 25

2025

database

bug
labels

mirror commented

2026-03-23 21:29:32 +00:00

Author

Owner

@khorshuheng commented on GitHub (Mar 17, 2025):

Not all field types operation results in corruption of the database entries - for eg. it is possible to change Select to Multi select , or Text . Which field type conversion did you perform? We will see if the data corruption is indeed expected, or if it is a result of some previously undiscovered bug. If it is expected, we can put up a warning message before performing similar operations, or just forbid it altogether.

We support undo operation, but not for field type operations at the moment. We know that it is possible to do so in Notion, and will check how we can do the same.

@khorshuheng commented on GitHub (Mar 17, 2025): Not all field types operation results in corruption of the database entries - for eg. it is possible to change `Select` to `Multi select` , or `Text` . Which field type conversion did you perform? We will see if the data corruption is indeed expected, or if it is a result of some previously undiscovered bug. If it is expected, we can put up a warning message before performing similar operations, or just forbid it altogether. We support undo operation, but not for field type operations at the moment. We know that it is possible to do so in Notion, and will check how we can do the same.

mirror commented

2026-03-23 21:29:32 +00:00

Author

Owner

@richardshiue commented on GitHub (Mar 17, 2025):

Reproducible steps:

Create a checklist field. In a row, enter some options into it.
Turn that field into text
Turn that field into single select option
See that we mistakenly attempt to convert the data to an option

@richardshiue commented on GitHub (Mar 17, 2025): Reproducible steps: 1. Create a checklist field. In a row, enter some options into it. 2. Turn that field into text 3. Turn that field into single select option 4. See that we mistakenly attempt to convert the data to an option

mirror commented

2026-03-23 21:29:32 +00:00

Author

Owner

@SoFMeRight commented on GitHub (Mar 17, 2025):

So basically what I did is clicked into a Kanban board item in the
"appflowy Default To-dos" and then clicked the menu to change the "Task"
field from a check list to any other type it resulted in any of the entries
under the check lists being lost and there was no warning other than
perhaps I can understand why this would lose data but also I think it's a
best practice to treat users like they are stupid and still put some kind
of protective barrier between this action.

TLDR: I originally noticed this via email reply and missed the response from @richardshiue that is 100% accurate as to what I observed. I'd love to see this one fixed. I honestly found for now the solution to either be mindful of this or break things up into individual bits so that cant happen even if i wanted to lol. I'm honestly so addicted to the way this thing is built in the few days of trying it even if I lost all of the stuff I did in it, I'd still have kept using it after the last tear was shed 🤣

I actually wanna say thanks for this project. I've enjoyed AppFlowy a shton, I gave it a glance a week or so ago and decided on the spot to deployed appflowy cloud from the overview! And I am glad I did. Its quite the uncommon experience to have software that is not only functional and extremely useful to core/critical everyday tasks but also an absolute joy to use! :D Super thankful for this project!

On Sun, Mar 16, 2025, 8:21 PM Richard Shiue @.***>
wrote:

Reproducible steps:

Create a checklist field. In a row, enter some options into it.

Turn that field into text

Turn that field into single select option

See that we mistakenly attempt to convert the data to an option

—
Reply to this email directly, view it on GitHub
https://github.com/AppFlowy-IO/AppFlowy/issues/7545#issuecomment-2727955867,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH2UFZKSAXESZQGUHQ3VITL2UY5UNAVCNFSM6AAAAABZCTAS2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXHE2TKOBWG4
.
You are receiving this because you authored the thread.Message ID:
@.***>
[image: richardshiue]richardshiue left a comment
(AppFlowy-IO/AppFlowy#7545)
https://github.com/AppFlowy-IO/AppFlowy/issues/7545#issuecomment-2727955867

Reproducible steps:

Create a checklist field. In a row, enter some options into it.

Turn that field into text

Turn that field into single select option

See that we mistakenly attempt to convert the data to an option

—
Reply to this email directly, view it on GitHub
https://github.com/AppFlowy-IO/AppFlowy/issues/7545#issuecomment-2727955867,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH2UFZKSAXESZQGUHQ3VITL2UY5UNAVCNFSM6AAAAABZCTAS2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXHE2TKOBWG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

@SoFMeRight commented on GitHub (Mar 17, 2025): ~~So basically what I did is clicked into a Kanban board item in the "appflowy Default To-dos" and then clicked the menu to change the "Task" field from a check list to any other type it resulted in any of the entries under the check lists being lost and there was no warning other than perhaps I can understand why this would lose data but also I think it's a best practice to treat users like they are stupid and still put some kind of protective barrier between this action.~~ TLDR: I originally noticed this via email reply and missed the response from @richardshiue that is 100% accurate as to what I observed. I'd love to see this one fixed. I honestly found for now the solution to either be mindful of this or break things up into individual bits so that cant happen even if i wanted to lol. I'm honestly so addicted to the way this thing is built in the few days of trying it even if I lost all of the stuff I did in it, I'd still have kept using it after the last tear was shed 🤣 I actually wanna say thanks for this project. I've enjoyed AppFlowy a shton, I gave it a glance a week or so ago and decided on the spot to deployed appflowy cloud from the overview! And I am glad I did. Its quite the uncommon experience to have software that is not only functional and extremely useful to core/critical everyday tasks but also an absolute joy to use! :D Super thankful for this project! On Sun, Mar 16, 2025, 8:21 PM Richard Shiue ***@***.***> wrote: > Reproducible steps: > > 1. Create a checklist field. In a row, enter some options into it. > 2. Turn that field into text > 3. Turn that field into single select option > 4. See that we mistakenly attempt to convert the data to an option > > — > Reply to this email directly, view it on GitHub > <https://github.com/AppFlowy-IO/AppFlowy/issues/7545#issuecomment-2727955867>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AH2UFZKSAXESZQGUHQ3VITL2UY5UNAVCNFSM6AAAAABZCTAS2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXHE2TKOBWG4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > [image: richardshiue]*richardshiue* left a comment > (AppFlowy-IO/AppFlowy#7545) > <https://github.com/AppFlowy-IO/AppFlowy/issues/7545#issuecomment-2727955867> > > Reproducible steps: > > 1. Create a checklist field. In a row, enter some options into it. > 2. Turn that field into text > 3. Turn that field into single select option > 4. See that we mistakenly attempt to convert the data to an option > > — > Reply to this email directly, view it on GitHub > <https://github.com/AppFlowy-IO/AppFlowy/issues/7545#issuecomment-2727955867>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AH2UFZKSAXESZQGUHQ3VITL2UY5UNAVCNFSM6AAAAABZCTAS2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRXHE2TKOBWG4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

mirror commented

2026-03-23 21:29:32 +00:00

Author

Owner

@annieappflowy commented on GitHub (Jun 17, 2025):

The web app (appflowy.com) doesn't have this issue

@annieappflowy commented on GitHub (Jun 17, 2025): The web app (appflowy.com) doesn't have this issue

mirror commented

2026-03-23 21:29:33 +00:00

Author

Owner

@SoFMeRight commented on GitHub (Jun 24, 2025):

I experienced this originally thru the Windows Desktop app. I found that
the web app does not support many of the features of the app... .. Has that
changed in recent time?

On Tue, Jun 17, 2025 at 8:16 AM Annie @.***> wrote:

annieappflowy left a comment (AppFlowy-IO/AppFlowy#7545)
https://github.com/AppFlowy-IO/AppFlowy/issues/7545#issuecomment-2980787046

The web app (appflowy.com) doesn't have this issue

—
Reply to this email directly, view it on GitHub
https://github.com/AppFlowy-IO/AppFlowy/issues/7545#issuecomment-2980787046,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH2UFZKUPVC2VITWAF4KAE33EAWOLAVCNFSM6AAAAABZCTAS2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBQG44DOMBUGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

@SoFMeRight commented on GitHub (Jun 24, 2025): I experienced this originally thru the Windows Desktop app. I found that the web app does not support many of the features of the app... .. Has that changed in recent time? On Tue, Jun 17, 2025 at 8:16 AM Annie ***@***.***> wrote: > *annieappflowy* left a comment (AppFlowy-IO/AppFlowy#7545) > <https://github.com/AppFlowy-IO/AppFlowy/issues/7545#issuecomment-2980787046> > > The web app (appflowy.com) doesn't have this issue > > — > Reply to this email directly, view it on GitHub > <https://github.com/AppFlowy-IO/AppFlowy/issues/7545#issuecomment-2980787046>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AH2UFZKUPVC2VITWAF4KAE33EAWOLAVCNFSM6AAAAABZCTAS2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBQG44DOMBUGY> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

mirror commented

2026-03-23 21:29:33 +00:00

Author

Owner

@appflowy commented on GitHub (Dec 11, 2025):

we didn't support undo in database. but in the upcoming release (0.10.7). You can update the field type back to checklist without losing data. I’m closing this issue. Feel free to reopen

@appflowy commented on GitHub (Dec 11, 2025): we didn't support undo in database. but in the upcoming release (0.10.7). You can update the field type back to checklist without losing data. I’m closing this issue. Feel free to reopen