Skip to main content
Question

Why do cell values go blank in table view when I sort them?

  • December 10, 2018
  • 6 replies
  • 19 views
S

Hello All,

When I sort the table view of an inspector in FME Inspector the values go blank and the cell value returns an error. I don't mean "Null" or "<Missing>" values, i mean they're completely blank and it suddenly removes values from every cell in the table.

Relative to the image below, Inspector "Combined" is the problematic table. It is the output of combining a geodatabase point feature class with output from a workflow. Inspectors "A" and "B" display and sort fine, it's only when I sort the combined one that I have issues.

Any help is appreciated!

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

6 replies

erik_jan
Contributor
Forum|alt.badge.img+22
  • erik_janContributor
  • Contributor
  • 2179 replies
  • December 10, 2018

Could it be that the 2 sources for combined do not have the same attributes (and not have the attribute you try to sort on)?

That seems like a plausible cause for an error.

S
  • succip
  • Author
  • 2 replies
  • December 10, 2018

Could it be that the 2 sources for combined do not have the same attributes (and not have the attribute you try to sort on)?

That seems like a plausible cause for an error.

Thanks for your reply.

In that case wouldn't the features without those attributes just list as "<Missing>" or null?

erik_jan
Contributor
Forum|alt.badge.img+22
  • erik_janContributor
  • Contributor
  • 2179 replies
  • December 10, 2018

Could it be that the 2 sources for combined do not have the same attributes (and not have the attribute you try to sort on)?

That seems like a plausible cause for an error.

Yes, you are right.

I tested it and could not break it this way.

daveatsafe
Safer
Forum|alt.badge.img+19
  • daveatsafeSafer
  • Safer
  • 1637 replies
  • December 11, 2018

Hi @succip,

What version of FME are you using? I seem to recall this happening in some of the betas for FME 2018.

S
  • succip
  • Author
  • 2 replies
  • December 11, 2018

Hi @succip,

What version of FME are you using? I seem to recall this happening in some of the betas for FME 2018.

Hi @DaveAtSafe,

I'm using 2018: "2018.0.0.2 (20180414 - Build 18301 - WIN32"

That said, this morning I realized the issue was my CoordinateSystemSetter from earlier in the script. I'm not entirely sure why it affected the table output, but now that it's removed it works fine. Maybe it is a 2018 issue, I haven't yet got around to reproducing it in 2017.

Cheers,

Paolo

daveatsafe
Safer
Forum|alt.badge.img+19
  • daveatsafeSafer
  • Safer
  • 1637 replies
  • December 11, 2018

Hi @DaveAtSafe,

I'm using 2018: "2018.0.0.2 (20180414 - Build 18301 - WIN32"

That said, this morning I realized the issue was my CoordinateSystemSetter from earlier in the script. I'm not entirely sure why it affected the table output, but now that it's removed it works fine. Maybe it is a 2018 issue, I haven't yet got around to reproducing it in 2017.

Cheers,

Paolo

Hi @succip,

I found the problem report for this issue, and it was fixed in FME 2018.1. Are you able to update your FME to the latest release? You can download it from www.safe.com/download.

Community Stats

32,083
Posts
121,831
Replies
39,718
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.