Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum dms_delete
    • Sign In

    • State Not Answered
    • Replies 14 replies
    • Subscribers 64 subscribers
    • Views 1995 views
    • Users 0 members are here

    dms_delete

    Luc Poulin
    Offline Luc Poulin over 3 years ago

    Hello

    Anyone has a detail explanation of when PW will add prefix like

    dms_delete

    dms_missref

    etc...

    Trying to reproduce the scenario that lead to this

    • Sign in to reply
    • Cancel

    Top Replies

    • Loris Paoletich
      Offline Loris Paoletich Thu, Jul 7 2022 9:40 PM in reply to Gayatri Belhekar +2
      Hi Gayatri, We are having issues with data shortcuts not finding the source dwg. None of the source dwg have been removed from PW, but for whatever reason all the reference files they now have the dms_deleted…
    • Loris Paoletich
      0 Offline Loris Paoletich Fri, Aug 26 2022 1:06 PM in reply to Bradley Armstrong

      Hi Bradley,

      This is the beginning...of the END!...just kidding.

      I used the ProjectWise Data Shortcut Project Editor to re-associate all the broken references to the source drawings, and that seemed to work. The only -not minor- problem that we had after re-pathing everything was that users were still getting broken DS all the time within individual DWGs. Those broken DS were just repaired within C3D by doing 'right-click'>Repair Broken Reference. 

      If you go the PW Data Shortcut Project Editor route, be patient on opening the CivilDSProj file as it may take a long time the first time. Just let it grind on the side and don't kill it through Task Manager. I would also do that when there is not a lot of users activity on DS or just ask other users not to open any drawing associated with the DS. Again, it is very slow at the beginning to edit and re-path, but it gets better as you start to re-connect broken paths. I did mine after office hours.

      I have no clue why we got the dms_delete and why this problem started.

      Hope this help.

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Dave Cumming
      0 Offline Dave Cumming Sun, Aug 28 2022 10:37 PM in reply to Bradley Armstrong

      Hi Bradley, 

      Deleting the "d" / "dms" folders is only advised after you first use the PW Local Document Organizer to purge the files from them. 

      Deleting the folders ensures that you are also purging any other residual clutter that may also exist in them and that PW is not managing, such as: .bak files; previous versions; files that have since been renamed or moved to other PW folders; dms_deleted files. 

      You don't necessarily need to purge the entire working directory. You can be selective, but that may take more time than it's worth because you will have to cross reference all of the folder IDs. 

      Are you seeing dms_deleted prefixes on your XREFs, or are they related to Civil 3D source drawings and therefore showing up in the prospector?

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Bradley Armstrong
      0 Offline Bradley Armstrong Mon, Aug 29 2022 9:14 AM in reply to Dave Cumming

      The prefixes are showing up in the prospector for the surface data shortcuts. The source drawing name stays the same, so the link is broken and needs repair. 

      This specific package underwent a relocation recently, and completely repathed. All of the XREFS and shortcuts were working properly the week of 8/15, but this occurrence popped up last week. This is a pretty significant package with over 70 surfaces used, so it was quite frustrating to relocate, recreate the proper paths, and then have the data shortcuts randomly break. However, it does seem like the shortcuts we have been able to repair starting late last week are sticking. 

      The Xrefs never experienced this prefix issue.

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Dave Cumming
      0 Offline Dave Cumming Mon, Aug 29 2022 12:29 PM in reply to Bradley Armstrong

      Hi Bradley, 

      Just to make sure that I'm clear on the issue (because terminology can often be interchangeable)... Do the surface data shortcuts appear to be broken in the Data Shortcut Project itself (in the lower half of the Prospector panel) or are they only broken when they are being consumed as references?

      Are you seeing this with ALL of the surface data shortcuts?

      Civil 3D likes stability. Making changes to the names or the locations of your source drawings can create a lot of additional work, but ProjectWise will allow you to move source drawings (and XREFs) and it will continue to maintain the relationships between those files and the documents that depend on them, as long as the dependencies were created in an integrated session of the CAD application. The .CivilDSProj file treats the source drawings as dependencies and if they move to a new PW location, it will continue to find them.

      After a significant change to the full paths (including the file name) of source drawings, it is always best to purge all the old project files from everyone's working directories because moving a document in PW does not have any affect on the files already copied out to the users. 

      Consumer drawings (those that DREF the surfaces) do not continuously look to the Data Shortcut Project to maintain updates to the path of the source drawings where they are DREFing from. Once you create the data reference in a consumer drawing, it hard-codes the local (working directory) path to the source drawing in the consuming drawing file, so if that location changes or if the source drawing is renamed the DREF presents as broken and it needs to be repaired. The definition of a "broken" data reference refers to the full path to the source of the data shortcut. Civil 3D uses those hard-coded paths to automatically synchronize each DREF when a consumer drawing is opened. When this happens, if the source drawing that it is looking for cannot be found in the target directory the ProjectWise integration will create a placeholder file with the prefix dms_deleted and the DREF will present as broken. 

      "Repairing" a "broken" DREF just means that you are telling the consumer drawing where the source drawing can now be found. It is important to also run a "Synchronize" after you make the repair. 

      Relocating source drawings can lead to a lot of DREF repairs throughout any of the drawings that depend on those source drawings. The ProjectWise integration provides a batch tool for repairing those data references, provided that all of the data shortcuts (in the data shortcut project) are healthy. Running the command DSFOLDERREPAIR from the PW-integrated C3D interface will allow you to cycle through all of the DWG files in a given PW folder (and optionally its subfolders) and repair all of the DREFs in each file against the source drawing location that is known to the.CivilDSProj file. 

      As with any batch process, doing this should first be tested on a sample dataset and coordinated with your project team, and especially with the project manager. Consider this the C3D equivalent of running the ScanRef tool for your XREFs... in order to parse out a sample/test dataset from the rest of the files in the folder that you run the process on, I would recommend that you either:

      1. Move a subset of documents to another PW folder and run DSFOLDERREPAIR on that folder, or
      2. Set all of the documents in the target folder to Final Status (or some other read-only state) except for the documents in the test dataset

      At this advance stage of your project, there are a lot of unknown variables that may be factoring into the equation. In particular, I often find evidence that some of the data shortcuts or data references were created (or edited) by someone who was opening files directly from their Working Directory. Relocating the source drawings can shine a spotlight on previously unknown issues that were caused by that action because those dependencies have to be recreated with PW integration. 

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    <

    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies