I'm using FF= to clip and save out portions of my file to new files, but the attached Item Types are not coming through. Is this a limitation or is there a solution that anyone knows?
Microstation Connect V10.14.02.01
I have tested the operation of the FF= or Copy Fence Contents tool and have found that if the Item Types are stored in a DGN file but not attached to any elements then they do not copy through to the new DGN file. Is this the operation and outcome you are describing here? Maybe you could provide some examples so we can confirm what you are explaining here. You might consider storing your Item Types in a Design Library (DGNLIB) rather than within separate DGN files.
RegardsAndrew BellTechnical SupportBentley Systems
Andrew Bell said:You might consider storing your Item Types in a Design Library (DGNLIB) rather than within separate DGN files.
When you first attach Item Types to DGN elements, the Item Type definition is copied from the DGNLib to the active DGN file. If that were not the case, then we would have to ship a complete workspace — including its DGNLibs — to a client wanting to see business data.
Regards, Jon Summers LA Solutions
You are correct Jon Summers, the exported file DGN file after performing the FF= should contain the Item Types stored in the original DGN file. I have raised a new Defect for this to be rectified.
Defect 1108818: Item Types dropped after performing Copy Fence Contents to New File
We do have the item types stored in a dgnlib. When items are attached, the definitions copy in, as expected, but as you found, they are lost during FF=. Thanks for raising the defect. Also, I found that when copying an element with an item attached using Fence Clip, even within the same file, the new element has no item attached. If you copy the entire element, the item comes with it.
Thanks for that extra detail. I will add that to the defect.