Skip to main content
Open

Data Virtualization - Import Endpoint Schema from Existing Dataset

Related products:FME Flow
  • August 20, 2025
  • 4 replies
  • 75 views

chriswilson
Enthusiast
Forum|alt.badge.img+21

I believe this was mentioned in a webinar, but being able to import an endpoint’s schema - from the dataset it is going to be accessing of course - without having to manually create every property would be a great thing to have.  This could be from a local file, cloud source, anything.

 

Beyond saving time, it should also ensure accuracy.

4 replies

rylanatsafe
Safer
Forum|alt.badge.img+14
  • Safer
  • August 25, 2025

Hi ​@chriswilson ! To make sure that I’m understanding, are you imagining something akin to the “Import > From Dataset...” feature that you can leverage to populate the values for a Choice User Parameter in FME Workbench?

We have considered this idea more in the context of importing schema from an OpenAPI specification. For example, the ability to select a specific schema from an OpenAPI JSON file to add to your existing API—instead of the current behaviour where you can import “all or nothing”.

I’ll speak to a few upcoming features in the upcoming Data Virtualization in Action webinar on Wednesday (August 27th 2025), but we have not yet implemented this ability or an equivalent.


chriswilson
Enthusiast
Forum|alt.badge.img+21
  • Author
  • Enthusiast
  • August 25, 2025

 

Thanks ​@rylanatsafe,

That’s just about it, though I use that feature in Form more for setting up writers/FeatureWriters e.g. ArcGIS Online feature layers when I want to update an existing dataset.  An auto-import of schema that saves time and error in creating schema manually.

It doesn’t have to be all or nothing, you could choose attributes to import via a wizard, but if we want to present back the data we are going to be reading/processing through the workspace - e.g. a straight-up data request - then importing and having the schema preserved/set correctly would be a good option.  For a large schema if everything was needed this would be borderline if not essential, and yet you could still select certain attributes to simplify your output schema.

Of course the OpenAPI spec is good, but it doesn’t cover the specifics of a given dataset’s schema, and so I think this functionality would compliment that while still staying within the stucture/framework of an OpenAPI-compliant spec.

Will check out the webinar when it comes out.


rylanatsafe
Safer
Forum|alt.badge.img+14
  • Safer
  • September 16, 2025
NewOpen

martinkoch
Supporter
Forum|alt.badge.img+22
  • Supporter
  • September 24, 2025

I started adding this as an idea myself when I got this post as a suggestion.

I miss something a bit like ‘Import Parameters from JSON’ in the Output attributes of automation triggers, or the ‘import from dataset’ option in a FeatureWriter.

Something to aid getting most of the structure right in more complex datamodels.