Solved

FME Desktop Build 22304: Moving attribute fields up and down through the “attribute manager” is slow,

  • 25 March 2022
  • 6 replies
  • 2 views

Badge +5

 

FME Desktop Build 22304: Moving attribute fields up and down through the “attribute manager” is slow,

 

I couldn’t figure out why moving attribute fields up and down is slow

 

 

 

Clip_305 

Is this by design?

icon

Best answer by jamal 6 August 2022, 18:04

View original

6 replies

Userlevel 2
Badge +10

Hi @jamal​. This was a known issue that was fixed as of FME 2022.0 - Build 22308. Let me know if you are still having any issues.

 

Thanks,

Dan M

Badge +5

The FME is upgraded to Build 22311 but the issue persists to exist.

 

In addition to that, why drag\\drop of fields is not applicable here? It’s much more decent to move them up and down by drag\\drop than working with arrows in particular cases

 

 

Clip_337

Userlevel 2
Badge +10

The FME is upgraded to Build 22311 but the issue persists to exist.

 

In addition to that, why drag\\drop of fields is not applicable here? It’s much more decent to move them up and down by drag\\drop than working with arrows in particular cases

 

 

Clip_337

@jamal​ I tested this in the latest Beta release of FME Desktop 2022 (Build 22315) and cannot reproduce the issue. I would expect that it should be fixed in Build 22311 as well, but if you're able to it'd be great to hear if you're still having the issue in Build 22315.

Additionally, what OS are you running FME Desktop on?

Badge +5

“move up” and “move down” works fine in build 22315 but when it comes to “move to top” an “move to bottom” it’s really slow

 

OS: Windows 11

 

Clip_366Clip_367 

 

Userlevel 2
Badge +10

“move up” and “move down” works fine in build 22315 but when it comes to “move to top” an “move to bottom” it’s really slow

 

OS: Windows 11

 

Clip_366Clip_367 

 

Hi @jamal​ I haven't been able to reproduce the issue in build 22315. I've created a support case to follow up with you on this and will post an answer here if a fix is released or a workaround is discovered.

Badge +5

The issues appears to be resolved in 2022.1 Build 22618

Clip_1013 

Reply