Skip to main content
Question

Schemamapper error

  • August 9, 2017
  • 3 replies
  • 47 views

redgeographics
VIP
Forum|alt.badge.img+63

If somebody from Safe's support could take a look at this.

As mentioned in this thread the SchemaMapper is showing some odd behaviour. I'm doing a simple attribute map and specify that the old attributes should be removed. However, they remain and the new ones aren't automatically exposed.

Sample template attached:

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.

3 replies

fmelizard
Safer
Forum|alt.badge.img+22
  • Safer
  • August 9, 2017

Hi @redgeographics. I'm looking into the SchemaMapper behaviour. For new attributes, there is a Known Issue # 31149 to expose attributes created by the SchemaMapper. So I'll add more interest to that.

For Source Attribute parameter, I'm continuing to investigate. Thanks!


fmelizard
Safer
Forum|alt.badge.img+22
  • Safer
  • August 10, 2017

Hi @redgeographics. For source attributes being displayed when Source Attribute parameter is set to Remove, I filed known issue # 78972. I'll update the question and add in any updates as I hear from Development.


redgeographics
VIP
Forum|alt.badge.img+63

Thanks Natalie!