Hello @Richard. We have tons of hybrid files to support old facilities. We need to be able to work with contractors on these facilities. If you didn't foresee the need for supporting a key document type, then you shouldn't punish us. I see this as a failure. You recommend that we write a script to make up for your failure. You should at least do this for us and make it readily available.

Thank you for your suggestion, but this cannot be impemented.

The data architecture to support hybrid files is not available in Portal, and enabling hybrid would mean an entire rebuild to support multiple source files. This is not scheduled on our near term roadmap.

On Power side, something that could be configured and scripted is a custom command to turn the hybrid parts into referenced documents when sending to Portal. This command should then be used by the user before sending to Portal.

If needed another command could be configured to turn the referenced documents back into hybrid parts.

Relevant script methods can be found here: https://help.meridian360.com/2022/Content/Online_Help/VBScript_API/Objects/Document_object_methods.htm?Highlight=hybrid

We had to add the hybrid part as a document in PowerWeb then reference the document into the CAD file, that was the only way we could get it to work.

The Hybrid parts are not ideal between PowerWeb and Portal, this really needs to be fixed.

I have 2 customers now that use Portal and are considering removing it rather than use the solution presented by Accruent of converting all their AutoCAD files to embedded TIFs as it was Accruent that originally imported them into the Meridian Vault as Hybrids.