Question

Exposed Elements in NeighborFinder are Forgotten/Aren't Saved


Elements that I try to add to my list of exposed elements in NeighborFinder are not being saved after closing and reopening workbench FME Desktop 2018.1. Upon reopening the workbench, only those elements that were originally exposed are still exposed. The newly exposed elements are forgotten/no longer exposed.

My workbench contains about a dozen NeighborFinder transformers, but no matter what I do, only a handful of them actually save the attributes that I expose after I save and reopen the workbench. I found an old forum post about the same issue in FME Desktop 2015 (https://knowledge.safe.com/questions/5162/attributesplitter-exposed-elements.html?childToView=91200). Is it possible that the same bug exists in 2018.1?

 

I’ve tried the following workarounds but none of them worked:

  1. Copy a working NeighborFinder and paste it to replace a broken NeighborFinder. Save and reopen the workbench.
  2. Create a brand new NeighborFinder, expose the elements, save and reopen the workbench.
  3. Copy the contents of the current workbench into a blank workbench, expose desired elements in the NeighborFinders, save and reopen the workbench.
  4. Expose all attributes when creating N list in NeighborFinder, expose desired elements in the NeighborFinder, save and reopen the workbench

3 replies

Userlevel 4
Badge +13

Hi @cheriesouthwick By "Exposed Elements" do you mean "Add Attribute..."? If the problem still exists with FME 2019.0 then please file a case via https://www.safe.com/support/report-a-problem/ Thanks!

Thanks @danatsafe . No I don't mean "Add Attribute", I mean "Expose Elements" from the "Matched" dropdown in NeighborFinder as shown in this image.

 

I opened a ticket with Safe Support last week but they haven't supplied any answers yet, hence my post here as well.
Badge +10

Hi @cheriesouthwick, I have responded to you via your support ticket not sure if you have received an email or it is filtered by your email. In case you have not, it is indeed an issue which I have filed an internal dev issue and is currently under development. Please contact us via your support ticket

C144727

 

 

Reply