Skip to main content
Solved

FME Flow App returns "The error number from ArcObjects is: '-2147215961'. The error message from ArcObjects is: {Invalid database name}" when User Parameter selects more than one feature type, but works when only one Feature type is selected?

  • September 5, 2023
  • 3 replies
  • 182 views

Hi Everyone,

 

I am relatively new and in my current position I am replacing someone who was a bit more advanced than me. I understand a lot of what the workspace is trying to do (and it worked in FME Server) but once we migrated to FME Flow, the workspace no longer works. The premise is similar to the FME Demo "Map Based Data Distribution". The difference in our workflow has an Input Project Area instead of an Area of Interest which allows the user to upload a shapefile or use our municipal boundaries which is stored in our Repository. We also create a waiver for our Digital Licensing Agreements, but that's a User Parameter with "yes/no" and with either setting, the workspace/app fails.

 

I've included images for the parameters for the FeatureReader (but not the connection parameters). For "Feature Types to Read", we have a User Parameter ($(FEATURETYPES_2)), which is Choice List. It's the FQN of our Feature Types in the database connection file (the connection file is using a UNC path FYI).

image.pngimage2_user_paramterworkspace data download Once 1 or more are selected its supposed to go through some filters that remove or adjust attributes or their values (such as looking for special characters and fixing it), but my workspace always fails when I select two or more feature types. I've tried adjusting the delimiter to commas or periods, with no avail. I am really not sure how to move forward in correcting this because I simply don't understand the error. In theory, I do, but i am exposing fme_feature_type and the feature types are in a list by their FQN. I might be thinking that maybe I am supposed to reference the connection file in the repository in FME Flow? Is that something that would help?

 

I truly am stumped on how to move forward. Can anyone shed some light or guidance? Where can I look or address the issue? What troubleshooting steps can I take? Really anything will help.

Best answer by shodzic

I found a solution maybe!

 

I was able to circumvent the issue listed by Safe Software by using a Tree Choice Configuration. My Values and Displays were in the format “SchemaName.TableName”. Below is my User Parameter options:

 

  • Multiple Selections: ON
  • Choice List Delimiter: <Space>
  • Tree Node Delimiter: . (period)

This version of a user parameter enabled me to select from the list which subsequently selected the Features from the “Feature to Read” Parameter option. I was using a Connection File for an ESRI SDE.

 

 

Below was the first response I received before i found the solution above. There is value in reading the below:

 

it seems like between 2020.2 and 2023.0.1, the user parameter expected by the Feature Types to Read parameter of the Feature Reader changed from a choice list to something specific and unique to the Feature Reader.

If a new Feature Reader is added to the canvas in 2023.2 and create a user parameter from the Feature Types to Read, the user parameter created is NOT a choice parameter and the Feature Types to Read is not a type of user parameter that could be manually created from the User Parameter Manager. In FME 2020.2, this creates a choice list user parameter which you've been using. So unfortunately, this is not compatible with FME 2023.

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

3 replies

merlinegeorge
Safer
Forum|alt.badge.img+5

Hello,

 

Would you be able to create a case, sending us the job log, the version and build of the new Flow installation? Please also test if the workspace is running on FME Workbench of the same version.


  • Author
  • September 11, 2023

Hi Merline,

 

I will put a job case very shortly, I will essentially be copying and pasting what I've done here. I feel as I am starting to doubt everything about the process and thinking of recreating it somehow. Regardless, if you guys can't recreate the problem, i will have to redo it.


  • Author
  • Best Answer
  • September 26, 2023

I found a solution maybe!

 

I was able to circumvent the issue listed by Safe Software by using a Tree Choice Configuration. My Values and Displays were in the format “SchemaName.TableName”. Below is my User Parameter options:

 

  • Multiple Selections: ON
  • Choice List Delimiter: <Space>
  • Tree Node Delimiter: . (period)

This version of a user parameter enabled me to select from the list which subsequently selected the Features from the “Feature to Read” Parameter option. I was using a Connection File for an ESRI SDE.

 

 

Below was the first response I received before i found the solution above. There is value in reading the below:

 

it seems like between 2020.2 and 2023.0.1, the user parameter expected by the Feature Types to Read parameter of the Feature Reader changed from a choice list to something specific and unique to the Feature Reader.

If a new Feature Reader is added to the canvas in 2023.2 and create a user parameter from the Feature Types to Read, the user parameter created is NOT a choice parameter and the Feature Types to Read is not a type of user parameter that could be manually created from the User Parameter Manager. In FME 2020.2, this creates a choice list user parameter which you've been using. So unfortunately, this is not compatible with FME 2023.


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