Is it possible to filter the accounts in LCR based on the owner information?
Pinned topic LCR filters: can we use person attribute (erpersonstatus) on account LCR
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-26T03:23:38Z at 2013-02-26T03:23:38Z by Preetha
Re: LCR filters: can we use person attribute (erpersonstatus) on account LCR2013-02-15T09:35:42ZThis is the accepted answer. This is the accepted answer.Not to the best of my knowledge. What you would need to do is have a lifecycle filter of (eraccountstatus=1). In your operation you can then put a script node to get the owner for each account and only process those where the erpersonstatus=1.
And vice versa you could have a person lcr which checked personstatus and then in the operation check the status of all the persons accounts.
If you need any explanation on how to do this let me know and I will expand upon the response.
The downside to both of these is that your lifecycle rule will select more entities to process than you would wih so there will be perhaps many ldapsearches needing to be performed to retrieve the information. The overhead will depend on how many account meet the criteria. You just need to be careful when you schedule it for.
Re: LCR filters: can we use person attribute (erpersonstatus) on account LCR2013-02-25T23:28:59ZThis is the accepted answer. This is the accepted answer.Hello goonitsupport,
Thanks for the reply.
I just figured out that it's possible. The filter is
Re: LCR filters: can we use person attribute (erpersonstatus) on account LCR2013-02-26T02:42:32ZThis is the accepted answer. This is the accepted answer.
- Preetha 060000V1WX