I'm sure this worked before.
As soon as I add a filter, in this case a level filter, the report returns no rows. If I remove the filter all rows are returned.
Have I missed something? I'm I getting crazy?
I've attached a small example.
Regards,
Krister
3750.test.dgn
Krister Surell said:As soon as I add a filter, in this case a level filter, the report returns no rows
I built the filter using the General property of elements rather than a property of line elements...
That results in selection by level as you require. The end result in the level filter is the same as yours (Lines.Filter = Level 3): that is, you can't tell that I achieved the filter using a different approach. Success depends on the route taken to create the filter, which is absurd...
Lines.Filter = Level 3
Regards, Jon Summers LA Solutions
Whats version are you using? I've tried both Element Common and the Line properties without success.
/Krister
Owner consultant at Surell Consulting AB
Krister Surell said:If I remove the filter and recreates it it stops working
Perhaps Mangesh.Shelar or his team can throw some light on this peculiarity?
It is not only levels that fail. As soon as I set any filter the result is 0 rows.
There was a bug filed by our QA BUG 963330. I fixed this a month ago for the upcoming release. As of now, both of your files work well on my box. Still, I have asked our QA to verify.
Thanks,
Mangesh
Answer Verified By: Krister Surell
Thanks. I've tried deleteing the upf and used different workspaces to see if the problem was caused by something in my environment without success. For now I can use fence in the report and toggle levels in the view.
Hi Mangesh,
This is working fine at my end as well.
Abhay
Abhay Gore said:This is working fine at my end
Thanks for your response, but that doesn't help us much. We users have published versions of MicroStation, not internal builds.
I apologies for the confusion.
I verified this issue in MS 10.17.01.58 and it is found fixed there.
And MS 10.17.01.58 is already released version. Please see the attached video for your reference.
By chance is there a hot fix for OpenRoads Designer to solve this issue?
OpenRoads Designer 2022 R1 | MicroStation CE Update 17 | ProjectWise CE 3.434
Turns out if you update/add the report filters in the latest version of MicroStation, ORD will be able to use them.
Hi Jack,
The next release of OpenRoads Designer will consume MicroStation 10.17.02.454 which contains the fix mentioned above that is available in MicroStation CONNECT Edition Update 17.17.01.58.
I recommend following the OpenRoads Communities Announcements Forum for updates on when the next version will be released.
Tamicca SellarsProduct Manager I