ItemTypes 2 Tags - problem with multiple TagSets...

Hi Mladen Kolarek,

Could you please provide your DGN file for testing?

if I understood correctly, you are using 3 different softwares in your workflow.

Attach item dialog on your second screen shot looks like OpenCities Map and the Tag Sets dialog does not look like MicroStation, maybe Open Comms.

was the DGN file originated with Microstation or Bentley Map?

What product do you use to export\save from DGN to DWG? What product do you use to open DWG and check for TagSets?

Do you get the same results opening the DWG with MicroStation and OpenCities?

According to what is posted, the item types are attached using OpenCities Map. This is also used to export the DWG. At that point, OP is using Bentley Map V8i (SS4) to view the DWG file and check the tag sets. The tag set dialogs do look to me like V8i products.

OP, What version of DWG are you saving to? Do you have access to plain MicroStation (instead of OCM or MAP)? Do you have access to AutoCAD?

Hi Maria and Mary,

first, the original DGN file is attached here

TEST_01.dgn

To create Cells, define ItemTypes, attach ItemType to each Cell and export to DWG (R2000), I use OCM Ultimate 10.17.01.29.

I use BMap V8i (SS4) 8.11.09.887 to check TagsSets and attached Tags in exported DWG (R2000).

@Mary I have access to plain Microstation and ACAD although haven't installed any of those on my computer. Today I'll check if there are any differences if I use MicroStation instead of OCM. I'll let you know what happens.

Hope this help.

Thank you all for your interest in this topic and your help!

Mladen 

Hi again,

I've made some progress with unique definition of TagSets in DWG file... but some new problems appeared when I export DGN to DWG (R2000 or whatever version).

First, if you wanna get unique definition of TagSets in DWG you need to use Shared Cells with attached ItemTypes. This makes sense because Shared Cells are similar to how Blocks are implemented in ACAD.

The current issue is with exported Tag values. In order to examine what is happening I created a TEST CASE.dgn. 

In DGN all Cells are placed as SharedCells and attached ItemTypes with values in all properties.

In the left column (101-104), a TextNode is added when I attach an ItemType to each SharedCell with different settings whose property have to be visible as a TextNode.

In the right column (105-108), I added TextNode for each property manually after attaching ItemType to the SharedCell. This can be done with TextEditor and FieldType from Element Properties.

When I export TEST CASE.dgn to TEST CASE.DWG most of the values are not the same. Only when I export SharedCell with all FieldType visualized as TextNode that element (105) is exported correctly. I suspect that other elements are having problems with parsing the values because correct values are all concatenated in one property (TOCKE) and other properties seems that copy values from first element.

What I need is to export all the values regardless they are associated with TextNodes or not. 

I suspect that there may be one or more bugs.

I didn't yet rise ServiceRequest and I would kindly ask colleague on this forum to give me an advice.

Kind regards,

Mladen

TEST CASE files:

MS_TEST_CASE_SharedCells.dgn

MS_TEST_CASE_SharedCells.dwg

Now I'm using Microstation CE U17 10.17.02.61 to create Cells, ItemTypes and Export to DWG. Also checking Tag values in DWG.

BMap V8i (SS4) 8.11.09.887 I use only to check unique TagSet of exported DWG

Your test DGN file shows that you might have your columns reversed, i.e. (101-104) are placed with text display turned off except the first value, and (105-108) are placed with all values turned on?  The 101-104 text nodes are combined by Item Types and Text Fields in such a way that is not supported in ACAD.  You have opted to display only the value of the first item.  After you have attached the item, a text node is created that is supposed to represent the first item's value only, but then as you have described, you have used the text editor to append text fields that point to the item values you have turned off for display.  This capability does not exist in ACAD - you can't alter the display of an attribute with a different value.  The value you entered for an attribute is what must be displayed in a view.

Your (105-108) items are comparable to ACAD attributes - each of them has its individual display control.