Add fields to Relationship Import in Constituent Update Batch
Oftentimes employment data comes in after the Constituent has been established. You can import a business relationship via Constituent Update Batch but you cannot import values for the employment history such as Job Title, Department, etc.
-
Guest
- Jul 9 2015
- Will not implement
| Organization Name (Please enter full organization name) | Deakin University |
| Reported Version | 3.0 |
Related ideas
I'm also very surprised there is no standard batch to update employment information. This should be part of basic functionality of CRM.
am surprised this is still not a basic functionality - we have to update these manually each time which is a complete WASTE OF TIME
When people currently import employer relationships (business primary) that seems to break the link between the two fields of relationship and job title-details etc. if you add the relationship manually as well as job title details before saving, where that link is intact it automatically end dates the previous job title and details, along with the former business-primary relationship, and the loss of this functionality puts me off importing the employer relationships.
To make all details importable, how would the data need to be arranged? Surely we could make it so the job title fields appeared when the relationship being added is employer, and they could then be populated in one header file and left blank for importing other relationship types?
This job title-no import issue is the same as the Region field for addresses isn't it? Or can those be updated at the same time as addresses?
Desperately need this...
This is a very manual process and see no reason why this cannot be delivered by Blackbaud in a batch template.