The M-Files Community will be updated on Tuesday, April 2, 2024 at 10:00 AM EST / 2:00 PM GMT and the update is expected to last for several hours. The site will be unavailable during this time.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How does M-Files determine that an external object is new on Quick Refresh?

On a couple of occasions, we have had problems with the database that populates an external object of development applications in our Planning Department.

The result is that the overnight full refresh will automatically delete M-Files external objects it no longer sees in the external database.

Subsequently, the external table is fully re-populated.

If I try to undelete these external objects, the INSERT INTO statement I have configured for this external object generates a primary key violation, blocking the undelete.

Having destroyed the deleted objects instead, I would expect M-Files to re-populate the external object from the external database.

This doesn't always work.

So my question is:  how does M-Files know when an external record is a new object, especially on a Quick Refresh?

and:  how should we address this deletion and re-population problem in the future?