Having read the documentation, I can’t see any means of handling a common use case associated with assignment of access profiles when multiple accounts are correlated.
How can I assign the access profile only when target accounts which have a given field in a non-blank or non-null state?
The configurator only allows “equals”, “does not equal”, and “contains”. Perhaps there is a way to say “equals *” - but the documentation does not describe any way to do this.
As far as I know, there isn’t an operator to check for null or non-empty values in the Multiple Account Options. The available operators are limited to Equals, Does Not Equal, and Contains, as you mentioned.
One possible workaround, although it requires some additional processing, is to populate a dedicated account attribute based on your account selection logic. You can then use that attribute in the Multiple Account Options criteria. For example, if you populate an attribute such as isPrimaryAccount with values like Yes or No during an After operation rule (after aggregation) , you can simply configure your access profile to select the account where isPrimaryAccount = Yes.
Hi @rmccoy-unum - unfortunately that is the limitation. You can setup a dedicated Identity Attribute with Transform logic to return a simple true /false based on the field. you would also need to use an accountFilter to make sure you are getting the data from the right account.
dang - it would sure be nice if it did work. like for example, if there was a means of passing a string that would check for null or empty. Like $null$. It seems like fixes which address simple shortcomings that could affect everyone would be better than generating lots of identity attributes in every tenant. I know there’s the idea board - but it doesn’t feel like a feature request board.