Hi,

At my company, we have to work on client files obtained from client datasources. Some clients do not allow us to work on their datasource directly. In these cases, we have a copy of the client's environment on my company's ProjectWise server so we can view/edit files and metadata freely with the same settings and attributes the client sees. We obtain the files needed and associated metadata using the ProjectWise Export to Excel tool on their system and then using the Import from Excel into our system. Then we import these files and metadata back into the client's ProjectWise datasource after we have completed our scope using the same tools. This client import process will fail unless we edit the Excel metadata spreadsheet ProjectWise creates and change the attribute IDs listed from our system to match the client's system, otherwise the import to their system will fail. Since we're essentially dealing with two different databases, the same file will have two different attribute IDs when inserted on different systems.

When talking with Bentley about this process, it was mentioned that this was not the intended use of this tool. It was also mentioned that Bentley does not have a tool intended to assist in a process similar to the one I described.

I'm requesting an update to the Excel Export/Import tool to preferably not rely on the Attribute ID or creation of a new tool directly intended to help transfer documents and metadata back and forth between datasources.