Skip to main content
Solved

Data inspector 'Save data as' error

  • December 17, 2019
  • 7 replies
  • 21 views
mario_bla
Participant
Forum|alt.badge.img+6

Hello,

I have recently upgraded from version 2016 to newest version 2019. I noticed some strange behavior of 'Save data as' functionality in Data inspector in new version.

When I want to make some quick 'one time' procedure to check something and don't want to lose to much time for polishing, I usually just add Inspector and later if needed export the results from inspector to excel...

For example, I have 2 txt files, one containing data: 1 2 3 5 7 (each in its own row), and the other containing data 1 3 7 8 9 (again each in its own row). I want to match those data and inspect the differences:

Everything works well but when I open Data inspector and want to save the data to excel I get this error:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

Feature Type: `Inspector'

 

Attribute(string): `text_line_data' has value `varchar(255)'

 

Attribute: `text_line_data' is sequenced

 

Geometry Type: Unknown (0)

 

Number of Coordinates: 0 -- Coordinate System: `'

 

===========================================================================

In old 2016 version it worked ok and I could save to excel from Data inspector. What is the reason this doesn't work any more? Or, how to make it to work again - what is the error message implying?

Best answer by fmelizard

Hi @mario_bla This problem with saving data from the Data Inspector is now fixed in the latest FME 2020 betas.

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

7 replies

redgeographics
Celebrity
Forum|alt.badge.img+49

I tried to reproduce your workflow and while I think I have the steps down I'm not getting your error.

I do have a suggestion for a different way. I would recommend that you do actually set up proper writers but use the Redirect option to send the data to the Data Inspector or in-Workbench viewer rather than writing files. When you're ok with the output, switch off that redirect and run the workspace again, it will write the files. Combine that with Feature Caching and partial runs and you should still be able to save some time.

The reason I'm recommending this is that you're using Data Inspector in a bit of a convoluted way. There's nothing against doing it that way, it certainly works technically (at least it seemed to do so for me ) but it doesn't give you as fine grained control over the output as a proper writer would.

mario_bla
Participant
Forum|alt.badge.img+6
  • mario_blaParticipant
  • Author
  • Participant
  • December 17, 2019
redgeographics wrote:

I tried to reproduce your workflow and while I think I have the steps down I'm not getting your error.

I do have a suggestion for a different way. I would recommend that you do actually set up proper writers but use the Redirect option to send the data to the Data Inspector or in-Workbench viewer rather than writing files. When you're ok with the output, switch off that redirect and run the workspace again, it will write the files. Combine that with Feature Caching and partial runs and you should still be able to save some time.

The reason I'm recommending this is that you're using Data Inspector in a bit of a convoluted way. There's nothing against doing it that way, it certainly works technically (at least it seemed to do so for me ) but it doesn't give you as fine grained control over the output as a proper writer would.

Thank you very much for your comment. If I may ask, what build are you using? I have tried in last two newest: 19813 (219.2.1.0) and 19801 (219.2.0.0) and have the same error. But for example, in build 19630 (219.1.2) this error doesn't occur (works like in older 2016 version).

I know that this is probably not the best approach to use inspector for this but this is only for small and 'dirty' procedures which I run only once just to get the general idea about data and don't even bother to save them after I use them. I can live without this functionality - the question is only is this a bug or there is some explanation or setting I have to apply to make this work like before.

I have also noticed that this error only happens when there is more than one or two inspectors. In most cases it works ok with only one inspector, even two in some cases (didn't figure out the pattern or rule yet)... With more inspectors it doesn't work.

chrisatsafe
Contributor
Forum|alt.badge.img+2
  • chrisatsafeContributor
  • Contributor
  • December 17, 2019
mario_bla wrote:

Thank you very much for your comment. If I may ask, what build are you using? I have tried in last two newest: 19813 (219.2.1.0) and 19801 (219.2.0.0) and have the same error. But for example, in build 19630 (219.1.2) this error doesn't occur (works like in older 2016 version).

I know that this is probably not the best approach to use inspector for this but this is only for small and 'dirty' procedures which I run only once just to get the general idea about data and don't even bother to save them after I use them. I can live without this functionality - the question is only is this a bug or there is some explanation or setting I have to apply to make this work like before.

I have also noticed that this error only happens when there is more than one or two inspectors. In most cases it works ok with only one inspector, even two in some cases (didn't figure out the pattern or rule yet)... With more inspectors it doesn't work.

Hi @mario_bla,

Just wanted to clarify if this behavior is with the FME Data Inspector application or the visual preview window within FME Workbench? Or do you get the same error in both Data Inspector and Visual Preview?

Also, I noticed you are using Inspectors but you also have feature caching on. Just wanted to share a blog article on feature caching so you can learn more about how to use feature caches: https://www.safe.com/blog/2018/05/caching-data-fme-evangelist174/

mario_bla
Participant
Forum|alt.badge.img+6
  • mario_blaParticipant
  • Author
  • Participant
  • December 17, 2019
chrisatsafe wrote:

Hi @mario_bla,

Just wanted to clarify if this behavior is with the FME Data Inspector application or the visual preview window within FME Workbench? Or do you get the same error in both Data Inspector and Visual Preview?

Also, I noticed you are using Inspectors but you also have feature caching on. Just wanted to share a blog article on feature caching so you can learn more about how to use feature caches: https://www.safe.com/blog/2018/05/caching-data-fme-evangelist174/

Hi @chrisatsafe,

I just tried and confirmed that I get the same error both in FME Data Inspector application and the visual preview window within FME Workbench.

(Thanks for the tip for feature caching and partial runs!)

chrisatsafe
Contributor
Forum|alt.badge.img+2
  • chrisatsafeContributor
  • Contributor
  • December 23, 2019
mario_bla wrote:

Hi @chrisatsafe,

I just tried and confirmed that I get the same error both in FME Data Inspector application and the visual preview window within FME Workbench.

(Thanks for the tip for feature caching and partial runs!)

Hi @mario_bla,

This is an interesting one! We had another user report similar behavior with build 19813 but it is proving to be a tricky one to reproduce. I haven't been able to reproduce locally or on a VM. Just to confirm, does this still occur after purging your temporary files (Tools > Purge Temporary Files)?

Would you be able to help us get a better understanding of your machine by running the system_information.bat file from the General Troubleshooting Guide and sending the resulting FMEReport.html file to our support team by submitting a case so we can continue to look into this for you?

mario_bla
Participant
Forum|alt.badge.img+6
  • mario_blaParticipant
  • Author
  • Participant
  • December 24, 2019
chrisatsafe wrote:

Hi @mario_bla,

This is an interesting one! We had another user report similar behavior with build 19813 but it is proving to be a tricky one to reproduce. I haven't been able to reproduce locally or on a VM. Just to confirm, does this still occur after purging your temporary files (Tools > Purge Temporary Files)?

Would you be able to help us get a better understanding of your machine by running the system_information.bat file from the General Troubleshooting Guide and sending the resulting FMEReport.html file to our support team by submitting a case so we can continue to look into this for you?

Hi @chrisatsafe,

Purging temporary files doesn't help.

I have followed your suggestion and submit a case. Case number is C150836.

Thanks for your help so far.

fmelizard
Safer
Forum|alt.badge.img+18
  • fmelizardSafer
  • Safer
  • Best Answer
  • January 30, 2020

Hi @mario_bla This problem with saving data from the Data Inspector is now fixed in the latest FME 2020 betas.

Reply


Helpful Members This Week

Community Stats

31,328
Posts
118,863
Replies
38,957
Members

Latest FME

Terms & ConditionsCookie settings

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
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.