Update of Handle Profile Changes - Bad Idea!

Samantha Insel

While updating the look of profile changes was great, removing very important columns from view was definitely not. Why would you ever remove UserID, HostID, UserFirstName, and UserLastName is beyond me. You should always have a sort of ID available for anything when it comes to data.


This update has made my job more difficult and I don't appreciate it AT ALL.

Susan Ott

Samantha Insel‍ I am totally with you. We haven't run Connect RE in over 3 weeks because of this "update". There's no way to sort through the Parent persona and eliminate the Parents of Candidates. I don't care about Candidates and Parents of Candidates until they become a member of our community. Plus it adds thousands of additional updates. If the host id was shown, I could at least tell the difference between current parents and candidate parents but as you mentioned, they left that very important piece off. Also thought I could at least filter by custom date and eliminate most but for some ridiculous reason, you can't select records and acknowledge them when you have a date filter. What is the point? We have an open support ticket and I requested an update yesterday but have heard nothing. We were told 3 weeks ago that a hot fix would be issued because this was an unintended consequence of the re-design. Still waiting.

Coco Parham

When our Advancement Office ran connect RE, they did not get any candidates or Parents of Candidates. I just want to be able to select them to speed up the process when handling profile changes.


Thanks,


Coco

Angie Addison

Hi Samantha, while we did display userid in the user header we did you're correct, drop it from the export. That's been corrected at this point (as well as adding back host id). Thanks for the feedback!

Angie Addison

Hi Susan (and all), the ability to handle changes when a filter is applied to the view is releasing tomorrow. You'll be able to select one, multiple or all and update as handled. Hope that helps!