Save button in Drawing Set Tab problem

I am having a problem with multiple users clicking the “Save” button in the “Drawing Set” tab inside the “Program Manager” form at once after modifying the Drawing Set descriptions. It appears that when this scenario happens, the descriptions for some drawing sets get duplicated.

We are adding two more descriptions and modifying their titles to each drawing set using the API, we are not using the PowerWise attribute mapping feature in our test project.

I know this button goes through all drawing set descriptions from the selected project and updates them in the database, but is it meant to be used by a single user?

It works properly when used by single user, but duplicates information or goes to default drawing set 1 when multiple people are clicking the Save button at once.

Please help!!!

  • Hi Diana.

    Unknown said:
    We are adding two more descriptions

    I'm not sure what this means. Are you adding two more descriptions somehow so that there are seven total?

    Unknown said:
    and modifying their titles to each drawing set using the API

    Does this mean you are changing the values in the Name column, for example changing "Description1" to "MyFavoriteDescription"?



  • Yes, that is correct.
    Please help understand how is the Save button designed and why its acting up when multiple users are trying to Save.
     
    Diana Sharkova, PMP
    Sr. Engineer
  • First, one disclaimer. Adding additional drawing set descriptions beyond the default five and changing the description names are not intended uses of the software as far as I know. Additional drawing set descriptions is leveraging how the software works, and the ability to change the names was originally an oversight. That said, it seems to work, although what I've done would not be considered extensive testing.

    When the Save button is clicked, I believe the software executes an Update statement that updates the relevant records in the Description table of the project database. I would guess that if two users click Save, it is a case of "whoever clicks last, wins". User1 says change it this way, and the software does, but then user2 says no, change it a different way. An example: if user1 changes the Name value and Description value for the first description, and user2 leaves the default Name value but changes the Description value for the first description, and user2 clicks Save after user1, user 2 wins. It could appear to user1 that the Name of the first description gets reset to the default "Description1" in this example because user2 left it that way when they clicked Save. And if user1 had already changed another Description to what user2 subsequently changed the first description to, there would then be duplicate values. Could this be what is happening?

    It seems to me that it would be best to have just one user making these changes, or assign users to change certain projects so they don't interfere with each other's changes. But again, I am not endorsing these types of changes.



  • See below.
     
    Diana Sharkova, PMP
    Sr. Engineer