Trimble Business Center

I am having some issues with TBC-GIS Module.

1. Decimal Values - Not respecting set properties.

See attached  "ScreenShot-1". Decimal numbers are set to zero in the FXL file. Yet there are two decimal values by default for "Object ID". This is true for all numerals. How to set to Integer only? and enforce it.

2. After creating properties, I exported to ESRI Geodatabase file. When opened in ArcMap there are additional attributes not needed by the client. How do I eliminate these unwanted attributes from exporting? (See attached *.xlsx files)

3. Is it possible to Edit the fields marked in red rectangles in attached "ScreenShot-2". If yes, how?  or is it possible to have a Macro do this?

For convenience I am attaching the *.vce file.

Hi Saif,

Do you already have an existing GDB container from your client? Are you trying to re-creating all the attribute fields in TBC? If possible, could you share the original GDB (just the blank schema would be sufficient) so we can look closer into it?

Thank you.

Rui Wu

My starting point is the ESRI Shapefiles (Attached). The client wants a GDB

output with certain parameters.He has supplied an MS Access file. The

Attribute Definition is defined by the client and cannot be changed. The

Schema comes from the Shapefiles.Challenge is to write a GDB file with

defined Attribute Definitions.

On Fri, Jan 10, 2020 at 10:42 PM rui_wu@trimble.com <trimble@jiveon.com>

Hi Saif,

Is the attached GDB what you're looking for? You can use ArcMap to make this conversion, which will take care of the ObjectID issue you saw in ScreenShot-1. The ObjectID field is a reserved ArcGIS field that is not supposed to be edited. Meanwhile, all the schema (attribute configurations) will be maintained.

The issue you saw in ScreenShot-2 is caused by the limitation of the shapefile format. When you use .SHP format, you could only use 10 characters to name a field (space included), that's why you see truncated field names. Now it's converted to GDB, the limitation is gone, so you can manually edit the field names in ArcGIS. 

I would suggest you pass the attached GDB to your client, let them modify the field names wherever is needed. Then you can get a copy of the new GDB from them, create a feature code library for your field data collection purpose, and at the end of the day, pushing new data back their GDB. Is this the workflow you're looking for?

We do have some videos explaining the complete workflow when you have an existing GDB to work with. Please let me know if they help: 

GIS Data Synchronization in TBC - 01. Data Connection - YouTube 

GIS Data Synchronization in TBC - 02. Schema Conversion - YouTube 

GIS Data Synchronization in TBC - 03. Data Harvest - YouTube 

Thank you.

Rui Wu

Thanks.

I have seen the videos.

I have now got a new GDB file. (Attached as a zip file here).But when I import it to TBC, I have several unwanted Attributes. I have created a fxl file unchecking all unwanted Attributes. That is good in I have now no need to edit the fxl file for the number of Characters. 

Still, it is a qusestion as why when in "ObjectID" properties of the fxl file, the number of decimals is set to zero, the value defaults to 1 when I type in the Object ID field giving me a non-integer value (Such as 242.0) by default.

Can I get a solution outside of ArcMap / ArcGIS. 

Hi Saif,

Indeed the decimal place is not working as expected. And it doesn't work only when the decimal place is set to 0.

If you follow the typical GIS workflow and convert the FXL from an existing GDB, then the ObjectID field should be automatically hidden, so there shouldn't be any issue.

But if you need to create your own ObjectID field for some reason, try to use Integer instead of Numeric type for that attribute. It will force TBC to get an integer.

Meanwhile, I will report the behavior as a bug. Thank you for reporting it!

Rui 

Thanks. 

I wish to draw your attention to Point 2 in my original post.

Also, When I export the GDB files from the TBC, Two additional layers namely Points and Lines are created by default. Any way I can avoid this.

Thanks again.

Hi Saif,

If you use the GIS Module, you should be able to Write Features to GIS. This method will not create two generic layers.

But if you have to export a new GDB from the Export command, then you cannot exclude the generic layers. Also notice that you will loose the schema with this method. That's why the GIS Module workflow is highly recommended as it provides a more streamlined workflow and avoid all these issues. 

Hope it helps. Thank you.

Rui