Continuing from an email thread with @Mark.
In my original email to Mark, I wrote, "At the start of the year, I built a fitness app (ArenaStrength) for a client. The app uses user-specific fields (checkboxes) which users check off when they have completed particular workouts. My client just told me that some of the users have duplicate rows in the tab that is used for the profile. She is interested in de-duping the user sheet, but is concerned that users will lose their progress (user-specific checkboxes) and perhaps their profile. The duplicate rows all have the same email address, but the user tab also has a column for RowID, and those RowID’s are different for all the duplicate rows.
Do you have any suggestions on how to de-dupe the user list while ensuring that the user-specific fields are kept? Is this data all bound together by the Row ID, user’s email, or something else? "
Mark replied with the following, “User-specific columns are bound to the user’s email address (and the row IDs in the sheet where they live), so de-duping the user profile rows wouldn’t affect them at all. If you’re not using the row IDs in the user profile sheet in the app for relations or something else, that shouldn’t be a problem, either.”
Thanks for the reply Mark. Moving the conversation to the community forum as requested. One follow-up question: The sheet used for the user-profile has columns for both email and RowID. Each duplicate row has a different RowID, but the same email address. The client is concerned about the subscribers needing a new PIN AND losing their user-specific data (their progress through the exercise programs, as described above). I believe that, based on your reply, I would have to know which Row ID is associated with the user-specific data to keep that row and preserve the data. Is that correct? If so, how do I know which row ID to keep?