Skip to main content
Solved

Attribute Creator - Adjacent Feature not populating more than 1 record

  • May 12, 2025
  • 6 replies
  • 86 views

bkerr
Contributor
Forum|alt.badge.img+6

Hi,

 

I am using the attribute creator to populate a new field. I want to fill in the blank rows with the previous master property number from the master prop no field. I have enabled the adjacent features but no matter what I try it still only populates just the 1 record after a value and not all the blanks. I thought I would only need 1 based on what I’ve found on the forums.

What am I doing wrong here?

I also tried to do that same thing via the attribute manager but get the same result.

The end result would also have row 3 (FME row id not the xlsx one) with ‘932590’ and row 6 with ‘933123’ and rows 9-11 with ‘933796’ etc with the number of blank rows varying from 1 to potentially hundreds.

The settings I have for the transformers are below.

I am using FME 2022.2.

 

Thank you!

 

Belinda

Best answer by takashi

HI ​@bkerr ,

If “master_prop_no_calc” is a new attribute that will be created in the AttributeCreator, expose its name with AttributeExposer beforehand.

Then, in the AttributeCreator, I think this conditional value setting works as expected.

If master prop. no. has a value then master prop.no.
Else feature[-1].master_prop_no_calc

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

6 replies

crutledge
Influencer
Forum|alt.badge.img+43
  • Influencer
  • May 12, 2025

Hi ​@bkerr This question just came up and ​@takashi caught the issue. In the first case: If there is a value then No Action. Else -1 

Fill in adjacent empty values in table is not working as I expect? | Community

Hope that helps!


bkerr
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • May 12, 2025

Hi ​@crutledge. I did see that post but in my case I’m populating a new field so I need it to take the value over rather than do no action. I did try that but it just leaves me with ‘missing’ values for that top row instead. 

 


crutledge
Influencer
Forum|alt.badge.img+43
  • Influencer
  • May 12, 2025

Ah ​@bkerr then you will want the part of the solution that I proposed (that didn’t work there but I think works here).

In Your case .test is .master_prop_no_calc

That work?


takashi
Celebrity
  • Best Answer
  • May 12, 2025

HI ​@bkerr ,

If “master_prop_no_calc” is a new attribute that will be created in the AttributeCreator, expose its name with AttributeExposer beforehand.

Then, in the AttributeCreator, I think this conditional value setting works as expected.

If master prop. no. has a value then master prop.no.
Else feature[-1].master_prop_no_calc


bkerr
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • May 12, 2025

Hi ​@takashi ,

 

That did the trick. I was getting the feature[-1] value from the wrong field. I thought it would of worked from the other but it doesnt. Swapping it to the newly calculated field resolved the issue. Thank you!


crutledge
Influencer
Forum|alt.badge.img+43
  • Influencer
  • May 12, 2025

@bkerr Good stuff. Glad you got it working! It’s always those little things. :D