This occurs when the user that logged in to fill out the form is currently linked to another record in The Education Edge database. When this warning message pops up the options are yes and no. 

There are a few scenarios which which can prompt this error. 

For both Scenarios, let's say the Parent's name is Jack and the Applicant's name is Jane. Jack has an Individual record within The Education Edge and is linked between NetCommunity and Education Edge.

Scenario 1: The option for Applicants Only is selected under the Login tab of the OLA form
Online Admissions Form showing the Login tab and the Apply As Applicants only
Scenario which likely happened: The user, Jack, logs into the NetCommunity website. When they fill out the information, they want to fill it out for the an applicant, Jane. However, when the Apply as Applicant is selected on the form, the form is assuming the user logged in is the applicant.
Correct steps for future reference: When Apply is set to Applicants Only, the applicant should be logging in with their unique username. If another user, other than the applicant fills out the form, you'll receive the error in the plugin.
 
Scenario 2: The option for Applicants and selected relationships is selected under the Login tab of the OLA form
Online Admissions Form showing the Login tab and the Apply As Applicants and Selected relationships displayed
Scenario which likely happened: The user, Jack, logs into NetCommunity. When they start the Online Admissions form, they will be prompted for "Applying as". If the user, Jack, chooses Applying as An applicant, see screenshot below, the form assumes that Jack is the applicant, even if they enter Jane's applicant information. 

Apply as Applicant, user view
Correct steps for future reference: When Apply as Applicants and Selected relationships is selected on the form, the user logged in should specify the correct response. In this scenario, Jack should choose Applying as A parent or relative of the application (this text may vary slightly), and then choose their relationship to the applicant. Screenshot example below.
Applying as a relationship

Scenario 3: Login is not required under the Login tab
Login not required
Scenario which likely happened: If Login is not required under the Login tab, but this error still occurs,  it indicates the user was logged in, but they filled out the Applicant information. Using our Jack and Jane example, Jack was logged into NetCommunity, but filled out the applicant information for Jane. 

Correct steps for future reference: If no log in is required, the form can either be filled out while not logged in, entering the applicant information. If a user logs in, even if the form does not require a log in, the applicant should log in to fill out the form. 

Results of the Scenario which likely happened:
Once the form comes into the plugin, we see the error message because the plugin wants us to double check whether the person who was logged in, Jack, should be continued to be linked to their existing record, or if the credentials should be applied to the applicant, Jane.

If Yes is clicked:
The applicant will now have the online login information that was used to login for the form to be filled out. The original record, usually the parent record, mentioned in the warning message will have no username or password on the record.

If No is clicked:
The applicant record will be generated with no username or password on the record. The original record, usually the parent record, mentioned in the warning message will keep the login information.

NOTE: You can deter the form from confusing the applicant and the parent by deselecting the option to allow the form to be filled out as an applicant. By requiring Login and choosing Selected Relationships Only, it will deter the form from thinking the person logged in is the applicant. 
  1. From the NetCommunity website, Navigate to Site Explorer>Forms
  2. Click the Pencil icon of the form to edit
  3. Click the Login tab
  4. Mark the box for Require Login
  5. Under Apply as, chose Selected Relationships Only
Apply as: Selected Relationships Only
  1. When finished, click Save

*NOTE: If selecting Yes or No triggers an unhandled exception check the matching record of the applicant, following the article linked.