Constituent find should also search maiden names (like it searches partners and aliases). One should NOT have to make the maiden name an alias - it's a wasted entry since it already exists in it's own field.
This is a business rule that can easily be set up to automatically put maiden name into alias without anyone having to do anything. I like having it separate - especially with the business rule turned on it makes life much easier.
Howard, can you take a look at the KB linked below and see if since you make it automatic, (not wasted steps to enter as a alias manually) if this works for you?
No it does not handle this. That's why I'm asking. We do use a Business Rule to automatically add Maiden names as an alias. As stated, that is wasted information since it already exists on the maiden name field - why does it hnow have to be there twice (maiden name field and alias field). We just need search to search Maiden Name like it searches partner name, alias, ...
How can a field that populates into another field not reflect changes made in the first field. We did not know that when we made a change in the maiden name field that it was not corrected in the Alias drop down. When we searched by maiden name, the record did not show up. Very frustrating. Please make maiden name a search field.
This is a business rule that can easily be set up to automatically put maiden name into alias without anyone having to do anything. I like having it separate - especially with the business rule turned on it makes life much easier.
use this KB solution to set up your business rule if you do not already have it set up. https://www.blackbaud.com/kb/index?page=content&id=BB123434&actp=search&viewlocale=en_US&searchid=1358978355838
Howard, can you take a look at the KB linked below and see if since you make it automatic, (not wasted steps to enter as a alias manually) if this works for you?
No it does not handle this. That's why I'm asking. We do use a Business Rule to automatically add Maiden names as an alias. As stated, that is wasted information since it already exists on the maiden name field - why does it hnow have to be there twice (maiden name field and alias field). We just need search to search Maiden Name like it searches partner name, alias, ...
How can a field that populates into another field not reflect changes made in the first field. We did not know that when we made a change in the maiden name field that it was not corrected in the Alias drop down. When we searched by maiden name, the record did not show up. Very frustrating. Please make maiden name a search field.
I have to agree with Howard. The "solution" provided in the KB does not directly correlate to the feature request.