Microsoft Azure Storage Table Reader Parameters

About Web Connections

Connections store authentication information.

For general information about web connections, please see Using Web Connections.

For information about managing web services (including authorization credentials such as Client Id and Client Secret), please see Managing Web Services.

Connection

From the Connection parameter in a web service format, you can do one of the following:

  • Select an existing previously defined connection. For information, see the section Reusing a Web Connection in Using Web Connections.
  • Select Add Web Connection to define a new connection. The new connection can be made visible only to the current user, or can be shared among multiple users.

Microsoft Azure Storage Connection

Select an existing Microsoft Azure Storage connection, or Add Web Connection....

Add Microsoft Azure Storage Connection

To define a new connection from the Connection parameter in a Microsoft Azure Storage Table format, see the topic Microsoft Azure Storage Table: Add Web Connection.

Constraints

Specifies the name of the table to read data from. The table name can be entered manually or chosen from a list of tables accessible by the account specified by the Storage Service Name.

Specifies the filter applied to the Azure Storage Table query. The format of the filter is the same as the $filter clause for OData.

Logical Operator

Description

Example Filter String

eq

Equal

City eq 'Redmond'
gt

Greater than

Price gt 20

ge

Greater than or equal to

Price ge 10

lt

Less than

Price lt 20

le

Less than or equal

Price le 100

ne

Not equal

City ne 'London'

and

And

Price le 200 and Price gt 3.5

or

Or

Price le 3.5 or Price gt 200

not

Not

not isAvailable

For a full filter syntax reference, please see Constructing Filter Strings for the Table Designer.

Schema Generation

This option can be set to prevent FME from unnecessarily reading all the rows from a potentially large file when determining its schema.

The default is 1.

Note  This setting only applies to the schema generation; it does not limit the number of rows read when the translation is run.

Advanced

  • Yes (default) – Ensures that a URL's digital certificate is valid (signed by a trusted certificate authority), trusted, and belongs to the domain to which you are connecting.
  • No – Verification will not be performed (that is, there is no verification that the URL’s certificate is valid or trusted).
Warning  Setting this parameter to No could allow the HTTP request/response to be intercepted.

How FME Processes Multiple Verification Parameters in a Workspace

FME evaluates the setting at the workspace component level. If a reader/writer or web connection has the Verify HTTPS Certificate(s) parameter set to Yes, and an HTTPCaller transformer has the Verify HTTPS Certificate(s) parameter set to No, then the reader will verify certificates for its data requests, but the transformer will not verify certificates for its own requests.

FME does not combine multiple verification parameters — it uses the parameter local to the reader/writer, transformer, or web connection that is making the web call.

It is good practice to ensure that all Verify HTTPS Certificate(s) parameters in a workspace are set to Yes.

Note  
  • On MacOS, requests to some servers will not work unless this parameter is set to Yes.
  • The value of the Verify HTTPS Certificate parameter takes priority over the value of the Verify SSL Certificates parameter, which may be defined by the Web Connection used with this format.

Schema Attributes

Use this parameter to expose Format Attributes in FME Workbench when you create a workspace:

  • In a dynamic scenario, it means these attributes can be passed to the output dataset at runtime.
  • In a non-dynamic scenario, this parameter allows you to expose additional attributes on multiple feature types. Click the browse button to view the available format attributes (which are different for each format) for the reader.