Book a Demo

Author Topic: Diagram Filter appears to do opposite  (Read 4542 times)

tonyabs

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Diagram Filter appears to do opposite
« on: July 05, 2018, 03:09:23 pm »
Have been trying to use diagram filters but they appear to do opposite to documentation.
If I select action to "hide" and select an 'objectType' then activate the filter, it hides everything except the objectType I selected. This looks to be the opposite of what the documentation describes. Is there something that someone may have set in configuration somewhere that could cause this?
Cannot combine filters while it works this way as they cancel each other out.
Using Enterprise Architect Ultimate v12.1.1229 (Desperately waiting for IT to upgrade it)
We have a shared, Oracle-based repository and too many with 'admin' rights, so all sorts of odd things could have occurred.

Sunshine

  • EA Practitioner
  • ***
  • Posts: 1353
  • Karma: +121/-10
  • Its the results that count
    • View Profile
Re: Diagram Filter appears to do opposite
« Reply #1 on: July 05, 2018, 04:04:39 pm »
Afraid thats just how the filters work.
If you want it to work the other way try "not equal to' instead of 'equal to' when defining the filter.
Happy to help
:)

tonyabs

  • EA Novice
  • *
  • Posts: 8
  • Karma: +0/-0
    • View Profile
Re: Diagram Filter appears to do opposite
« Reply #2 on: July 05, 2018, 05:02:29 pm »
If I read it carefully you are right - normal behaviour. Though cannot do inverse. Tried the 'Not Equals' but oddly it does not seem to recognise the list the same way as 'Is one of'.
It also appears that anything MDG based if very hit an miss - I have a diagram with both Archimate and BPMN objects and it becomes very cryptic to find ways to hide say just the Archimate objects.
Looks like a dead end  :(

Nizam

  • Prolab Moderator
  • EA User
  • *
  • Posts: 320
  • Karma: +15/-2
  • Model Sharing - Simplified
    • View Profile
    • Professional Model Collaboration
Re: Diagram Filter appears to do opposite
« Reply #3 on: July 06, 2018, 10:58:50 am »
Maybe its not aligning with your previous tools experience, but you must be able to achieve most usecases with the current behavior, in the example in your case define a filter for BPMN objects (of course you have to define the stereotypes one by one, cannot be like stereotype like 'BPMN%") and if you enable that will disable all but BPMN.