Skip to main content
Solved

SQL Executor results not mapped in Schema Mapper

  • July 13, 2021
  • 2 replies
  • 56 views

Hi All,

I created a SchemaMapper lookup table in PostgreSQL and used it to map schemas in two scenarios.

  1. When I used ESRI SDE feature class as a reader and PostgreSQL as a writer the SchemaMapper mapped all and no problem
  2. When I used SQLExecutor reading from Microsoft SQL Server database that creates a query from four tables and writing to a Single PostgreSQL table, the SchemaMapper outputs the results as unmapped. I have used AttributeExposer transformer and it still didn't change. please see the screen shot below:

Can anyone please help me fix the issue or let me know if I'm missing anything?SchemaMapper issueThank you in advance

Best answer by david_r

My first hunch would be to check the case of the attribute names in both scenarios, remember that FME is case sensitive when comparing attribute names. Also make sure your SchemaMapper doesn't reference fme_feature_type, in which case you'll have to set it yourself after the SQLExecutor.

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.

2 replies

david_r
Celebrity
  • Best Answer
  • July 14, 2021

My first hunch would be to check the case of the attribute names in both scenarios, remember that FME is case sensitive when comparing attribute names. Also make sure your SchemaMapper doesn't reference fme_feature_type, in which case you'll have to set it yourself after the SQLExecutor.


  • Author
  • July 14, 2021

Thanks david_r, setting fme_feature_type worked for me.