Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum WorkSpace Copies filter lists all copied out design documents, while Copies filter remains empty
    • Sign In

    • State Not Answered
    • Replies 7 replies
    • Subscribers 61 subscribers
    • Views 1278 views
    • Users 0 members are here
    • Projectwise Explorer
    • MicroStation
    • ProjectWise
    • Local Document Organizer

    WorkSpace Copies filter lists all copied out design documents, while Copies filter remains empty

    TSAlex
    Offline TSAlex over 2 years ago

    ProjectWise Explorer, v. 10.00.02.99I

    IntegratedPower Geopak V8i (SELECT series 10), v. 08.11.09.918

    Managed Workspace environment

    The "WorkSpace Copies" filter in the Local Document Organizer is listing all local design files & references copied out during normal master file Check Out, as well as all workspace resource files. The separate filter list for "Copies" in LDO is practically empty (except for one file: world.dpr). This behavior appears to defeat the purpose of having these filters at all, which seem aimed at making it easier to parse local files to manually purge in the event of workspace file deletions in the Datasource, or otherwise manage copied out design documents separately.

    It seems reasonable that the lack of differentiation by ProjectWise between WorkSpace resource files and copied out design documents might also be causing other problems by packaging design files in with managed workspace exports.

    In any case, what I'm observing does not appear to be working as intended, and I am concerned that the excessive 'copy out' and 'managed workspace export' operations we are experiencing during ordinary plans production are being caused by this apparent incorrect classification of document 'Copies' vs. 'WorkSpace Copies' in PW.

    Is it possible that the Managed Workspace configuration variables for this particular project are too broadly defined, and end up flagging every resolved directory and its contents as 'WorkSpace' files? If so, what are some workarounds - if not, what explains this filter behavior in LDO?

    Thanks,

    TS

    • Sign in to reply
    • Cancel

    Top Replies

    • Kevin van Haaren
      Offline Kevin van Haaren Fri, Nov 20 2020 5:48 PM +1
      are you specifying a MS_RFDIR or MS_DEF in your workspace? When files appear in the workspace tab it's because Projectwise thinks the file, or the directory the file is in, is part of the workspace.…
    • Kevin van Haaren
      Offline Kevin van Haaren Fri, Nov 20 2020 7:14 PM in reply to TSAlex +1
      Neither should be defined in a managed workspace referring to folders inside of Projectwise. If MS_RFDIR is defined it should only point to folders outside of ProjectWise that hold reference files (although…
    • Kevin van Haaren
      Offline Kevin van Haaren Sun, Nov 22 2020 11:17 AM in reply to TSAlex +1
      After setting the variables did you purge the workspace files and try again? Three ideas: 1. managed workspaces are processed twice, once by Projectwise and once by microstation. Projectwise processes…
    • Kevin van Haaren
      0 Offline Kevin van Haaren Sun, Nov 22 2020 11:17 AM in reply to TSAlex

      After setting the variables did you purge the workspace files and try again?

      Three ideas:
      1. managed workspaces are processed twice, once by Projectwise and once by microstation. Projectwise processes everything to determine what files to copy out.  Once a copied out file is identified as part of a workspace it will remain so, even if the actual workspace no longer refers to the files. Purging the files and reloading the workspace fixes this.

      2. Did you set the variables to null in your UCF on your hard drive? I haven't tested but I'm not sure the Projectwise processing considers the UCF in processing the workspace. If it doesn't, then removing the variables in the UCF only affects microstation and not Projectwise.

      3. Don't set to (null), instead use

      %undefine MS_RFDIR

      %undefine MS_DEF

       

      • Cancel
      • Vote Up +1 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • TSAlex
      0 Offline TSAlex Sat, Nov 21 2020 1:31 PM in reply to Kevin van Haaren

      Kevin, I have set these at the user level:

      MS_DEG = (null)

      MS_RFDIR = (null)

      And set any other variable that resolved to a projectwise folder in the same way (or changed it to resolve to a file or wildcard). These were mostly on the Project level.

      However, all copied out documents & design references are still only displaying in the Local Document Organizer uneder the "WorkSpace Copies" filter, and the "Copies" filter results are unchanged.

      I have asked the PW admin for the Managed Workspace list of 'Variables to Exclude from Copy-Out' to see if I can learn anything else.

      Could this be the result of the Folder properties inside of PW of our various subfolders?

      Under the Folder Properties>WorkSpace tab

           Workspace type: 'Managed'

           Level associations: 'Object & Inherited'

      configuration blocks are coming from two levels:

           WorkSet/Project

           User

           "Allow inheritable configuration block associations from the parent to propagate to this object and all child objects" is checked.

      I'm grasping for straws here, do you have any other suggestions?

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Kevin van Haaren
      0 Offline Kevin van Haaren Fri, Nov 20 2020 8:51 PM in reply to TSAlex

      Off the top of my head, yes. Might be some rarely used ones that I'm forgett About.

      btw, it's best to avoid MS_RFDIR in any Projectwise workspace - managed or not.

       

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • TSAlex
      0 Offline TSAlex Fri, Nov 20 2020 7:18 PM in reply to Kevin van Haaren

      Great, thank you Kevin. Are MS_DEF & MS_RFDIR the only two problem variables I should be looking to disable in the managed workspace?

      • Cancel
      • Vote Up 0 Vote Down
      • Sign in to reply
      • Verify Answer
      • Cancel
    • Kevin van Haaren
      0 Offline Kevin van Haaren Fri, Nov 20 2020 7:14 PM in reply to TSAlex

      Neither should be defined in a managed workspace referring to folders inside of Projectwise.

      If MS_RFDIR is defined it should only point to folders outside of ProjectWise that hold reference files (although this is generally a bad idea). ProjectWise handles reference pathing for files inside of ProjectWise.

      MS_DEF shouldn't be defined at all.

       

      • Cancel
      • Vote Up +1 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