Just wanted to complain a bit and maybe provide some answers to those that run into this. In pre-connect era we could get an element by ID using GetElementByID, even if it was inside of a cell. That's not the behavior now, instead you're returned a cell object that contains that sub element. In my opinion this is a bug, although I'm sure someone can come up with a reason why that's the behavior. So if you do need to get to the subelement by ID, you should probably check if the result is a cell and it likely doesn't match your ID, and then perform a scan on that cell object for any sub or sub-sub elements with that ID.
Hi Viktor,
it has been discussed sooo many times, why not to search for GetElementByID at first?
As far as I know defect #655078 was created for this issue.
With regards,
Jan
P.S. Please respect and follow the best practices! With buggy API (especially VBA / COM one), when in every version some bugs are fixed and new one are introduced (or more often, a regression appears), it's critically important to exactly specified used version.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi Jan, it did feel like deja vu, I'm pretty sure even I asked a similar question a year or two ago when i first started to port to Connect. But surprisingly the search did not return relevant results at the top, so i decided to add one more squeak.