Can't save data: Partner ... is currently banned.

Gergerg

Dear All,

I'm a relatively new user. Today I opened some records, saved data elsewhere, made highlights on images, and edited some data, usually typos, misreadings or wrong estimates of dates. At the last one, I couldn't save my modification. I got an error msg. like "Data is not saved, please reload". I reloaded and made the mod. again, I clicked Save and got the same result. Then I checked the console of my browser and found this:

{"errors":[{"code":108,"msg":"Partner … is currently banned."}]}

It was the response for the data pack my browser sent when I clicked Save. At the pos. of … I got a 4-digit ID, I guess that's my ID in the system.

What happened? Is there a limit to the number of documents I can open, data saves I can make, or stg?

Thanks for any info.

MandyShaw1

Hello @Gergerg.

There is no 4-digit number identifying users of FamilySearch as far as I know. FS has millions of users.

Could you clarify what change you were trying to make to what profile, index entry, etc., please? A screenshot would be useful (avoiding living person information).

Also, what browser are you using?

Péter3183

Hello MandyShaw1.

I made nothing special. The person who tagged a Registry page miscalculated the DOB of one of my long-dead relatives based on his date of death and age, and I wanted to change that. Link:

https://www.familysearch.org/ark:/61903/1:1:QVB6-QQ62

These are death records from 1925 (i.e., there's no chance of any living person being on the list).

If I try to modify the estimated year of birth I still get the error message:

The strangest thing is that I can modify anything else but not the est. YOB. I'm banned from doing that.

The response from the server: {"errors":[{"code":108,"msg":"Partner 1398 is currently banned."}]}

I run the latest Chrome on up-to-date Win 11 Pro for Workstations.

Thanks for any help!

Áine Ní Donnghaile

It seems the poster is editing record indexes, not the FamilySearch Family Tree.

@Péter3183 @Gergerg Have you created 2 usernames here in the Community? That will be confusing for you and for us.

Partner in this case may refer to the record custodian. The term partner is used in some instances to refer to other websites or repositories holding the record.

And banned may simply mean there is communication difficulty between the system of the partner and FamilySearch.

You might try using a different browser or clearing your FamilySearch cookies in your preferred browser.

MandyShaw1

Or, given that one specific metadata item seems to be blocked, the agreement between the record custodian and FS does not support FS-side user editing of that item.

The error message is probably a generic one, so the 'try again later' bit may or may not apply.

De-Community-software-mangled URL: https://www.familysearch.org/ark:/61903/1:1:QVB6-QQ62

I am not sure there's anything further that can be done to help you here, but flagging @Ashlee C. in case there is.

Be aware that many Records have index metadata that is incorrect in some way, for many, many reasons, and that the metadata is not intended to be a transcript, merely a search aid.

MandyShaw1

Here's the underlying Persona data in case it helps at all:

label	text
EVENT_COUNTY_ORIG	Szabolcs
EVENT_DATE	1925. július 9.
EVENT_DATE_ORIG	9 Júl 1925
EVENT_DAY_ORIG	9
EVENT_MONTH_ORIG	Júl
EVENT_PLACE	Szabolcs, Magyarország
EVENT_PLACE	Tiszaszalka, Bereg County, Hungary
EVENT_PLACE_ORIG	Tiszaszalka, Szabolcs
EVENT_TOWN_ORIG	Tiszaszalka
EVENT_TYPE	Death
EVENT_TYPE_ORIG	Death
EVENT_YEAR_ORIG	1925
FS_SORT_KEY	0000000004528483_00074_00003_0000102292619104_000
PR_AGE	8 months
PR_AGE_MONTHS_ORIG	8
PR_AGE_ORIG	8
PR_BIR_YEAR_EST	1924
PR_BIR_YEAR_EST	1925
PR_NAME	Keresztesi Lajos
PR_NAME_GN	Lajos
PR_NAME_GN_ORIG	Lajos
PR_NAME_ORIG	Lajos Keresztesi
PR_NAME_SURN	Keresztesi
PR_NAME_SURN_ORIG	Keresztesi
PR_SEX_CODE	Unknown

You will see that the underlying data has two different values for PR_BIR_YEAR_EST, both of which appear on the FS Record display, though you need to hit the little down arrow to see the 1924.

I don't fully understand the JSON structure re these birth dates, but I think the 1925 is set as the birth "date" while 1924 is just one of potentially multiple birth "altDates".

Péter3183

@Áine Ní Donnghaile "Have you created 2 usernames here in the Community? That will be confusing for you and for us.". No, I'm sorry, we are son (Gergő) and father (me, Peter). Sometimes we share a PC and forgot to check who was logged in. We will try to pay attention and not to confuse anyone.

@Áine Ní Donnghaile & @MandyShaw1 The final solution was this: the birth year was in a Calculated field. When I added the real birth year, I got the error message. As soon as I removed the Calculated field and added a Year field (as the record has only the age of the deceased in months, not the full date of birth that I know from elsewhere), I was able to record the right data.

Thanks for your help.