Skip to main content
Solved

Attribute discrepancy between both sides of AttributeManager


nea
Contributor
Forum|alt.badge.img+9
  • Contributor

I have an AttributeManager in a custom transformer (may be part of the problem but thought I would start simple with the AttributeManager) that has the following data (correct) on the input but the name of the attribute (not the attribute values) is assigned in the output.

Input Attribute “Public_Water_System_ID” with correct values and output with wrong values:

Settings in the AttributeManager is as follows:

For data type I’ve tried buffer (default), varchar(20), and char(20). None of the other types seemed to make sense since the values are string.

Perhaps a related problem is that this attribute (“Public_Water_System_ID”) is passed as a parameter into this custom transformer and is seems like there might be an issue with the transfer.  However, that being said, the correct values are appearing at the input port of the AttributeManager which is downstream from the custom transformer input.

 

Best answer by nea

The problem was with the Custom Tranformer parameter.  I deleted it and then recreated it.  Now the Custom Transformer is working properly.

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

3 replies

nea
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • February 22, 2024

Information on the customTransformer.

When I double-click the CT in the main portion of FMW.

Under User Parameters in the CT:

When I try to edit this attribute I get the following:

 


nea
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • Best Answer
  • February 23, 2024

The problem was with the Custom Tranformer parameter.  I deleted it and then recreated it.  Now the Custom Transformer is working properly.


mark2atsafe
Safer
Forum|alt.badge.img+49
  • Safer
  • February 23, 2024
nea wrote:

The problem was with the Custom Tranformer parameter.  I deleted it and then recreated it.  Now the Custom Transformer is working properly.

Thanks for letting us know the problem is solved.


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