Skip to main content
Solved

Unable to remove duplicate attributes


mapper
Contributor
Forum|alt.badge.img

I am translating data from a SDE database to a file gdb. For some reason there seems to be a second copy of all my attributes (the upper case attributes in the attached image). I can not access these attributes to remove them. Several of the attributes are dates, I used the date formater to change the format of the date. Unfortunatly the dupliacte attributes aren't getting reformated and are causing an error in the writer. I have never seen an error like this and don't know where to start. Any Ideas?

Best answer by mapper

Thanks, using the attributeExposer to expose the upper case attributes and then removing them with the attributeRemover worked. great.

View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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

takashi
Supporter
  • December 4, 2015

Hi,

If the uppercase attribute names just aren't shown on Workbench interface, you can expose them with the AttributeExposer, and then you can format the date string, remove unnecessary attributes, and so on.

Takashi


pratap
Contributor
Forum|alt.badge.img+11
  • Contributor
  • December 4, 2015

Hi,

As far as I understand, SDE DB will have attributes in uppercase and gdb will accept in both cases. It might be case that you are processing both case attributes till the writer i.e. file gdb. As @takashi told remove the attributes either by exposing and removing or use attrbutekeeper before the writer and allow only required attributes to writer.

Pratap


mapper
Contributor
Forum|alt.badge.img
  • Author
  • Contributor
  • Best Answer
  • December 4, 2015

Thanks, using the attributeExposer to expose the upper case attributes and then removing them with the attributeRemover worked. great.


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