Skip to main content
September 7, 2022

IC Member Filter for Accounts

  • September 7, 2022
  • 2 replies
  • 0 views

Trying to use IC Member Filter on the account dimension to limit the entities that can be used at IC partners for the account.  Does anyone know the syntax needed; I don't see any documentation on it.  I tried a list of just one entity member name and that didn't work. 

2 replies

September 8, 2022


EricOsmanski_0-1662659283508.png

 

October 16, 2024

Just a followup question to this.  I am trying to use IC Member Filter on an entity to only allow a select few entities to be used as partners along with the None partner.  It doesn't seem to work.  I can only get IC Member Filter to work when applied on an account which doesn't help me as I want this to be set at the entity level as every entity will have different select partners they can book with.  Thoughts?

October 16, 2024

I've had very limited success with the IC member filter.  My suggestion would be writing the Conditional NoInput rule from hell if this was needed.  You could also catch this in a confirmation rule, which would stop wrong IC combinations from loading.

June 5, 2024

Anyway I could do E#NorthAmerica.Base?  Or would I be better off writing a conditional input rule on this account?

June 7, 2024

Using the Constraint settings EricOsmanski showed is always preferable to conditional input rules.

June 7, 2024

Preferred solution for performance.  I agree.  For dynamic flexibility, though, I beg to respectfully disagree.  If for instance, a customer added an intercompany entity below E#NorthAmerica, then they would also have to manually update the IC filter.  A correctly written noinput rule, however, should be able to pick up the fact that a new entity has been added to E#NorthAmerica and automatically update without any additional manual steps.  All this is theoretical, seeing how I've yet to attempt to write said noinput rule.