Finish your profile
-
As we've been testing, we're now getting users that have already completed the 'finish profile' fields and are being asked to update them again on each login. We haven't added any new profile fields to capture, so I'm not sure how it's occurring. The only thing I can guess is that since we're now updating some of the registration fields via the "Update a User Registration" API, perhaps that is triggering it to think something is new (even though the fields themselves aren't changing, just some values)? We do this when a user wants to update a profile field from our application. Is that a possibility, and are there known mechanisms that trigger this that I could investigate further? Thanks in advance!
-
Hmmm. This behavior would be triggered if you had added new required fields, but it sounds like you aren't doing that.
Is there any chance you are inadvertently nulling out required fields when you are updating the registration using the API?
You might be doing that if you are using the PUT/Update operation and not sending the entire registration object.