Trimble Business Center

I've discovered what i believe is a bug with TBC 2025.10.9324.19130.  Using connected workspace, I've brought in a .job file from a TSC7 with a T04 file at the same time.  The points in this file need to be processed PPK.  These points also have attributes as determined in a .FXL file.  The attributes are not there though after processing field codes.  If I bring in ONLY the .job file, the attributes are there.  Here's what I've tried:

1) .job and .t04 brought in at the same time, processed feature codes on both, no attributes

2) .job and .t04 brought in at the same time, processed feature codes on only the .job, no attributes

3) .job and then the .t04 brought in after, processed feature codes on only the .job, no attributes

4) .job brought in, processed feature codes on the .job, attributes are there!

5) .t04 brought in, processed feature codes on the .t04, no attributes.

6) .t04 brought in, then .job brought in, processed feature codes on only the .job, no attributes.

7) .job brought in, processed feature codes on the .job, brought .t04 in, attributes are there!

The only workflow that works is to bring in the .job, process  feature codes, THEN bring in the .t04 file and process baselines.  If the .t04 file is present at any point before feature codes are processed, you will lose all your attributes (other than the feature code itself).

Hello George,

Only thing I can think of is a t04 file brings in a coordinate on import. This coordinate likely has no description but carries higher weight than an observation. If you disable or delete this coordinate the attribution should repopulate from the observation.

I've discovered what i believe is a bug with TBC 2025.10.9324.19130.  Using connected workspace, I've brought in a .job file from a TSC7 with a T04 file at the same time.  The points in this file need to be processed PPK.  These points also have attributes as determined in a .FXL file.  The attributes are not there though after processing field codes.  If I bring in ONLY the .job file, the attributes are there.  Here's what I've tried:

1) .job and .t04 brought in at the same time, processed feature codes on both, no attributes

2) .job and .t04 brought in at the same time, processed feature codes on only the .job, no attributes

3) .job and then the .t04 brought in after, processed feature codes on only the .job, no attributes

4) .job brought in, processed feature codes on the .job, attributes are there!

5) .t04 brought in, processed feature codes on the .t04, no attributes.

6) .t04 brought in, then .job brought in, processed feature codes on only the .job, no attributes.

7) .job brought in, processed feature codes on the .job, brought .t04 in, attributes are there!

The only workflow that works is to bring in the .job, process  feature codes, THEN bring in the .t04 file and process baselines.  If the .t04 file is present at any point before feature codes are processed, you will lose all your attributes (other than the feature code itself).

Hi Kyle,

When you say "the attribution should repopulate from the observation", do you have to re-run Process Feature Codes for the attributes to show up on the Point?  Or do the attributes get populated/stored on the observation (during Process Feature Codes), and are just "displayed" on the Point based on what source data has the highest weight?

(apologies if this is obvious, I'm not as familiar with geospatial workflows)

Hello George,

Only thing I can think of is a t04 file brings in a coordinate on import. This coordinate likely has no description but carries higher weight than an observation. If you disable or delete this coordinate the attribution should repopulate from the observation.

I've discovered what i believe is a bug with TBC 2025.10.9324.19130.  Using connected workspace, I've brought in a .job file from a TSC7 with a T04 file at the same time.  The points in this file need to be processed PPK.  These points also have attributes as determined in a .FXL file.  The attributes are not there though after processing field codes.  If I bring in ONLY the .job file, the attributes are there.  Here's what I've tried:

1) .job and .t04 brought in at the same time, processed feature codes on both, no attributes

2) .job and .t04 brought in at the same time, processed feature codes on only the .job, no attributes

3) .job and then the .t04 brought in after, processed feature codes on only the .job, no attributes

4) .job brought in, processed feature codes on the .job, attributes are there!

5) .t04 brought in, processed feature codes on the .t04, no attributes.

6) .t04 brought in, then .job brought in, processed feature codes on only the .job, no attributes.

7) .job brought in, processed feature codes on the .job, brought .t04 in, attributes are there!

The only workflow that works is to bring in the .job, process  feature codes, THEN bring in the .t04 file and process baselines.  If the .t04 file is present at any point before feature codes are processed, you will lose all your attributes (other than the feature code itself).

Hello Quan,

You shouldn't need to rerun the process feature codes for the attributes to exist, but you would need to rerun the process codes for anything you expected to happen to that point based on said attributes. Post feature code processing it will display based on what TBC has decided as the ultimate driver of the feature code and attribution that was recognized.

How TBC handles points can be counterintuitive at times based on my own empirical evidence. I like to think of points as folders and the coordinates and observations being within the folder. When there is conflicting information odd things can happen.

What I wonder is happening is the coordinate from the T04 file has a feature code embedded in it. This feature code likely cannot bring attribution along (Don't have a good example to test from my own data), but I will infer it performs similar as importing a CSV. In the case of a CSV import attribution is skipped or does not persist due to limitation of how TBC handles this form of import.

Any data from the JOB file whether via observation or its own coordinate can have both the feature code as well as the attribution.

Based on the tests run by George without the influence of the T04 and processing the Job file attribution is there so it seems likely it is tied to a lack of attribution in the T04 and TBC holding the "empty" attribution of the T04 verse the "filled" attribution of the job file.

In the case of the CSV example above once the coordinate from the CSV is disable the attribution from the jobfile is then able to come through upon recomputing the project.

To further complicate things you could have multiple observations that have different feature coding or attribution stored under one point, but in TBC we can only see one at a time. If you rename the observations to different points or disable the other observation the per observation attribution can come through. Discovered this when field crews unintentionally store geographical distinct features under the same point number accidentally.

Hi Kyle,

When you say "the attribution should repopulate from the observation", do you have to re-run Process Feature Codes for the attributes to show up on the Point?  Or do the attributes get populated/stored on the observation (during Process Feature Codes), and are just "displayed" on the Point based on what source data has the highest weight?

(apologies if this is obvious, I'm not as familiar with geospatial workflows)

Hello George,

Only thing I can think of is a t04 file brings in a coordinate on import. This coordinate likely has no description but carries higher weight than an observation. If you disable or delete this coordinate the attribution should repopulate from the observation.

I've discovered what i believe is a bug with TBC 2025.10.9324.19130.  Using connected workspace, I've brought in a .job file from a TSC7 with a T04 file at the same time.  The points in this file need to be processed PPK.  These points also have attributes as determined in a .FXL file.  The attributes are not there though after processing field codes.  If I bring in ONLY the .job file, the attributes are there.  Here's what I've tried:

1) .job and .t04 brought in at the same time, processed feature codes on both, no attributes

2) .job and .t04 brought in at the same time, processed feature codes on only the .job, no attributes

3) .job and then the .t04 brought in after, processed feature codes on only the .job, no attributes

4) .job brought in, processed feature codes on the .job, attributes are there!

5) .t04 brought in, processed feature codes on the .t04, no attributes.

6) .t04 brought in, then .job brought in, processed feature codes on only the .job, no attributes.

7) .job brought in, processed feature codes on the .job, brought .t04 in, attributes are there!

The only workflow that works is to bring in the .job, process  feature codes, THEN bring in the .t04 file and process baselines.  If the .t04 file is present at any point before feature codes are processed, you will lose all your attributes (other than the feature code itself).

I've discovered what i believe is a bug with TBC 2025.10.9324.19130.  Using connected workspace, I've brought in a .job file from a TSC7 with a T04 file at the same time.  The points in this file need to be processed PPK.  These points also have attributes as determined in a .FXL file.  The attributes are not there though after processing field codes.  If I bring in ONLY the .job file, the attributes are there.  Here's what I've tried:

1) .job and .t04 brought in at the same time, processed feature codes on both, no attributes

2) .job and .t04 brought in at the same time, processed feature codes on only the .job, no attributes

3) .job and then the .t04 brought in after, processed feature codes on only the .job, no attributes

4) .job brought in, processed feature codes on the .job, attributes are there!

5) .t04 brought in, processed feature codes on the .t04, no attributes.

6) .t04 brought in, then .job brought in, processed feature codes on only the .job, no attributes.

7) .job brought in, processed feature codes on the .job, brought .t04 in, attributes are there!

The only workflow that works is to bring in the .job, process  feature codes, THEN bring in the .t04 file and process baselines.  If the .t04 file is present at any point before feature codes are processed, you will lose all your attributes (other than the feature code itself).