# DT3 Warning: Possible bug resulting in loss of data

**URL:** <https://discourse.devontechnologies.com/t/dt3-warning-possible-bug-resulting-in-loss-of-data/46477>\
**Category:** DEVONthink\
**Created:** [April 26, 2019, 12:24am UTC](https://discourse.devontechnologies.com/t/dt3-warning-possible-bug-resulting-in-loss-of-data/46477 "2019-04-26T00:24:02Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bernardo\_V](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bernardo_v/32/7312_2.png) [@Bernardo\_V](https://discourse.devontechnologies.com/u/Bernardo_V)\
**Post date:** [April 26, 2019, 12:24am UTC](https://discourse.devontechnologies.com/t/dt3-warning-possible-bug-resulting-in-loss-of-data/46477/1 "2019-04-26T00:24:02Z")

</div>

I just (nearly) lost thousands of MD files while moving them from one DB to another.  
Here is a breakdown of what happened:

1. I had a indexed folder with thousands of text files in Greek and English.  
English files were tagged with ENG and Greek files with GRC.

2. I moved the indexed items to the database.

3. I used the tags pane to filter only the English files with the ‘ENG’ tag.

4. My folder structure appeared. I moved it to a new database.  
The (wrong) assumption was that it would pass along only the ENG files while maintaining the GRC files organized under the same folder structure in the old database.

5. The outcome was baffling. Most folders were moved, but some were left behind (without any files).  
Similarly, most ENG files were moved, but **ALL** greek files **disappeared**. By this I mean the following: the tag filter wasn’t active anymore and they were not in the new database; they were not in the old database; they were not in the trash.

My first backup was Dropbox since the indexed folder was synced. For some reason the files were not in the cloud along with other deleted files either. Luckily, the folder was also a git repository so I managed to revert the changes using a git manager (sublime merge, in this case).

Maybe it was my fault and mistake. Maybe it is a bug. I don’t know.

---

<div class="post-metadata">

**Author:** ![BLUEFROG](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bluefrog/32/135_2.png) [@BLUEFROG](https://discourse.devontechnologies.com/u/BLUEFROG)\
**Post date:** [April 26, 2019, 2:49am UTC](https://discourse.devontechnologies.com/t/dt3-warning-possible-bug-resulting-in-loss-of-data/46477/2 "2019-04-26T02:49:52Z")

</div>

> 2. I moved the indexed items to the database.

Do you mean you used **Move into Database** from the contextual menu?

PS: I hope you are working with test data, not your live databases.

---

<div class="post-metadata">

**Author:** ![Bernardo\_V](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bernardo_v/32/7312_2.png) [@Bernardo\_V](https://discourse.devontechnologies.com/u/Bernardo_V)\
**Post date:** [April 26, 2019, 10:16am UTC](https://discourse.devontechnologies.com/t/dt3-warning-possible-bug-resulting-in-loss-of-data/46477/3 "2019-04-26T10:16:34Z")

</div>

> [@BLUEFROG](#):
>
> > 2. I moved the indexed items to the database.
> 
> Do you mean you used **Move into Database** from the contextual menu?

Yes.

> [@BLUEFROG](#):
>
> PS: I hope you are working with test data, not your live databases.

Apparently I wasn’t that smart as I assumed it would already be safe to use. But I’ll make sure to use dummies from now on.

Also, I encountered the same issue again moving indexed files from um db to another. They simply went missing and I could not find them again.

---

<div class="post-metadata">

**Author:** ![BLUEFROG](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bluefrog/32/135_2.png) [@BLUEFROG](https://discourse.devontechnologies.com/u/BLUEFROG)\
**Post date:** [April 26, 2019, 2:14pm UTC](https://discourse.devontechnologies.com/t/dt3-warning-possible-bug-resulting-in-loss-of-data/46477/4 "2019-04-26T14:14:14Z")

</div>

> Apparently I wasn’t that smart as I assumed it would already be safe to use. But I’ll make sure to use dummies from now on.

Remember, this is a **beta test** , not an _“early access program”_. It is meant for testing, finding/reporting bugs.

Also, there have been considerable changes to indexing in DT3. We will try to reproduce the issue.

---

<div class="post-metadata">

**Author:** ![Bernardo\_V](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bernardo_v/32/7312_2.png) [@Bernardo\_V](https://discourse.devontechnologies.com/u/Bernardo_V)\
**Post date:** [April 27, 2019, 12:58am UTC](https://discourse.devontechnologies.com/t/dt3-warning-possible-bug-resulting-in-loss-of-data/46477/5 "2019-04-27T00:58:44Z")

</div>

@BLUEFROG, thanks for clearing that out.

---

<div class="post-metadata">

**Author:** ![Bernardo\_V](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bernardo_v/32/7312_2.png) [@Bernardo\_V](https://discourse.devontechnologies.com/u/Bernardo_V)\
**Post date:** [April 27, 2019, 1:19am UTC](https://discourse.devontechnologies.com/t/dt3-warning-possible-bug-resulting-in-loss-of-data/46477/6 "2019-04-27T01:19:38Z")

</div>

Another possible issue. When using the search, it is odd that it finds many occurrences in the file, but lists just one of them in the sidebar.

 ![07](https://devontech-discourse.s3.dualstack.us-east-1.amazonaws.com/uploads/original/2X/1/172165ef471049feef32d1c76b00ccd9b6f79f80.jpeg)

---

<div class="post-metadata">

**Author:** ![cgrunenberg](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/cgrunenberg/32/7172_2.png) [@cgrunenberg](https://discourse.devontechnologies.com/u/cgrunenberg)\
**Post date:** [April 28, 2019, 9:45am UTC](https://discourse.devontechnologies.com/t/dt3-warning-possible-bug-resulting-in-loss-of-data/46477/7 "2019-04-28T09:45:49Z")

</div>

Could you send the doc plus the search term to cgrunenberg - at - [devon-technologies.com](http://devon-technologies.com)? Thanks!