Skip to main content
Solved

Error "The table name or field names may be too long or invalid for the server"

scarecrow
Contributor
Forum|alt.badge.img+4

Hello,

I’m trying to read specific feature classes from an SDE database using a user parameter within a feature reader.

I’ve not had a problem with this previously so not sure if it’s a bug (I’m using FME 2023.1.2.0 (20231110 - Build 23641 - WIN64) 

The issue I’m having is:

When selecting feature classes manually in the ‘Feature types to read’ section of the Feature Reader window I can select as many as I want and they’ll all read fine.

When using the user parameter (please see settings in screenshot below):

Selecting one dataset reads fine

Selecting 2 or more feature classes I get the error “Error creating feature dataset 'feature class a feature class b'. The table name or field names may be too long or invalid for the server”

 

Thanks for you time

 

Best answer by scarecrow

 @crystalatsafe thanks for your reply.

Sorry I can’t share the workbench but it is just what is shown in the screenshot. A creator linked to a SDE feature reader, with all default settings. As you say I think this is an issue with the version I’m running.

For now my workaround is to use a parameter fetcher to get the inputs set by the user, send it to an attribute splitter to separate the feature classes and then use a list exploder to create an attribute that feeds the feature reader.

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

3 replies

crystalatsafe
Safer
Forum|alt.badge.img+18

Hi @scarecrow 

 

It looks like a similar issue was fixed in a newer version of FME (2024.0.1).

If you are able to, please send your workspace over and I can take a look. 

 

Crystal 

 

scarecrow
Contributor
Forum|alt.badge.img+4
  • scarecrowContributor
  • Author
  • Contributor
  • Best Answer
  • June 14, 2024

 @crystalatsafe thanks for your reply.

Sorry I can’t share the workbench but it is just what is shown in the screenshot. A creator linked to a SDE feature reader, with all default settings. As you say I think this is an issue with the version I’m running.

For now my workaround is to use a parameter fetcher to get the inputs set by the user, send it to an attribute splitter to separate the feature classes and then use a list exploder to create an attribute that feeds the feature reader.

crystalatsafe
Safer
Forum|alt.badge.img+18

Hi @scarecrow 

I’m glad you were able to find a workaround.

If you do test this is in 2024.0.1 or newer please let us know how it goes. 

 

Crystal 

Reply


Most helpful members this week

Community Stats

30,846
Posts
116,934
Replies
38,669
Members
Terms & ConditionsCookie settings

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
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.