Skip to main content
Question

Dynamic schema creation failing for Esri Guid

  • July 26, 2019
  • 3 replies
  • 13 views

todd_davis
Influencer
Forum|alt.badge.img+23

Hi,

I am creating a dynamic schema from a list, however when I am trying to create a GUID in an Esri File Geodatabase it is showing the field as text (using both writers and changing the format_short_name). What's more annoying is this same example is shown in this article: https://knowledge.safe.com/articles/1051/index.html

Does this no longer work, or can you see an issue in this example??Guid.fmw

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

mark2atsafe
Safer
Forum|alt.badge.img+59

I think fme_format_short_name should be GEODATABASE_FILE and not FILEGDB. Hoping that makes the difference.


todd_davis
Influencer
Forum|alt.badge.img+23
  • Author
  • Influencer
  • July 26, 2019

I think fme_format_short_name should be GEODATABASE_FILE and not FILEGDB. Hoping that makes the difference.

Hi @mark2atsafe,

Oops had a mistake in the example (have now corrected the attached example for FILEGDB), because I had been playing around with different FIle Geodatabase writers and obviously forgot to update the short_name on the one I loaded.

Unfortunately this isn't the fix though, as it still shows as text.

Cheers,

Todd


mark2atsafe
Safer
Forum|alt.badge.img+59

Hi @mark2atsafe,

Oops had a mistake in the example (have now corrected the attached example for FILEGDB), because I had been playing around with different FIle Geodatabase writers and obviously forgot to update the short_name on the one I loaded.

Unfortunately this isn't the fix though, as it still shows as text.

Cheers,

Todd

I'm checking with the developers. My first thought is that the API (FILEGDB) format doesn't support this, although I don't see why. I'll let you know what I hear back.