Skip to main content
Question

SQLITE Reader and FeatureMerger - User Attributes behavior

  • February 12, 2024
  • 2 replies
  • 55 views
kalbert
Supporter
Forum|alt.badge.img+14

When using the SQLITE3 Reader, unchecked attributes from the User Attributes tab are not exposed downstream to any transformer like AttributeManager, -Remover, -Keeper. This behavior is as expected.

However when using the FeatureType downstream on the Requestor side of a FetureMerger and the conflict resolution is set to ‘Use Requestor’ , the unchecked attribute is still active behind the scene and take precedence over the attribute of the same name coming from the Supplier.

It turned out that I need to keep the unwanted attribute ‘checked’ and remove it actively with an AttributeRemover to avoid the unexpected usage in the FeatureMerger.

I also tried to force it by changing the workspace option Reader/Writer Options > Allow Reader Feature Type Editing, but it made no difference.

Question: is this a bug or dangerously intended?

 

Setup: FME Forms 2023.2 for win 64

2 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+47
  • virtualcitymattCelebrity
  • Celebrity
  • 2000 replies
  • February 12, 2024

Certainly the doc seems to echo your thinking: https://docs.safe.com/fme/html/FME-Form-Documentation/FME-ReadersWriters/aboutFeatures/feat_type_reader_usrAttr.htm

In my experience the behavior of this feature is very much format dependent. For example a database format typically works this was as expected - just reads what is checked - but for other formats I've noticed they are just not exposed (as you've seen). 

Not that this is helpful, but I personally almost never use this feature and choose to modify the attributes myself in the workflow with Managers/Keepers - and a big part of that decision I think is the inconsistently between formats.

Hard to say if this is a bug or by design though. My guess is that it's half way between.

Perhaps @nampreetatsafe or @markatsafe is able to comment?

kalbert
Supporter
Forum|alt.badge.img+14
  • kalbertSupporter
  • Author
  • Supporter
  • 27 replies
  • February 19, 2024

I think it’s acceptable that data formats have different capabilities in terms of attribute behavior when they got read by FME. However I would expect to see the user attribute check boxes disabled for formats where check/un-check can not be supported for technical reasons. 


Community Stats

32,070
Posts
121,771
Replies
39,696
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.