Skip to main content
Solved

fme form data inspector for debugging

  • June 3, 2026
  • 6 replies
  • 65 views

jpaulo
Participant
Forum|alt.badge.img+5

Hi there, 

I am new to FME, and would appreciate any help or resource that teaches how to use “fme form data inspector” to debug error in the workspace?

Thanks in advance 

Best answer by redgeographics

In broad terms, you can use the Data Inspector (or Visual Preview in Workbench itself) to check whether your data looks like you expect it to look after running it through a workspace.

Things I generally look out for:

  • Is the data in the correct geographic location
  • Is the amount of data along the lines of what I would expect (for example, if I work with data for a municipality with a population of 15.000 and I have 100.000 building polygons, I know that’s probably not correct, so worth looking in to).
  • Are the attributes filled with the values I expect

If there’s an error in the workspace I of course try and see what may have caused that error, keeping in mind that the transformer where the error is noticed may not be the one where it’s caused.

The webinar ​@hkingsbury pointed out sounds like a good one to watch. I also recall an excercise from the old training materials where you’d have to debug a workspace, but I don’t think that one made it to the FME Academy (for the old-timers: it’s the one where Dale drove his Tesla over a bridge)

6 replies

danilo_fme
Celebrity
Forum|alt.badge.img+54
  • Celebrity
  • June 3, 2026

Hi ​@jpaulo

 

I suggest that you use transformers in FME Workbench to perform your QA/QC validation.

You can check for possible bugs in Data Inspector after running your workflow in Workbench, and enable the Stop at Breakpoints option: Crtl + Shift + F5.

 

If you need more informations or help, danilo@solutial.com.br.

 

Thanks in Advance,

 

 

 


hkingsbury
Celebrity
Forum|alt.badge.img+73
  • Celebrity
  • June 3, 2026

hkingsbury
Celebrity
Forum|alt.badge.img+73
  • Celebrity
  • June 3, 2026

redgeographics
VIP
Forum|alt.badge.img+62

In broad terms, you can use the Data Inspector (or Visual Preview in Workbench itself) to check whether your data looks like you expect it to look after running it through a workspace.

Things I generally look out for:

  • Is the data in the correct geographic location
  • Is the amount of data along the lines of what I would expect (for example, if I work with data for a municipality with a population of 15.000 and I have 100.000 building polygons, I know that’s probably not correct, so worth looking in to).
  • Are the attributes filled with the values I expect

If there’s an error in the workspace I of course try and see what may have caused that error, keeping in mind that the transformer where the error is noticed may not be the one where it’s caused.

The webinar ​@hkingsbury pointed out sounds like a good one to watch. I also recall an excercise from the old training materials where you’d have to debug a workspace, but I don’t think that one made it to the FME Academy (for the old-timers: it’s the one where Dale drove his Tesla over a bridge)


hkingsbury
Celebrity
Forum|alt.badge.img+73
  • Celebrity
  • June 4, 2026

@redgeographics you’re showing your age! It’s Data Preview now ;)

 

 


redgeographics
VIP
Forum|alt.badge.img+62

@redgeographics you’re showing your age! It’s Data Preview now ;)

 

 

I've been around for a large part of FME's development 😅 Still remember the FME Viewer and even pre-Workbench days...