Microsoft Azure Files (Beta) Get File activity

Introduction

A Microsoft Azure Files (Beta) Get File activity, using its Microsoft Azure Files (Beta) connection, retrieves a file from a Microsoft Azure Files file share and is intended to be used as a source in an operation.

Create a Microsoft Azure Files (Beta) Get File activity

An instance of a Microsoft Azure Files (Beta) Get File activity is created from a Microsoft Azure Files (Beta) connection using its Get File activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.

An existing Microsoft Azure Files (Beta) Get File activity can be edited from these locations:

• The design canvas (see Component actions menu in Design canvas).
• The project pane's Components tab (see Component actions menu in Project pane Components tab).

Configure a Microsoft Azure Files (Beta) Get File activity

Follow these steps to configure a Microsoft Azure Files (Beta) Get File activity:

• Step 1: Enter a name and select a file share
  Provide a name for the activity and select a file share.

• Step 2: Review the data schemas
  Any request or response schemas are displayed.

Step 1: Enter a name and select a file Share

In this step, provide a name for the activity and select a file share. Each user interface element of this step is described below.

• Name: Enter a name to identify the activity. The name must be unique for each Microsoft Azure Files (Beta) Get File activity and must not contain forward slashes / or colons :.

• Select a File Share: This section displays file shares available in the Microsoft Azure Files (Beta) endpoint.

  • Selected object: After a file share is selected, it is listed here.

  • Search: Enter any column's value into the search box to filter the list of file shares. The search is not case-sensitive. If file shares are already displayed within the table, the table results are filtered in real time with each keystroke. To reload file shares from the endpoint when searching, enter search criteria and then refresh, as described below.

  • Refresh: Click the refresh icon or the word Refresh to reload file shares from the Microsoft Azure Files (Beta) endpoint. This may be useful if file shares have been added to Microsoft Azure Files (Beta). This action refreshes all metadata used to build the table of file shares displayed in the configuration.

  • Selecting a File Share: Within the table, click anywhere on a row to select a file share. Only one file share can be selected. The information available for each file share is fetched from the Microsoft Azure Files (Beta) endpoint:

    • Name: The name of the file share.

    • Modified: The timestamp of when the file share was last modified.

  Tip

  If the table does not populate with available file shares, the Microsoft Azure Files (Beta) connection may not be successful. Ensure you are connected by reopening the connection and retesting the credentials.

• Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

• Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the data schemas

Any request or response schemas are displayed. Each user interface element of this step is described below.

• Data schema: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

  Note

  Data supplied in a transformation takes precedence over the activity configuration.

  The Microsoft Azure Files (Beta) connector uses the Microsoft Azure Files REST API. Refer to the API documentation for information on the schema nodes and fields.

• Refresh: Click the refresh icon or the word Refresh to regenerate schemas from the Microsoft Azure Files (Beta) endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

• Back: Click to temporarily store the configuration for this step and return to the previous step.

• Finished: Click to save the configuration for all steps and close the activity configuration.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next steps

After configuring a Microsoft Azure Files (Beta) Get File activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

Microsoft Azure Files (Beta) Get File activities can be used as a source with these operation patterns:

• Transformation pattern
• Two-target archive pattern (as the first source only)
• Two-target HTTP archive pattern (as the first source only)
• Two-transformation pattern (as the first or second source)

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.