Skip to main content
  • EN
Ok, I know attributes with the same name in the source and destination are automatically connected, assuming the case is the same. If this occurs, the connection arrows will turn green and the attribute information will be pushed across.

 

 

 

I have attributes that are the spelled the same in both the source and destination, but one is lowercase and the other is uppercase. Even though the connector arrow is yellow, the source information is still being populated in the destination attribute. Is there a way to disable the automatic mapping?

 

 

 

I’m currently using FME Workbench 2011.

 

 

 

Thanks in advance.

 

 

 

Hi,

 

 

You can add an attribute remover before the writer and leave only the attributes you want to be mapped. If you have more attributes that need removing than kept use the attribute keeper.

 

 

Itay
I actually need that attribute. I'm using a attributevaluemapper to change the values to match the target model, but the original values are being passed instead of my mapped values.

 

 

My other concern is, I have a lot of features w \\ numerous attributes that have to be imported, and don't what the worry of checking all attributes for similar spelling.

 

 

YJ
That is simply because your value mapped attribute  is not routed properly to its destination. Attribute.

 

For a more flexible approach see the schema mapper.
I mapped the new attrubute that Attributevaulemapper creates to the target model and left the original attribute alone, but the original value was still being populated. If I redirect to the visualizer first, the information in the attributes is correct, when it writes to the database I'm getting the original value.

 

 

Just curious if anyone else is having this issue. 

 

 

I'll look into schema mapper.

 

 

Thanks
Sounds to me like something on the writer side, are you writting to an existing table? What happens if you truncate the table?

 

 

 

Hi,

 

 

one think to verify is the possible precense of run-time attributes that are not visible at design-time (in the Workbench).

 

 

Try to send a copy of your features entering the Writer to a Logger so that you can check for the precense of these.

 

 

I agree with Itay on inserting an AttributeKeeper to prevent surprises if this is the case.

 

 

David
Maybe you are not linking/merging the tables correctly?

 

 

Reply


Community Stats

30,149
Posts
114,438
Replies
37,793
Members
Terms & ConditionsCookie settings
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.