Updating Out-of-Date Seequent Evo Objects

This topic describes how to find out what Seequent Evo objects in a project have changed and how to update changed objects. This topic is divided into:

See the Leapfrog Works/Seequent Evo Data Flow topic for an overview of importing, publishing and reloading Evo data.

Out-of-Date Indicators

When an object imported from Evo is updated in Evo, a status indicator will appear in the Leapfrog Works project tree alongside the object that has changed. For example, here a drilling dataset is out-of date:

Clock icons at the right of the project tree rows, marking Evo objects that are out of date, with the count of out-of-date objects in the Project Tree header

See Object Status Indicators for more information on the different status indicators.

Manually Checking for Updates

You can also check for updates by clicking the button at the top of the project tree and selecting Check For Updates:

Check For Updates in the menu beside the clock counter in the Project Tree header

Once the check is complete, the number of objects that are available for update is indicated in the project tree title bar (A). Click on the button to select all of the out-of-date objects in the project tree (B):

After checking for updates, the header count (A) and the highlighted rows with clock icons (B) show which objects need updating

Refreshing Out-of-Date Objects

To refresh a single out-of-date object, right-click on it in the project tree and choose Reload Latest From Seequent Evo:

Reload Latest From Seequent Evo in the right-click menu of an out-of-date drillhole object

In some cases, you will be given the choice between reloading the latest object or choosing a version from the project history:

Choosing Reload From History opens the Reload Table from Seequent Evo window, listing the published versions of the table to reload

To refresh multiple objects at once, select them in the project tree. Then, right-click on them and choose the Reload Latest From Seequent Evo option:

Reloading several out-of-date Evo objects at once by selecting them together and choosing Reload Latest From Seequent Evo

Some objects imported from Evo will include an associated colourmap. When these objects are reloaded, the colourmap will also be reloaded, if it has changed.

In some cases, reloading simply makes new data available in the form of additional rows or columns. At times, reloading can also result in name changes to existing data objects. In these cases, a message will be displayed indicating the changes that will result.

Some source data modifications can result in significant changes to the project:

  • When a column is removed in Seequent Evo, on reloading in Leapfrog Works the column is deleted and any downstream objects associated with the deleted column are also deleted.
  • When a column type is changed in Seequent Evo, on reloading in Leapfrog Works the old column is deleted and a new column with the new name is added to the table.

In these cases, a message will be displayed that identifies the differences between the current local version and the remote version, along with what objects in the project will be affected by reloading the data. In this example, the selected version of a table of points in Evo is missing a data column that the current local object contains. The validation warning message indicates that if the reload process is completed, the data column will be removed from the local Leapfrog Works project.

The Reload Points window comparing the current and reload versions and warning that a missing Cu column will be removed

If you do not wish to lose any downstream data, click the Import as New button to import the object as a new object. This will result in two different versions of the object in the project tree; you can then compare versions and decide which one to use.

There is also a Cancel button in case you prefer not to reload the data from Evo at this time.

Objects Deleted in Evo

When objects are deleted from an Evo workspace, they will appear as out-of-date in the Leapfrog Works project. When you update that object in Leapfrog Works, a message will be displayed saying the object has been deleted from Evo. Click OK to dismiss the message.

If you wish to republish the object to Evo, then publish it to Evo as a new object. You can then choose whether to publish it to the workspace it was deleted from or to a different workspace.

Effect on Dependent Objects of Deletions

When reloading from Seequent Evo, it is possible that elements will be deleted as they no longer exist in the object in Seequent Evo. Other objects in Leapfrog Works that referenced that object will be affected. For example, consider drilling data in a borehole object. A borehole could be referenced in a collar query, or it could be projected onto a section. If that borehole is updated, those objects referencing the borehole will reference the modified borehole. However, if the borehole has been deleted from the data in Seequent Evo, when Leapfrog Works reloads that object from Seequent Evo, there is no longer valid data to reference. Any dependent objects, such as a filter or a section, will remove the reference to the missing object.

As a result, even if a future version of the data in Seequent Evo restores the object that had been deleted, such as the borehole in this example, the references from other dependent objects to the restored data are not automatically restored, as the reference was broken by the earlier deletion and reload. It is necessary to manually reinstate such object references.