#EDA Relationships & Affiliations0 discussing

Hi Elena, I will let some of my EDA colleagues chime in with more information, but essentially how you want to track your constituent's association with another educational institutions is really up to you. Affiliations might be better suited for an active relationship; for example if a graduate student is part-time adjunct teaching at a neighboring college you may have an active affiliation. Education History does no utilize affiliations as you can see here in the updated diagram - https://powerofus.force.com/s/article/EDA-Entity-Relationship-Diagram

As for your Primary Education Institution when still an applicant, this would also be up to how you prefer to handle this in your org (if I'm understanding the question correctly). If it is the Primary Institution they are applying to then it could be an affiliation. Here is a bit more info on Education History as well - https://powerofus.force.com/s/article/EDA-Education-History

Hi Tridib, I'm kind of having trouble understanding your questions, which may be why the response rate is less than wonderful.

#1 for instance-- That seems like you'd get that answer simply by creating a test lead and then hit the Convert Button. That will show you the answer to that question, no?

#2. Opportunity records need an ACCOUNT, not necessarily a contact. I'm not really sure what you mean by "it has the provision to create a new Administrative Account record." Opportunities in Salesforce must have accounts. Often, if you create an opportunity with a Contact, the system will give the opportunity that contact's account. Maybe that's what you're seeing? Hard to tell.

#3 - Sorry, that again I do not understand your question. My understanding of HEDA, and I'm kind of new to it, is that you create a contact/student, and then you go to the related list called Program Enrollment, and you click on new, and that is what starts you on a path to enroll that student into that program. However...Much of what I've learned about how HEDA works is by taking a test contact, and trying to fill up all the fields and objects and connections that that student might need. That gave me a sense of the structure.

There are two Trailhead modules that are able to help you. Also, there is documentation. https://powerofus.force.com/s/article/EDA-Documentation

Also, it's good to keep in mind that many of the North American folks who might be able to help you are between 10 and 13 hours earlier than you are. So when you are getting late at night, some of us are just getting up.

I think this could be accomplished with a Process Builder/Flow. Let's start with what you're doing before we can prescribe a potential solution. What I am reading is:

1. An account exists
2. You create a Contact and specify the Account from Step 1 as that contact's Account
3. Expected outcome would be that after making that Contact a "child" of that Account, you want to see an Affiliation created?

What types of contacts are we talking about? Are these any kind of contact that gets added to an Account. The reason I ask is because when you create an account, if you don't specify the account it belongs to it should create an Account type of your choosing (based on EDA Settings) and assign the contact to that account. If you're asking for that to create an affiliation with the same account as well, I would think we can do that as a flow as well (but I digress).

In the larger scheme of things, you should be able to create a Process Builder process (might have to be a Flow but we can get there) that looks at the Account you've associated with the Contact and create an Affiliation object for that account and that contact. You'd have to tell the process to populate the status, start/end dates etc. as well.

You could also do this with your own triggers as well but process builder and flow have a lower barrier to entry if you're not a developer. (It's been awhile for me since I'ver leveraged process builder and flow so I may have some holes here). Also, I want to be sure I fully understand the use case as well.