Item Types Report

Hello Bentley community,

I want to integrate in a report the connection of two elements which share a geometric constraint (2D drawing).

In the report tree I do not find the geometric constraint.

For my example. I have a line (or complex chain) connected to two cells by a geometric constraint of the "coincidence" type (2D drawing).

I want to retrieve in my line report the information located in my cell (here cell name).

Below is a picture, which speaks more than words.

To make it simple is it possible to recover an item associated types of element that share a geometric constraint ?

Regards

Cyril B. a french user.






Parents
  • Hi Cyril,

    I want to integrate in a report the connection of two elements which share a geometric constraint (2D drawing).

    I think it's a misunderstanding how Item Types report works.

    They are designed to report Item Types data attached to elements (in a "per element way") and also element data, that are available in supported (Item Type / EC) format (like color...). The reports, as far as I know, are not able to work with any other type of data or relations.

    To make it simple is it possible to recover an item associated types of element that share a geometric constraint ?

    No, because geometric constraints data are not supported.

    But I think you can post new Idea. I can imagine a specialized Expression (give me this type of data) can be added. To convert constraints itself to supported format, so they will be available in the report definition, is probably more complicated.

    Regards,

      Jan

  • Hi Jan,

    I think it's a misunderstanding how Item Types report works.

    They are designed to report Item Types data attached to elements (in a "per element way") and also element data, that are available in supported (Item Type / EC) format (like color...). The reports, as far as I know, are not able to work with any other type of data or relations.

    - so, we can report data only if element data we want to extract are literally stated in "Expression types and syntax examples" (in Help)?

    I have similar problem. My goal is to report cell names in whole model, together with XYZ origin of each cell and item types attached to each cell. As cell origin is not available in Expression, I am thinking of generating two separate reports:

    - one with elementID/cell origin

    - second with this.GetElement().ElementID and other data stored in Item Type

    and then somehow link those data together (Excel?), based on Element ID.

    Can you imagine of making it in an easier way?

    No, because geometric constraints data are not supported.

    But I think you can post new Idea. I can imagine a specialized Expression (give me this type of data) can be added. To convert constraints itself to supported format, so they will be available in the report definition, is probably more complicated.

    - or the only easier way might be after some enhancements?

    Regards,
    Wojtek

    --

    Best regards, Wojtek

    SW: Promis.e 08.11.13.96/23.00.00.46

  • Hi Wojtek,

    Can you imagine of making it in an easier way?

    Do you mean something like this?

    The report contains:

    • Cell ID (element id)
    • Cell name (empty item in the list is "grouped elements cell")
    • X + Y + Z coordinates, split into separate columns
    • Properties "Name" and "ID" from Item Type attached to the cell.

    The situation can be more complicated depending what properties you want to report and also whether only one item type or more are used.

    With regards,

      Jan

  • For this, you need to use *Add related Items* option during selecting Items.

    For e.g. I have created two lines and attached same ItemType to each one of these.

    While selecting Items for reporting, I have selected *Include these Items* as *Lines* and *Related Item* as my ItemType (Door) via ElementHasAttachedItem. 

    So that, in report definition you can see:

    Now, I have selected column as:

    So, here Line properties and ItemType properties will be treated as one row. Because, Line class and ItemType properties are *JOINed*.

    However, when you select *Include ItemType * as *Lines* and *ItemTypes (Door)*:

    Report cannot relate these two distinct EC entity. Hence, each result will be shown as different row:

    Hope, this helps.

    Thanks,

    Mangesh


    This is a test

  • Thanks Jan,

    Do you mean something like this?

    Yes, exactly that.

    I have followed tip from Mangesh Shelar below. After configuring "Included Items" in Report in that way:

    the report seems to be able to join both data together.

    The situation can be more complicated depending what properties you want to report and also whether only one item type or more are used.

    I will make some more test using that method and I will share any unexpected behavior.

    Regards,

    Wojtek

    --

    Best regards, Wojtek

    SW: Promis.e 08.11.13.96/23.00.00.46

  • Typically they are elements (with or without ItemTypes attached), but can be e.g. model or even file(s). The input data can be further filtered and enhanced by other properties including relationships (again, as long as they can be interpreted by internal mechanism).

    Hello,
    I advanced a little on the treatment of a report associated with several elements of the plan. It work by using the "named groups" but that remains laborious...
    The solution of a drawing constraint seems to me simpler.

    Also I can not get on my report line the total of several same items values, it seems that it manages only one data on report related items. Maybe you have a solution for that ?

    Thx Again!

    Cyril B. / French User

  • Also I can not get on my report line the total of several same items values, it seems that it manages only one data on report related items. Maybe you have a solution for that ?

    Please follow the rule "one topic per one post"! Otherwise every discussion will become messy.

    Plus, when you will search this forum, you will find several similar discussions, where the idea of "sum functions" were discussed already including link to the idea posted by Jon.

    With regards,

      Jan

Reply Children
No Data