Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / Document Linking
Microsoft Dynamics NAV (Archived)

Document Linking

(0) ShareShare
ReportReport
Posted on by Kevin Fons 45

I was looking at linking documents like PDF drawings to item sin NAV (2009 R2 mixed classic / rtc). I know I can link the document in RTC (and possibly classic) and it works, Zeta Docs Express is another option but I have not researched it much. The thing I worry about with these is links being corrupted, etc. if something changes (directory name, etc. inadvertently). The best solution would be saving the file as a blob directly in the DB (not sure how exactly to do this easily though).

What are others thoughts and experiences with this?

Kevin

*This post is locked for comments

  • Kevin Fons Profile Picture
    Kevin Fons 45 on at
    Re: Document Linking

    So are you saying to modify the exisiting functionality or create brand new functionality.  It sounds like you did the Blob and moved away from it and are now just linking?  I'm not completely opposed to linking, it may work better in some cases (ie we save the active drawing as the drawing number only (1234.pdf) and then archive the old revision as the drawing number with the revision (1234C.pdf).  This way if we replace the file with the new revison the link always points to the current without having to re-connect the new one or replace the old one somehow.  

    This goes back to should we just use the standard links saved on a network drive or should we use the free Zeta Docs express and save in sharepoint, or something else?

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: Document Linking

    Sounds like you don;t trust your system setup.  With a solid office setup nothing should happen "inadvertantly".  And with any important data a proper setup and backups are important.  Not just the database, tho having it all in one place can solve your issue.

    We cleared out all our blobs and saved them externally on a seperate server with a raid 1 array and scheduled backups.  With our 150,000 items, that's alot of pictures and alot of space which ballooned our database.

    If I was to tackle such an issue I would create a NEWLINKS table that has at least four fields.

    TYPE- No.-Description-blob  - you might want to also add a doc date and userid field if you want to keep track of who added what & when.  

    Type & No. & description would be the primary keys.

    that way you can save multiple docs for the same item number.

    The type field would be an option type: customer,vendor,item,etc so it could be expanded to hold other docs that might relate to customers & vendors.

    depending on the type & no you can do a lookup to the right account.

    you can use the item picture functionality as an example.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans