How are default WorkSet Properties modified

When a workset is created, there is an option to create new WorkSet Properties.  These can be added and edited later from the workset menu.

There are also default Workset Properties such as Project Name, Project Number, etc.  Where can these properties be modified?  The workset menu only shows the properties I created.  Under the File Properties within a DGN there is a section called WorkSet Properties where I can see both the default and user added properties (all properly greyed out since they shouldn't be edited within the file).  But I can only edit the ones I added.  How do I edit the default Workset Properties?

I'm investigating using the workset properties to populate sheet number block items such as the "Project Number" that will go on all sheets.  Once the Workset Properties are set and all the pertinent properties can be edited; is it possible to save that as a workset template (to be used on all projects)?

(I've also tested using properties within the Sheet Index properties, and have the same question about having a DGNWS template.)

Using OpenRoads Designer Version 10.04.00

Parents
  • The answer to your first question is that the properties are stored in the worksets DGNws file. You can open the DGNws file and edit any of the properties, they are stored on the file header. Any changes will be written to files opened with that workset active.

    You can have a workset template or a DGNws seed for creating new workset. There are configuration variables to set this up and you can create a base workset to work as a template if you want. A workset template is more detailed than a DGNws seed, the workset template also contains the dgnws but also folders and other files can be included.  There are several TR's on this concept so tread where you want with caution.

    Regarding Sheet indexing note that the Workset custom properties and sheet indexing properties and custom properties are somewhat different. Text fields, reporting, etc. can use either. One set is stored on the model (sheet models inparticular) the other is stored on the file.

    HTH

    ~HTH

    John.

    yep

    Answer Verified By: Stephen Chapman 

Reply
  • The answer to your first question is that the properties are stored in the worksets DGNws file. You can open the DGNws file and edit any of the properties, they are stored on the file header. Any changes will be written to files opened with that workset active.

    You can have a workset template or a DGNws seed for creating new workset. There are configuration variables to set this up and you can create a base workset to work as a template if you want. A workset template is more detailed than a DGNws seed, the workset template also contains the dgnws but also folders and other files can be included.  There are several TR's on this concept so tread where you want with caution.

    Regarding Sheet indexing note that the Workset custom properties and sheet indexing properties and custom properties are somewhat different. Text fields, reporting, etc. can use either. One set is stored on the model (sheet models inparticular) the other is stored on the file.

    HTH

    ~HTH

    John.

    yep

    Answer Verified By: Stephen Chapman 

Children
  • How do I change the default properties on the file header?  When I go to the Edit WorkSet area I can change the default "Description" variable and the variables I added.  The other default variables are not available here.

    Then when I go to the File Properties of a DGN in the WorkSet I can see both the "default" properties and the ones I could edit in the above screen.  How can these circled attributes be edited?

    When I used this DGNWS as a seed (either on the use template option on the create workset dialog OR in the configuration variables) my added workset variables do not come across.

    I fared better using the Sheet Index variables.  I added three subfolders to the Sheet Index, each with their own sheet numbering rules, plus I added some Sheet Index variables.  These all came over when using the DGNWS as a seed.  However they came across as a group with the seed DGNWS name.  A second empty group with the active DGNWS name was also included.  This seems rather awkward; I'd rather have the seed group renamed to the new DGNWS name - I think I saw another thread about that.

    One other oddity is that the Sheet Index variables do not show up in the Manage Sheet Index dialog.  They can be seen and modified in the Properties tab, but not in the dialog.

    SCC.dgnws

    For my application I think I'd rather use the workset properties than the Sheet Index properties since, as you point out, they are more universally available.  But at the moment the Sheet Index variables seem to work better.

    ORD-2018 Release 2 Update 4 - Version 10.04.00.48

  • Open the DGNws file and you can edit those properties. They are then pushed on to all files opened in that workset. You can not edit the values from any file other than the dgnws.

    I think those variables are used with ProjectWise CONNECTED projects.

    One other oddity is that the Sheet Index variables do not show up in the Manage Sheet Index dialog.  They can be seen and modified in the Properties tab, but not in the dialog.

    They only show up once a sheet has been added to the Index. Sheet Index properties are more robust as they can be edited from any file. The Sheet index tools actually open the DGNws in the background to allow this.  Those Workset properties don't really have a UI other than the properties dialog.

    Let me know if I need to explain more.

    ~HTH

    John.

    yep

  • Thanks!  It did not occur to me open the DGNWS in MicroStation.  That answers my primary question. 

    It appears that added variables in a DGNWS seed do not travel to new DGNWS files - but that is something for another day.

    Steve

  • Depends on what you exactly mean but I may have a TR on that.

    ~HTH

    John.

    yep

  • John Frampton - you just blew my mind!

    I never would have thought you could open a .DGNWS file in MicroStation like a dgn or a dgnlib file.

    Thank you for the great tip.

    Rod Wing
    Senior Systems Analyst