Skip to main content
Solved

FME Desktop 2020.1 - Sorting Issue & Shift-F6 not working as intended

  • October 6, 2020
  • 2 replies
  • 21 views

sameer
Contributor
Forum|alt.badge.img+18

Current Version: FME(R) 2020.1.2.1 (20200909 - Build 20624 - WIN64)

 

Hello

 

1) Since upgrading to 2020.1 regardless of build version, the sorting function is no longer working and therefore causing issues. (Tick / Untick box does not work)

 

FME_Desktop_Sorting Issue

 

2) "Run-to-Selected" no longer working as it should. it carries on translating the entire workspace.

 

FME_Desktop_Shift-F6

 

PS: Not discarding the fact that it might be a localised issue.

 

Thanks

Sameer

Best answer by chrisatsafe

Hi @sameer​ ,

 

Thanks for reporting this, I'm going to convert this thread to a case and file an issue report in our system to have the sort functionality corrected as I'm able to reproduce this.

 

On the Run to Selected side of things, although the connection is disabled the feature count will still appear on connection - this simply shows how many features exited the AttributeManager's output port. In this case, the translation will run up to the Inspector and the feature count will appear on the connection between the AttributeManager and FeatureJoiner but features will not arrive at the FeatureJoiner (and beyond). If that is not the case, please install the latest build (20632).

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.

2 replies

chrisatsafe
Contributor
Forum|alt.badge.img+2
  • Contributor
  • 606 replies
  • Best Answer
  • October 14, 2020

Hi @sameer​ ,

 

Thanks for reporting this, I'm going to convert this thread to a case and file an issue report in our system to have the sort functionality corrected as I'm able to reproduce this.

 

On the Run to Selected side of things, although the connection is disabled the feature count will still appear on connection - this simply shows how many features exited the AttributeManager's output port. In this case, the translation will run up to the Inspector and the feature count will appear on the connection between the AttributeManager and FeatureJoiner but features will not arrive at the FeatureJoiner (and beyond). If that is not the case, please install the latest build (20632).


sameer
Contributor
Forum|alt.badge.img+18
  • Author
  • Contributor
  • 63 replies
  • October 15, 2020

Hi @sameer​ ,

 

Thanks for reporting this, I'm going to convert this thread to a case and file an issue report in our system to have the sort functionality corrected as I'm able to reproduce this.

 

On the Run to Selected side of things, although the connection is disabled the feature count will still appear on connection - this simply shows how many features exited the AttributeManager's output port. In this case, the translation will run up to the Inspector and the feature count will appear on the connection between the AttributeManager and FeatureJoiner but features will not arrive at the FeatureJoiner (and beyond). If that is not the case, please install the latest build (20632).

Hi @chrisatsafe​ and thanks for looking into it for me. The "Run To Selected" is working as it should but I'm inclined to recommend that this behaviour, by design, should change as can be misleading when dealing with complex workspaces. Can't wait for the guys to apply a fix for the "Sorting" issue.