The same was sent to our rep along with the source fxl and job files. A ticket was submitted to Trimble who has responded that they have added this issue as a potential bug to be corrected in a future update. It'll probably be a while before that's addressed and released, though. I was hoping someone had been able to make a modification that I'm not aware of to fix this issue.
If anyone else is experiencing the same problem, there are a couple workarounds. Obviously, they are less than ideal as they involve either multiple, additional steps or modification of the fxl.
- A custom export (PNEZD w/ Attributes) out of Trimble Access on the controller DOES produce the correct date format.
- If any modification (uncorrected v. corrected control, instrument height adjustments, etc.) needs to be made, you would need to process them in TBC, export a new job file, import to the controller, finally export a point file from Access with the correctly formatted date attributes.
- Replace the Date attribute type with a String attribute type.
- This opens up possibility for field crews to incorrectly enter dates (fat-finger, incorrect format, etc.)
- The majority of the feature definition libraries that we use are client-supplied, and I don't like making modifications to those files for fear of attribute type or value mismatches when our files are loaded into their data models.
For now, we'll probably stick with manual or scripted line-by-line edits, depending on file sizes.
------------------------------
R.P. Schaller
------------------------------
Original Message:
Sent: 09-14-2022 15:45
From: James McWha
Subject: Date Attribute Formatting Issue On Export
I would recommend reporting this issue to your local Trimble Dealer. Please include some same data and the fxl file.
------------------------------
James McWha
Original Message:
Sent: 09-14-2022 07:33
From: R.P. Schaller
Subject: Date Attribute Formatting Issue On Export
Wondering if anyone has some insight and a fix to the problem below.
- In our project fxl, the "CROSSING_DATE" attribute for code "UTIL" is set up with a format of MM/DD/YYYY.
- This is verified by checking the programming in the fxl where the "AnnotationFormat" attribute has a value of "d" which is the MM/DD/YYYY format.
- The attribute value for the point feature in TBC contains the correct MM/DD/YYYY value & formatting.
- Using a custom export format definition to include attribute values, the Export Preview function shows an incorrectly reformatted date value.
- This same, incorrect formatting is present in the resulting exports.
- Since much of our workflow is built around utilization of comma delimited files, this requires line-by-line correction, either manually or scripted, of these formatting errors.
------------------------------
R.P. Schaller
------------------------------