November 2017

This article outlines the major enhancements introduced to MX Deposit as part of an update performed on Nov. 24, 2017.

New Features

Drill hole map view

Drill holes can now be viewed as interactive points on a map. The drill hole landing screen in the web app has an alternate map view option. When you click on the map view icon, the current list of drill holes will be plotted on a Google map using the WGS84 geographic coordinate system. Points are colour-coded based on the drill hole status, and users can click on a point to view information about the drill hole such as hole number, current progress, assigned user. Users can also click through to any table using the Go To menu right from the map view. If there are any project boundaries defined, they will also be displayed on the map.


How to use it:

  1. Click on the Drill Holes module in the main navigation pane
  2. Select the project and apply any filters you want to refine the list of drill holes
  3. Click the Map view icon to the right of the quick filters to change the view 
  4. The filtered list of drill holes will be plotted on the map
  5. In map view, standard Google map pan/zoom tools can be used

NOTE: If you do not see any points on the map, or the points are not in an expected location – there may be an issue with the grid definition that you are using, specifically the conversion parameters to WGS84. If this is the case, please contact support at

Project boundary validation

Drill hole collar coordinates can now be validated against a defined project boundary. As part of the Project configuration, you can define a geographic boundary in the form of a Polygon that defines an area that all coordinates should fall within. When a user inputs a new collar coordinate, and a project boundary is defined – if the coordinate falls outside of the boundary then the user will receive a validation message. The goal is to validate the real-world location of each drill hole to ensure that users are correctly inputting coordinate values. NOTE: This feature will only be enabled if a project boundary has been defined. If there is no boundary, then no validation will occur.


How to use it:

  1. With a project boundary defined, all existing coordinate points will be tested against the boundary
  2. When a user inputs a new coordinate that is out of the defined boundary, a validation message will appear
  3. Coordinates that have been flagged as out of the defined boundary will be highlighted in the Header tab  boundaryValidation3.png

Project & activity user permissions

Module access can now be controlled for every user and for every project / activity combination. Previously, all users could access the activity data in all modules (including the Assay & QAQC module). Now, you can limit access to each activity dataset for each user. By default, all admin users have access to all modules, and all non-admin users have access to all module except the Assay & QAQC module. Permissions are set at the activity level within each project.


How to use it:

  1. Within the project configuration section, the Assign users step – you can click on user initials in the Activity, or click the more menu beside the Activity name and select Edit user permissions userPermissions2.png
  2. In the Edit User permissions screen, all users that have been granted access to the current activity will be listed on the left, and each user set of permissions will be listed on the right
  3. To grant or deny access to a module for a user, make sure the user is selected on the left and simply toggle the module access on or off userPermissions3.png
  4. By default, users don’t have access to the Assays & QAQC module. You will need to enable this module if a user requires access. NOTE: The Assays & QAQC module is for the import of lab certificates and the releasing of results. Changing this module access does not affect the viewing of released sample results in the drill hole module.

Web app improvements

Data grid refactor

The data grid (tables) in the MX Deposit web app has been completely overhauled to handle performance and scaling issues when viewing large data sets. The new data grid loads much faster, scrolls better, and is generally more responsive – even when loaded with large data sets. You should notice a significant improvement when viewing tables in the web app.

New validation engine

As part of the data grid refactor, the validation engine has also been rewritten. Previously, intervals were always validated against its “neighbors” (previous and next intervals). As such – it was a hard requirement that intervals had to be in order. This has changed so intervals are now validated against all intervals in the same table. You will no longer received validation messages that intervals are out of order. Also, when you roll over a cell that is in error, you will get more information that will give you what you need to resolve the issue.


Sort order

As previously mentioned, intervals that are out of order are no longer considered invalid. The system will still highlight intervals that are out of order to notify the user that this scenario exists.


The table status bar at the bottom of the screen will summarize how many intervals are considered out of order.


If you click on the number, you will be prompted to sort the rows. Performing this action cannot be undone.


Improved navigation

Several improvements have been made to streamline how you navigate around a table. Some of the features include:

  • Scroll to top / scroll to bottom shortcuts in the table status bar 
  • The system now remembers your scroll position when you navigate between tabs.
  • Keyboard navigation has been improved to support all common keyboard controls for navigating a table (e.g. tab, arrow keys, shift + tab, space bar, enter key, etc.)
  • If you are using the fill-down functionality, and the fill-down action will overwrite any existing data, the system will now prompt you to confirm that you want to complete this action 
  • The Header now appears as a tab alongside the other tabs (vs. previous implementation as a link to view header) 
  • In new rows, the [From] value is now auto-populated based on the previous rows [To] value 

Mobile app improvements

New validation engine

The changes described above for the web app validation engine have also been implemented in the mobile app to provide a consistent user experience.

Improved navigation & performance

The following improvements listed above have also been implemented in the mobile app:

  • Scroll to top / scroll to bottom shortcuts
  • Remember scroll position as you navigate between tabs
  • Fill-down overwrite confirmation
  • Auto-populate the next [From] value based on the previous rows [To] value

Also, several performance improvements have been made to improve the responsiveness and scalability of the data grid when dealing with larger data sets.

Finally, the mobile app will now remember user emails for those users that have successfully logged in at some point. This provides a streamlined login experience so that users don’t have to input their email every time they log in to the app.

Adjustable column widths

Users can now manually adjust the width of any column to maximize the content that is displayed. Column settings are saved on each device so that the user only needs to resize the column once.


Sync process improvements

Several changes have been made to how the mobile app synchronizes data and files (images) are included. Each file is now individually synchronized separate of any data that also needs to be synchronized. This ensures that data is synchronized first and is never jeopardized in the case of an error when synchronizing files.



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk