Best Of

Great, that should work just fine. Now when you export these point samples, you can also include the header fields for each sample row in the export file. Then these shared XYZ values will repeat for each row, and any other header field you might want to include. To achieve this - on the general export dialog there's a "Include header fields with table data" option that will union the header fields with the sample rows. Otherwise the export template lets you set this up as well.

Thanks David, this is very helpful and clarifies the configuration and underlying logic very well.

In our case, the objective is to associate multiple samples with a single logical field point, with all samples sharing the same XYZ captured at the point/header level. Based on your explanation, disabling the “limit entry to single row” option in the sample table is exactly what we were looking for.

Thanks again for the detailed explanation and for sharing best-practice considerations.

Hi David. Tested the case. It seems I was trying to login with internet connection which leads to the online login page. I have turned off all the connection and logged in without any issues. Thank you very much for the detailed explanation. 🤩

Yes, you can configure MX Deposit to allow multiple samples for the same point/header. In fact, if you are currently limited to just one sample row in the sample table - then somebody has explicitly configured it that way. In the activity configuration, you can expand the sample table (or any table) and there is an option called "limit entry to single row". If this option is enabled, then you will only be allowed to enter a single row (or sample) in that table. If you disable this option, it will let you add multiple rows (or samples) in that table.

The trick with point data is the coordinates. The coordinates are captured in the header, which then enables all the coordinate validation and transformation options. So in your case, are you looking to capture different XYZ values for each sample in the same table? Or will the XYZ live in the header, and the sample table has just sample IDs? We have seen customers add their own XYZ columns in sample tables, which works fine - but you won't be able to transform those coordinates on export. You would just need to make sure that what you capture in the table is in the coordinate system that you are always working in.

Would be good to understand if these ideas/solutions work for you, or if there's anything you think would work better here. We have tossed around the idea of having a sort of special "coordinate" table that has built-in northing/easting/elevation/CRS columns that would also make use of the coordinate transformation features on export. That would let you capture different XYZ values for different samples in the same table, then the point header could just be some logical grouping of samples.

Thoughts?

Hi Amaraa - you can definitely log in to the mobile app while in offline mode. The only precondition is that the user must have signed in at least once on that device while it was online, so that the mobile app has a record of that users email. When the app is in offline mode, you would click the "Sign in with Seequent ID" button as usual - but at that point, it will not direct you to the Seequent ID login page because that page is not accessible without Internet. Instead - the app will present an offline login page where you can enter your email and password. Then as long as you enter an email that has signed in previously (i.e. not a new user signing in for the first time) then it will let you in. Also remember that only assigned out drill holes will be available in offline mode, as that data has been downloaded to the device. The scenario you have described is supported by the app - so if it isn't working please reach out to Seequent support (support@seequent.com) and we can investigate.