Skip to main content
Solved

Missing fme attributes in SQL output ??

  • December 17, 2020
  • 3 replies
  • 30 views

lifalin2016
Contributor
Forum|alt.badge.img+29

Hi all.

I'm importing some DWGs and DGNs, merging all features from all files, and adding fme_basename and fme_dataset to the input. This works fine, until output.

The output writer featuretype lists the two attributes under "Format attributes" with a green arrow. The writer featuretype dropdown also lists them. And the User Attributes are set to "Automatic".

But the writer fails to output the fme values to the database tables. Only the "autocad"/"igds" values are output.

What am I missing here ?

Shouldn't the fme attributes be included in the output ?

Need I do anything else to make this happen ?

Cheers

Best answer by lifalin2016

Happy New Year.

I guess the writers just strip any and all attributes named fme_... from the output ?

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

3 replies

lifalin2016
Contributor
Forum|alt.badge.img+29
  • Author
  • Contributor
  • December 17, 2020

For fun I appended "autocad_" to the fme attribute names (renamed them), and now it seems they all get output !??

What trickery is afoot here ??


lifalin2016
Contributor
Forum|alt.badge.img+29
  • Author
  • Contributor
  • December 17, 2020
lifalin2016 wrote:

For fun I appended "autocad_" to the fme attribute names (renamed them), and now it seems they all get output !??

What trickery is afoot here ??

Secondary issue: How come fme_dataset defaults to char(50) ?!?

Path names are very often longer than that. On Windows they're char(127).

Using this expression luckily did the trick: (a)TrimRight((a)Value(fme_dataset)(blank)(blank))


lifalin2016
Contributor
Forum|alt.badge.img+29
  • Author
  • Contributor
  • Best Answer
  • January 5, 2021

Happy New Year.

I guess the writers just strip any and all attributes named fme_... from the output ?


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