ProjectWise Attribute Mapping security issue

I do not have the ability to map ProjectWise attributes within Promis.e. Error message is attached.

I even setup the Promis.e setup configuration with the login of a regional ProjectWise administrator within my company.  Even with her security privileges, it still gave the same alert message.

What specific security privileges is Promis.e looking for within ProjectWise to have this functioning?

The image below is showing: Promis.e attribute = Designed By being mapped to ProjectWise attribute = DESIGNED_BY, both of these are editable attributes within their respective programs.

  • The ProjectWise Attribute Mapping settings, like the other Project Options settings, are stored in the ProjectOptions.xml file in the project's folder. The message seems to be saying you do not have permission to modify this file.

    Do you get the same message if you make a change to an area of Project Options besides ProjectWise Attribute Mapping?

    I removed the Document > Modify permission for my user and then got a different message ("ProjectOptions.xml file may be read-only") when I clicked Apply on Project Options. So I don't know what's causing the message for you. Please see the ProjectWise permissions for promis.e and Bentley Substation integration article if you have not already.



  • Yes, I get the same error message. But I can actually go into the projectoptions.xml within ProjectWise explorer and make modifications and check it back in, however when I did this with the ProjectWise attributes it didn't do anything to the files associated with the project.

    Within the XML it had the mapping, and within Promis.e it had the mapping, BUT none of the attribute information transferred over to ProjectWise. I'll check with the ProjectWise team and see if it has something to do with the "Allow user to change project types and project Properties" security setting.

    Bentley Software utilized: Promis.e v.08.11.13.57, ProjectWise v.10.00.01.67, MicroStation v.08.11.09.536

  • Hello Matt, modifying Promis.e options within ProjectWise is directly related to the ProjectWise security option to "Delete Project". Why would Bentley have a dependency between Promis.e options and deletion of a ProjectWise Project?

    We have hundreds of projects on multiple datasouces using ProjectWise from across the business, we as an organization don't apply that permission to regular user accounts for obvious reasons.

    Should I submit an enhancement request to not have Promis.e options dependent on ProjectWise project deletion?

    Bentley Software utilized: Promis.e v.08.11.13.57, ProjectWise v.10.00.01.67, MicroStation v.08.11.09.536

  • After I disabled the "Allow user to change project types and project Properties" setting for my user, I receive the same "You do not have permission to do this on some subfolders or files of the project" error message as you when I click Apply on Project Options.



  • We also did some testing on our Sandbox datasource, modifying Promis.e options within ProjectWise is also directly related to the ProjectWise security option to "Delete Project". Why would Bentley have a dependency between Promis.e options and deletion of a ProjectWise Project? I mentioned this in the post directly above yours, we seem to have responded at the exact same time.

    Bentley Software utilized: Promis.e v.08.11.13.57, ProjectWise v.10.00.01.67, MicroStation v.08.11.09.536