• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
Since moving to v.18 in production when updating the global portion of the patron record (setting a block for example) we get the following error message:

"Bor ID already has personal profile. In order to udate profile, personal profile needs to be deleted first."

We have always loaded all our patrons w/a profile of ALEPH. This profile has to be deleted to make any global
change. How has the profile field changed?

The drop down window next to the profile field looks to be a list of patron record keys.

Resolution:
The drop down window next to the profile field is a list of z61_rec_key's -- many of which *are* personal profiles, matching the z303_rec_key.

The problem occurs only with converted patrons. (In v18 when the patron creates a personal profile, the system changes the z303_profile_id to their z303_rec_key -- so that it matches the z61_rec_key of the personal profile which has been created.)

No change is going to be made to the program to accommodate the converted patrons. If you want to prevent Circ staff from having to delete the personal profile in these cases, you can instruct them to paste the patron ID into the Profile field (replacing the "ALEPH") when they get this message.

• Article last edited: 10/8/2013