Skip to main content
Solved

Expose elements doesn't work in FME 2020 ?


fikusas
Contributor
Forum|alt.badge.img+5

Seems like exposing elements in AttributeSplitter doesn't work in FME 2020.0.1 (build 20218). Even exposing attributes after splitter with AttributeExposer is broken.

Or maybe it's Data Inspector's fault for not displaying them. Any thoughts on this?

Best answer by markatsafe

Thanks @fikusas & @takashi for reporting this. I've reproduced the problem and we'll try and get that addressed.

test workspace (FME 2020): exposelistelements.fmw

Fixed in FME 2020.1

View original
Did this help you find an answer to your question?

16 replies

takashi
Contributor
Forum|alt.badge.img+19
  • Contributor
  • April 21, 2020

Not only in the Table View, a similar issue appears in the AttributeManager parameters too.

Hope someone from Safe clarifies this. @danatsafe?


ebygomm
Influencer
Forum|alt.badge.img+31
  • Influencer
  • April 21, 2020

In 2019, you definitely can expose each list element in this way so it is visible in the Table View

 


Forum|alt.badge.img+2
  • Best Answer
  • April 21, 2020

Thanks @fikusas & @takashi for reporting this. I've reproduced the problem and we'll try and get that addressed.

test workspace (FME 2020): exposelistelements.fmw

Fixed in FME 2020.1


fikusas
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • April 21, 2020
ebygomm wrote:

In 2019, you definitely can expose each list element in this way so it is visible in the Table View

 

Yeah, the 2019 works properly.


Forum|alt.badge.img+3
markatsafe wrote:

Thanks @fikusas & @takashi for reporting this. I've reproduced the problem and we'll try and get that addressed.

test workspace (FME 2020): exposelistelements.fmw

Fixed in FME 2020.1

Hi Mark- I wondered which build/version this might be repaired in. This is impacting several of my important workflows.


fmelizard
Contributor
Forum|alt.badge.img+17
  • Contributor
  • June 5, 2020

@fikusas The problem (from your screenshot) is with the Data Inspector. Too many exposed list elements could bog down the DI in FME 2019. With FME 2020 the work-around is to expose attributes in the table view with the Column Selector.

@fme_fan_mike Maybe there should be option to expose a small number of list elements by default, e.g. 10 or 20?


Forum|alt.badge.img+6

Hi @fme_fan_mike (and others!),

A fix for exposed list elements no longer appearing in the AttributeManager has been released in 2020.0.3 (https://www.safe.com/support/downloads/). The fix relating to Visual Preview/Data Inspector is a work-in-progress but is likely to be in 2020.1.

I hope this helps! Please feel free to reach back out here or through Support if you have any questions, comments or concerns.

Best,

Annabelle


Forum|alt.badge.img+3
annabelleatsafe wrote:

Hi @fme_fan_mike (and others!),

A fix for exposed list elements no longer appearing in the AttributeManager has been released in 2020.0.3 (https://www.safe.com/support/downloads/). The fix relating to Visual Preview/Data Inspector is a work-in-progress but is likely to be in 2020.1.

I hope this helps! Please feel free to reach back out here or through Support if you have any questions, comments or concerns.

Best,

Annabelle

Thanks very much for the fast repair!


Forum|alt.badge.img
annabelleatsafe wrote:

Hi @fme_fan_mike (and others!),

A fix for exposed list elements no longer appearing in the AttributeManager has been released in 2020.0.3 (https://www.safe.com/support/downloads/). The fix relating to Visual Preview/Data Inspector is a work-in-progress but is likely to be in 2020.1.

I hope this helps! Please feel free to reach back out here or through Support if you have any questions, comments or concerns.

Best,

Annabelle

Hi @annabelleatsafe

I have similar issue with the Resource Reader when using it to read the schema from table - parameter window is not showing the attributes from the source file. Do you know if it was addressed and fixed in the newer releases?

image 1 - FME 2020.0.0.1

image 2 - FME 2019

 


Forum|alt.badge.img+6
zuzanna_sz wrote:

Hi @annabelleatsafe

I have similar issue with the Resource Reader when using it to read the schema from table - parameter window is not showing the attributes from the source file. Do you know if it was addressed and fixed in the newer releases?

image 1 - FME 2020.0.0.1

image 2 - FME 2019

 

Hi @zuzanna_sz,

 

I'm sorry to hear you ran into this issue! I just tried reproducing the above in 2020.0.3 and it looks like everything is working as expected now in this build (https://www.safe.com/support/downloads/#official), but of course, the best way to know for sure is to download and test using your own data. I would recommend giving this a shot! If you are still noticing the same issue in 2020.0.3, please let us know through https://www.safe.com/support/ and we'd be happy to take a deeper look.

Best,

Annabelle


Forum|alt.badge.img
annabelleatsafe wrote:

Hi @zuzanna_sz,

 

I'm sorry to hear you ran into this issue! I just tried reproducing the above in 2020.0.3 and it looks like everything is working as expected now in this build (https://www.safe.com/support/downloads/#official), but of course, the best way to know for sure is to download and test using your own data. I would recommend giving this a shot! If you are still noticing the same issue in 2020.0.3, please let us know through https://www.safe.com/support/ and we'd be happy to take a deeper look.

Best,

Annabelle

Hi, I gave it a try, but 2020.0.3 seems to have the same issue. I created a ticket via support page - thanks for the link!


Forum|alt.badge.img+2
zuzanna_sz wrote:

Hi, I gave it a try, but 2020.0.3 seems to have the same issue. I created a ticket via support page - thanks for the link!

Hi @zuzanna_sz,

Thank you for contacting Safe Software Support. Upon further testing we discovered this issue only occurs when there are spaces in the attribute names and was introduced in 2020.0.

Bug FMEENGINE-64915 has been filed to request this fix.


Forum|alt.badge.img
hollyatsafe wrote:

Hi @zuzanna_sz,

Thank you for contacting Safe Software Support. Upon further testing we discovered this issue only occurs when there are spaces in the attribute names and was introduced in 2020.0.

Bug FMEENGINE-64915 has been filed to request this fix.

Hi @hollyatsafe, thanks for addressing that! It's not a big issue, I will implement one change in my workflows to generate schema file headers without spaces but it will be nice to have the full functionality back in 2020.1

all the best for the SafeSoftware team!


salvaleonrp
Enthusiast
Forum|alt.badge.img+15
  • Enthusiast
  • June 26, 2020
annabelleatsafe wrote:

Hi @zuzanna_sz,

 

I'm sorry to hear you ran into this issue! I just tried reproducing the above in 2020.0.3 and it looks like everything is working as expected now in this build (https://www.safe.com/support/downloads/#official), but of course, the best way to know for sure is to download and test using your own data. I would recommend giving this a shot! If you are still noticing the same issue in 2020.0.3, please let us know through https://www.safe.com/support/ and we'd be happy to take a deeper look.

Best,

Annabelle

I did install build 20252 last night after reading the Best Answer hoping my issues would be fixed and it wasn't. I'm glad you found out the space was the cause of the bug because that's my specific case. Hope there can be a bug fix soon.


Forum|alt.badge.img+2
salvaleonrp wrote:

I did install build 20252 last night after reading the Best Answer hoping my issues would be fixed and it wasn't. I'm glad you found out the space was the cause of the bug because that's my specific case. Hope there can be a bug fix soon.

Hi @zuzanna_sz and @salvaleonrp,

The issue with the Schema (From Table) Reader truncating the Feature Type/Attribute Name list at values containing a space has been resolved in FME 2020.1 Beta b20587 and is available to download from safe.com/beta

Please note the FME 2020.1 Official Release is scheduled for next week.


markatsafe wrote:

Thanks @fikusas & @takashi for reporting this. I've reproduced the problem and we'll try and get that addressed.

test workspace (FME 2020): exposelistelements.fmw

Fixed in FME 2020.1

Hi @Mark Stoakes​ and @lizatsafe​,

 

I seem to have picked up a regression in this function in FME Workbench 2022.1.3 (Build 22630, Windows, x64). Exposed attributes won't display correctly in Visual Preview. AttributeSplitter won't automatically list them in the Output list directly under the transformer either, though I'm not sure if this is intended behaviour.

 

Exposing attributes manually through the Table View Schema options doesn't stick as soon as you navigate to another object in the workspace (another transformer, reader, etc.).

 

Steps (feature caching enabled, huge raster dataset):

  1. Utilise AttributeSplitter
  2. Manually expose attributes in AttributeSplitter transformer
  3. Open Visual Preview. Exposed attributes aren't displayed.
  4. Manually display attributes using Table View Schema options.
  5. Exposed attributes should now display.
  6. Select another transformer in the workspace. See that Visual Preview shows that transformers' stuff
  7. Navigate back to the AttributeSplitter with manually exposed attributes
  8. See that the 'exposed' attributes have disappeared in the table.

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings