Saving record blanks out/erases all visable row data.

DLJonsson

Well-known member
We open our main database as classic grid in DadaBik.

We are looking for records where the County/Parish field is empty.
On quick search we select County/Parish : [is empty].

We add a County into the County field and press <Next>

Then clicking <Previous> we see all visible data from the form has been erased
including the new data we entered into the County field.

Releasing the Quick Search filter we double check the record and its confirmed
all of rows visible at time of the 'Save' have been erased.

We confirm via our SQL client software using
Select * from aw_main where aw_item_number='18'
that all visable columns in the row edited have been blanked/erased.


Could this be a problem with Safari browser?
Should we be advised not to edit when using quick search filters?
Or?

Any suggestions appreciated.
 

eugenio

Administrator
Staff member
Hello I am not able to reproduce this issue, it seems impossible to me that records are DELETED. Could you try to reproduce the behaviour in one of the online demo?

Best,
 

DLJonsson

Well-known member
The record/row wasn't deleted, only the columns visible in the edit form were impacted.

I've moved the workstation and user to using Chrome rather than Safari and the
issue hasn't repeated.

For now I need to write it off as local issue with Safari on that workstation,
doubt if it is repeatable. Safari did have timeout issues on that machine and
was sometimes hanging on Dadabik. Since moving to a fresh install of
Chrome haven't been able to repeat the issue.
 

eugenio

Administrator
Staff member
Very strange, I would say it should be impossible for this to happen unless you click on "save" but let me know if it happens again.

Best,
 

DLJonsson

Well-known member
Looking closer at the table today, I see that the problem was the data entry person deleted
the content of a field that was being used as a filter in the view they were using.

Drilling into the table today looking at the 'missing' record and a previous backup
it is clear now this is/was the problem.
 

DLJonsson

Well-known member
That is correct the record was simply excluded from the view
once the field being filter in the view was changed and no longer
matched the condition in the view where clause.

Later auditing the table I found the row complete and un-effected except it was missing the column which was
manually blanked out - the view in question required - that specific field/column to be (not empty and not null).

I hope that makes sense, not a Dadabik issue rather an issue caused by the filtration of the view the form was
accessing.
 
Top