I will be as detailed as possible. The error happens to multiple records at random times, on random days. The record in question (today) is highlighted in yellow.
There is a Table connected to a Dataset. The Dataset is linked to a database collection with permissions for Anyone to create. Dataset mode is set to Read Only. The table is located on a Wix Dashboard page for the Client to view and manage the records, as needed.
The screenshot of the live database collection was taken (by me) today and shows that the record in question was last modified on Sept 22 . The record shows Number of 3 People .
The screenshot on the top left corner was taken (by Client) yesterday and the record was showing Number of 4 People . That screenshot is from the dashboard page located on the Wix Dashboard on Owner account .
The screenshot on the top right corner was taken (by me) today and the record is showing Number of 3 People . The screenshot is from the same dashboard page located on the Wix Dashboard (on my account) as Contributor .
Summary:
Same record. Has not been modified since Sept 22 . Connected directly via Dataset. Different numbers on different days within the last 24 hours.
It would be great if a Corvid Dev Team member could take a look at this for me please.
Ahhh. The information is still mismatched.
There are only 3 Sarah records as seen on live database screenshot, and the date, name and number are mismatched.
@code-queen Iâd guess (itâs hard to see from the screenshots), that the highlighted row on the top-left screenshot is equivalent to the 2nd row in the top-right screenshot and to the 3rd row in the bottom screenshot.
Could the date mismatch be due to time zone difference?
The tour database collection will be updated when someone joins or when an employee gets assigned to the tour. When form is submitted it enters the record in 2 database collections. 1 collection is called âtourâ and the other âparticipantsâ.
So for that one record, the original participants are 3 and no one else shows up. This is all so confusing. I wouldnât even know how to track if a person deleted a field from one database collection ⌠cause if they would have changed it manually in the last day or two ⌠wouldnât the updated date be different? I donât know. I will have to check it out later. The dates didnât match either ⌠they were all mixed up.
Who as access to that participants dataset, just yourself or your client as well?
Do your clients have access to change anything in a dataset?
As when you mentionâŚ
âThe tour database collection will be updated when someone joins or when an employee gets assigned to the tour. When form is submitted it enters the record in 2 database collections. 1 collection is called âtourâ and the other âparticipantsâ.â
This indicates to me that the forms user inputs are submitted into the two separate datasets of âTourâ and âParticipantsâ.
Then as youâve said when somebody joins or employee gets assigned etc, then the âTourâ dataset will get updated, hence the reason for the different updated dates if that original bottom pic in your post was the âTourâ dataset.
However, as youâve said as well, you have nothing updating that âParticipantsâ dataset, only when the form is first submitted, so any alterations to the tour is not being recorded in that âParticipantsâ dataset.
Is there not a way that you could create an admin form or client use only form that they have to use if there are any needed changes, so that it checks all the datasets and updates the required fields in all if needed?
Know it will be extra work for yourself, however, as youâve said, you have got nothing updating your âParticipantsâ dataset, so everything else gets changed and that stays the same.
Or is it simply a case, that the clients do have access to all the datasets and that they have simply not used their own initiative and only changed the numbers in the âTourâ dataset and not the âParticipantsâ dataset too?
Also, as for the mismatch of dates and times etc, could that just be as J. D. simply stated already with the time zone differences, is that set to their own local time etc.
@givemeawhisky Client is owner of site - so they still have access to Database via Dashboard. He is also same time zone as me.
Another screenshot he sent me was that 2 people filled out the form within 1 minute of each other. 2 different tours, 2 different people ⌠and somehow their ânamesâ were saved in the database in the wrong tour. Which is odd ⌠it does not make any sense. The form is connected via the dataset also â the names are not âinsertedâ via code.
Okay, so that does rule out a few possibilities that it could have been.
However, the fact that the users are filling in the forms and simply submitting it via a submit button and not being done through code, then it should all be inserted correctly as the user entered themselves as each record should be inserted separately.
The only thing that I can see that is happening here, is as that when you say two seperate users fill in the same form and then just happen to submit it at the exact same time, then those records are not being kept separate and are getting muddled up, so that they end up as you say with things mixed up.
If they are trying to write to the dataset at the same time and so some fields are getting mixed up as one submit tries to do one action like insert user input to one field, whilst the other submit tries to do the same thing, then in theory you would expect that one would wait for the other one to finish, stack up so to speak and not simply try to write to the dataset with immediate effect.
Are you able to view the site and datasets at the same time as your client and get the client and somebody else to fill out the form on two seperate computers and then have them both submitted at exactly the same time?
At least you will be able to observe for yourself what exactly is happening when they submit at the same time and see if it happens again.
If it does, then youâve narrowed down the issue and you just need the help of those wise Wix Devs to come to your rescue and to get it sorted.
@yisrael-wix Can yourself or another Mod look at this or pass it on so it can get sorted quickly, one drink on me if you do
