Sounds like you also need to include the MM_* tables in the pGDB. You should be able to do that using ArcCatalog by dragging them from your sde database into the pGDB.
We do PGDBs all the time here.
- On SDE as the data owner, run the "ArcFM XML Export" tool on the database
- Check every option on the export screen, select where you want the file to go, and give it a name. Do NOT check the "Apply Style Sheet" option. (you will probably see a warning that some info could not be exported, just click "yes")
- On SDE as the data owner, copy the data you want to the PGDB.
- Once this is completed, run the "Create/Update ArcFM Solution System Tables" tool on the PGDB.
- Exit ArcCatalog and relaunch it (you have to do this to release the status lock on the PGDB)
- On the PGDB, choose to "Upgrade ArcFM Solution Database".
- Once completed, run the "Convert to ArcFM" tool and choose "Convert to use ArcFM Objects" (Click "Yes" when it warns you about this may prevent some tools from working)
- Finally, run "ArcFM XML Import" tool on the PGDB. Select the option to "Overwrite" and choose the XML you created in step 2. Do NOT check the "Apply Style Sheet" option. (you will most likely get a warning that some info could not be imported...this is ok, just click "yes")
You should now have a fully functional ArcFM-erized PGDB.
Thanks for everyone's help thus far, I appear to be making progress! When I'm performing the XML export, should I change the database connection back to the default sde? It makes sense that I should be, but all of the previous steps in creating this had me pointed to the version I created.
I usually pull the XML straight from DEFAULT.
I'm up and running, all except for the error code that appears when trying to use connection manager! I'm currently working through that issue (found the workaround online, even though I've yet to determine which non-fiber layer is preventing me from executing the command).
Thanks again folks