OpenRoads V8i SS4 Maintenance Release 2 and import and export of .eav file

RE: OpenRoads V8i SS4 Maintenance Release 2 and import and export of .eav file

Wesley Nyberg — Thu, 28 Apr 2016 15:42:34 GMT

Thanks!

RE: OpenRoads V8i SS4 Maintenance Release 2 and import and export of .eav file

Chris Key — Thu, 28 Apr 2016 15:30:21 GMT

I didn't have issues with it loading the EAV from PW once I copied it up. But this definitely will all need to be looked at so I will make a note in the defect so they can double-check that process as well.

RE: OpenRoads V8i SS4 Maintenance Release 2 and import and export of .eav file

Wesley Nyberg — Thu, 28 Apr 2016 15:00:16 GMT

I did try to save the .eav file to my local and copy it up to Projectwise but every time I try to import the .eav that I copied up Microstation crashes. It doesn't crash if I import it from my local drive though.

RE: OpenRoads V8i SS4 Maintenance Release 2 and import and export of .eav file

Chris Key — Thu, 28 Apr 2016 14:50:58 GMT

Defect 423383 has been filed for this issue.

RE: OpenRoads V8i SS4 Maintenance Release 2 and import and export of .eav file

Chris Key — Thu, 28 Apr 2016 14:14:23 GMT

When writing the file to ProjectWise, you would need to first select the Folder at the top where you are saving the file. So you select the 'Change' button and browse to a path in PW you wish to save the file. Then you give it a Name as you have done and the File name does need the file type extension as you did in the second screenshot.

However with this all set up and you select Save, it will create the file in PW but there is nothing stored in the file so there appears to be a defect which will not write the information inside the file when created in PW. The .EAV File is an XML coded file so we tried different processes and combinations of the Application, Document Names and File Names with the file extensions with no luck. I believe it is an issue with writing the XML file to PW.

As a workflow, you can save the file local and copy up to ProjectWise.