Skip to main content
Question

FME Form not using local value for offline deployment parameter?

  • June 1, 2026
  • 2 replies
  • 30 views
janet
Contributor

Hello,

I’m authoring some workspaces for operating in FME Flow Hosted and I’ve configured some deployment parameters for DB connections and text values. Now because it’s a Hosted service, I don’t need to keep an FME Flow instance running while I’m authoring. From FME Form, it looks like local values are set, but I can’t seem to get the workspace to run without syncing to Flow.

 

 

 

Why isn’t Form recognizing the local values? I seem to remember in previous versions that I wouldn’t need to create user parameters just to assign to deployment parameters for offline runs. That seems redundant. What am I missing?

I’m on FME Form 2026.1.1.

 

    2 replies

    j.botterill
    Influencer
    Forum|alt.badge.img+58
    • j.botterillInfluencer
    • Influencer
    • June 2, 2026

    FME Form can use deployment parameters offline only if it can resolve them locally.

    • For text/password deployment parameters, a local value is enough. 
    • For database connection and web connection deployment parameters, Form still needs a locally resolvable connection (typically a local connection with the same name) or access to the Flow-backed connection store.

    If it can’t resolve that reference, it will look like the workspace needs to sync/connect to Flow before it can run. Deployment parameters are stored in FME Flow, not in the workspace itself. Form can reference them when connected to a Flow deployment parameter store

    Deployment Parameters for DB/Web connections require 

    • using FME Flow as the connection storage, or
    • finding a database/web connection of the same name locally in FME Workbench.
      If neither is true, Form returns an error.

    So not 100% user parameter, but more a resolvable connection file store in the connection store for offline use

    janet
    Contributor
    • janetContributor
    • Author
    • June 2, 2026

    All the right points, which is why this is confusing.

    For the local values with text type, “dbschema”, “user”, there IS a value set locally, but the parameter itself still isn’t resolved.

     

    And for “dbconn”, I DO have the same connection name in Form and it DOES resolve when assigned.

    It would make sense if the deployment parameter icons stay red, but I should be able to run the workspace, but I can’t.

    Community Stats

    32,610
    Posts
    123,761
    Replies
    40,955
    Members
    Terms & ConditionsAccessibility statement
    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.