Hi! I’m trying to run a report on my model - but for some reason it’s adding the “Definition Name” in front of some of my “Entity Names” . Anyone have experience fixing this?
Share the model so we can see how you’ve set it up.
Test Model_purged.skp (6.6 MB)
Here you go!
Can you show a screen shot of your report format and the report? Which of these objects are showing this?
Perhaps @colin has some thoughts on this. I does seem odd although I don’t think that grouping by Definition Name should exclude it from the Entity Name. One thing you could do for the time being is use Entity Description instead of Entity Name.
It appears (in your image) that you have the report set to Group by Definition Name.
@DaveR Thank you, I’ll try the Entity Description!
@DanRathbun Yes, but why would that add the definition name in front of my entity name? When the definition name is already it’s own column?
Not all instances of the two definitions are named, so when you group by definition it would show the different named instances as a set of ‘deduped’ strings under entity (try setting the Entity name to ‘a set of concatenated strings, deduped with count’ and you see how many instances have a name)
The ones without a name are indicated by the definition (103549 and 104667)
Quickest way is to name the instances that don’t have a instance name yet the same as the others.
@MikeWayzovski OH thank you that’s interesting! How would I set the Entity name to ‘a set of concatenated strings, deduped with count’?
You can change that in the settings per attribute (click on the icon that looks like a gear when editing the report)
Thank you all!! This has been very helpful, switching to “Entity Description” instead of “Entity Name” worked well!
Now I’m running into problems when I group objects, the components show up fine in the report when they are ungrouped, but as soon as I group them or place a component within a component, they don’t appear in the list the same way. I’ll attach my new model here! Anyone know a way to get around this? We use groupings all the time and I’m trying to set up the files in a way that we won’t have to manually edit the components in each drawing:
Test Model_3.skp (7.1 MB)
The first file had an embedded report which was set to ‘only selected’ and level 2. One needs to realize that the level is determined in the model hierarchy, regardless of the selection.
(Model = level 0, then followed by objects in the model (level 1) which can have nested levels inside (level 2, 3 etc.)
Note that level 3 objects are actually reported, because level 2 is the level that is ‘grouped by’
Have outliner open and check what you see:
So, going forward, you must have a good knowledge as of how your model is structured, and any colleague that starts grouping messes up the saved report when set to a certain level, with the risk of missing information.
The file has more than 10 levels, and grouping by level generates a report where level 1 is followed up by level 10,11,12,etc instead of 2,3,4, etc…
So one needs to decide at what level the most important objects reside and have a strict manner of organizing for it to work. (the less levels, the better)
You can select ranges and individual nesting levels.
For example 1-2, and 4 in the image.
If you only have prized components that are relevant for your quote, you could group by price and have the filters set to all levels.
In this case, there would only be 4 rows.