Work around for renaming tags

Hello all,

We have a piece of code that updates tag values to match approval dates input by the user.  Given that several designers could be working on the drawing at a time, we are looking to update only those tagged elements added by a specific user.  Example: designer A adds three cells containing the "approvalDate" tag, and designer B adds two cells containing the 'approvalDate' tag.  When designer B runs the piece of code, only the two cells he/she added should have the "approvalDate" tag values updated and those added by designer A should be ignored.  It's also possible for the designer to be working multiple projects using the same drawing so we now need to seperate the update by user name and project number.

My original thought was to rename the tag name by appending the username and project number as the cell is being placed, but have since learned the tag definition name is a read only property!!!  Any thoughts on how I can isolate the added features by username and project number?

Any pointers in the right direction will be greatly appreciated!

Adam O.

Parents
  • Data Models and Access Control

    Make the problem abstract and remove MicroStation from your considerations. You are left with a table of data …

     …Approval Date …
    Row 1
    Row 2
    Row 3

    Your requirement …

    • User 1 should be able to update Row 1, but not edit any other row
    • User 2 should be able to update Row 2, but not edit any other row
    • User 3 should be able to update Row 3, but not edit any other row

    There's no simple control mechanism that would grant those access rights. Consider implementing your data, say, in an Excel worksheet or in a relational DB table, and you remain faced with the same dilemma.

    User Access Rights

    When you discuss different users, do you mean computer users each having her own login account?

    If so, you might consider some sort of reference attachment workflow. The MicroStation idiom to prevent a user editing data is the reference attachment.

    User 1 works on her DGN models and attaches those of User 2 and User 3 as references. User 1 can see the tags added by her colleagues but can edit only those in the active DGN model.

    User 2 works on his DGN models and attaches those of User 1 and User 3 as references. User 2 can see the tags added by his colleagues but can edit only those in the active DGN model.

    User 3 works on her DGN models and attaches those of User 1 and User 2 as references. User 3 can see the tags added by her colleagues but can edit only those in the active DGN model.

    Regards, Jon Summers
    LA Solutions

     
    Regards, Jon Summers
    LA Solutions

Reply
  • Data Models and Access Control

    Make the problem abstract and remove MicroStation from your considerations. You are left with a table of data …

     …Approval Date …
    Row 1
    Row 2
    Row 3

    Your requirement …

    • User 1 should be able to update Row 1, but not edit any other row
    • User 2 should be able to update Row 2, but not edit any other row
    • User 3 should be able to update Row 3, but not edit any other row

    There's no simple control mechanism that would grant those access rights. Consider implementing your data, say, in an Excel worksheet or in a relational DB table, and you remain faced with the same dilemma.

    User Access Rights

    When you discuss different users, do you mean computer users each having her own login account?

    If so, you might consider some sort of reference attachment workflow. The MicroStation idiom to prevent a user editing data is the reference attachment.

    User 1 works on her DGN models and attaches those of User 2 and User 3 as references. User 1 can see the tags added by her colleagues but can edit only those in the active DGN model.

    User 2 works on his DGN models and attaches those of User 1 and User 3 as references. User 2 can see the tags added by his colleagues but can edit only those in the active DGN model.

    User 3 works on her DGN models and attaches those of User 1 and User 2 as references. User 3 can see the tags added by her colleagues but can edit only those in the active DGN model.

    Regards, Jon Summers
    LA Solutions

     
    Regards, Jon Summers
    LA Solutions

Children
  • Thank you Jon, you saved me a great deal of time trying to find a way to get this done via Microstation!  

    We have an "old dog" environment in the office with the majority very resistent to change.  I can push the tool with very minimal setup requirements on the user's end and will be shot down if the "prep work" is increased.  I wrote the coding for this project on my own time because it's a great time saver (updating construction stamp, approval dates and issued for construction dates via batch processing), but may abandon the project if there is no way to isolate the cells by user without additional user interaction.

    Thanks again for the suggestion!