The note attachment is where documents go to die
Watch a diligent advancement services coordinator handle a signed gift agreement, and you will often see the same move: scan it, open the donor in Dynamics, and attach the PDF to a note. It feels like exactly the right thing, and the instinct behind it is exactly right. The document belongs with the constituent. Put it where the relationship lives.
The trouble is what happens next, which is nothing. Ever.
Why the note is a dead end
A note attachment in Dynamics is stored, but it is not managed, and the difference plays out in four quiet ways.
Search cannot read it. Dataverse search covers fields and text, not the pages inside an attached PDF. The scanned agreement contains a naming clause, a reporting schedule, and a restriction, and none of those words are findable. The document is on the record and still invisible.
The timeline buries it. A donor record accumulates years of calls, emails, and tasks. The note holding the 2014 agreement sits somewhere under all of it. Finding it means scrolling and knowing it exists, which brings us to the real dependency.
It relies on one person’s memory. The coordinator who attached it knows it is there. When she retires, the knowledge retires with her. Her successor opens the same record, sees an ordinary timeline, and starts a search through shared drives for a document that was on the record the whole time.
Governance never sees it. Your retention schedule says gift agreements are permanent records. The retention system has no idea this one exists. No hold can freeze it, no audit trail covers who viewed it, and nothing prevents the note, and the only copy, from being deleted with a click.
A note attachment is filed in the one place search cannot read and retention cannot reach.
There is also a bill for all this. Those attachments accumulate in Dataverse storage at Dataverse prices, which is how a decade of good filing instincts becomes the capacity email your admin gets every Monday.
The instinct was right. The container was wrong.
Here is what makes this failure mode so persistent: attaching the scan to the note is the closest thing Dynamics offers to filing a document on the constituent, and filing on the constituent is the correct idea. Documents belong on the record, not in a folder named “Scans 2019”. The people doing this were never wrong about where the document should live. They were let down by what the note does with it, which is hold it in the dark.
So the fix is not to stop attaching documents to records. The fix is to change what happens underneath.
What it looks like when the document lives
PaperlessZen™ extracts note attachments out of Dataverse and into an archive, including the backlog of years past, in bulk. The note keeps showing its attachment, so nobody’s habits change. But underneath, the file has become a document:
- Search reads every page, so “naming rights” finds the clause and the page it sits on.
- It is filed on the constituent, next to every other agreement, amendment, and letter, visible in one panel on the record instead of buried in one note.
- Retention, legal holds, and an audit trail govern it like the record it always was.
The coordinator’s instinct is finally honored end to end: the document is with the donor, and it can be found by someone who does not know it exists. That is the whole difference between filing and burial.
If your team has spent years attaching scans to notes, the good news is that nothing was wasted. The documents are all sitting there, on the right records, waiting to be turned back on. Read how the extraction works, check what those attachments are costing in your capacity report, or book a demo and watch a note from 2014 become searchable.