1. To-Increase Dynamics 365 for Finance & Operations
  2. EDI studio
  3. Flows

Set up file actions for Azure file storage connector
Activity Flow

With a Azure file storage connector, you exchange files between your D365 FO environment and another environment via an Azure file share or a local folder. If the other environment has no access to the Azure file share or local folder, you can use file actions to transfer the files to a location where the other environment can access the files.

Each file action has one direction. The file action direction defines when the action is applicable. If the direction is:
  • Source, the file action is done:
    • Only if the connector is used as source connector on a message.
    • Before the message is run.
  • Target, the file action is done
    • Only if the connector is used as target connector on a message.
    • After the message is run.
The file actions are done in the sequence as shown in the grid. To put the file actions in the correct sequence, use Move up and Move down.

Application Consultant Application Consultant Start Start Set up file action - Copy Set up file action - Copy You can use the Copy file action to copy a file to another location.If the direction is:Source, before the message is run, the file is copied from a defined folder to the Working folder. The original file stays in the defined folder.Target, after the message is run, the created file is copied from the Working folder to the defined folder. The original file stays in the Working folder. Procedure 1. Click Connectivity studio Integration Design. 2. Click the Connectors tab. 3. In the list, find and select the desired connector of type Azure file storage. 4. Click Edit. 5. You can export connectivity setup and import it in another D365 FO environment. For example, you first set up and test the connectivity setup in a development environment. When finished, you deploy the setup in your production environment. To prevent messing up your production data, use different file locations for your development or testing environment and for your production environment. To strictly distinguish between different environments, you can define unique file action properties for each of your environment types. So, each file action can have a different set of properties for each applicable environment type. Which file action properties are applicable to the current environment is defined in the Environment type field on the Connectivity studio parameters. Example: If set to Development, the file action properties, as defined for environment type Development are applicable. In the Environment types field, select an option. Note: For each file action, you can repeat the sub-tasks for each of your environment types. To set the environment-specific properties of a file action, only change the environment type, find the file action, and set the properties. So, do not create a new file action for each environment type. 6. Expand the File action section. 7. Sub-task: Set up a Copy file action with direction Source. 8. Click New. 9. In the Name field, type a value. 10. Click Save. 11. In the File name field, type a value. 12. Select Yes in the Skip field. 13. Enter the UNC path to the applicable Azure file share or Windows folder. In the Share field, type a value. Note: You can only use a Windows folder if it has access control with a user and password defined. 14. In the User name field, type a value. 15. Define the password or the password reference to access the Azure file share or Windows folder. Whether the password or password reference applies is defined by the Display secret field in the Connectivity studio parameters. If the Display secret parameter is set to: - Secret, fill in the Password field with the desired password or access key. The password or access key is specific for the current file action. - Secret reference, fill in the Password reference field with the desired secret reference. The password reference refers to a centrally stored password or access key which makes updating secrets easier. - Both, fill in either the Password field or the Password reference field. In the Password field, or in the Password reference field, type a value. Note: To access an Azure file share, the password is the key, or the password reference refers to the key of the applicable Azure Storage Account. 16. In the Working path field, enter or select a value. 17. Sub-task: Set up a Copy file action with direction Target. 18. Click New. 19. In the Name field, type a value. 20. Click Save. 21. In the Direction field, select 'Target'. 22. Click Save. 23. Select Yes in the Skip field. 24. Enter the UNC path to the applicable Azure file share or Windows folder. In the Share field, type a value. Note: You can only use a Windows folder if it has access control with a user and password defined. 25. In the User name field, type a value. 26. Define the password or the password reference to access the Azure file share or Windows folder. Whether the password or password reference applies is defined by the Display secret field in the Connectivity studio parameters. If the Display secret parameter is set to: - Secret, fill in the Password field with the desired password or access key. The password or access key is specific for the current file action. - Secret reference, fill in the Password reference field with the desired secret reference. The password reference refers to a centrally stored password or access key which makes updating secrets easier. - Both, fill in either the Password field or the Password reference field. In the Password field, or in the Password reference field, type a value. Note: To access an Azure file share, the password is the key, or the password reference refers to the key of the applicable Azure Storage Account. 27. In the Working path field, enter or select a value. 28. Close the page. 29. Close the page. Set up file action - Move Set up file action - Move You can use the Move file action to move a file to another location.If the direction is:Source, before the message is run, the file is moved from a defined folder to the Working folder.Target, after the message is run, the created file is moved from the Working folder to the defined folder. Procedure 1. Click Connectivity studio Integration Design. 2. Click the Connectors tab. 3. In the list, find and select the desired connector of type Azure file storage. 4. Click Edit. 5. You can export connectivity setup and import it in another D365 FO environment. For example, you first set up and test the connectivity setup in a development environment. When finished, you deploy the setup in your production environment. To prevent messing up your production data, use different file locations for your development or testing environment and for your production environment. To strictly distinguish between different environments, you can define unique file action properties for each of your environment types. So, each file action can have a different set of properties for each applicable environment type. Which file action properties are applicable to the current environment is defined in the Environment type field on the Connectivity studio parameters. Example: If set to Development, the file action properties, as defined for environment type Development are applicable. In the Environment types field, select an option. Note: For each file action, you can repeat the sub-tasks for each of your environment types. To set the environment-specific properties of a file action, only change the environment type, find the file action, and set the properties. So, do not create a new file action for each environment type. 6. Expand the File action section. 7. Sub-task: Set up a Move file action with direction Source. 8. Click New. 9. In the Name field, type a value. 10. In the File action field, select 'Move'. 11. Click Save. 12. In the File name field, type a value. 13. Select Yes in the Skip field. 14. Enter the UNC path to the applicable Azure file share or Windows folder. In the Share field, type a value. Note: You can only use a Windows folder if it has access control with a user and password defined. 15. In the User name field, type a value. 16. Define the password or the password reference to access the Azure file share or Windows folder. Whether the password or password reference applies is defined by the Display secret field in the Connectivity studio parameters. If the Display secret parameter is set to: - Secret, fill in the Password field with the desired password or access key. The password or access key is specific for the current file action. - Secret reference, fill in the Password reference field with the desired secret reference. The password reference refers to a centrally stored password or access key which makes updating secrets easier. - Both, fill in either the Password field or the Password reference field. In the Password field, or in the Password reference field, type a value. Note: To access an Azure file share, the password is the key, or the password reference refers to the key of the applicable Azure Storage Account. 17. In the Working path field, enter or select a value. 18. Sub-task: Set up a Move file action with direction Target. 19. Close the page. 20. Click New. 21. In the Name field, type a value. 22. In the File action field, select 'Move'. 23. Click Save. 24. In the Direction field, select 'Target'. 25. Click Save. 26. Select Yes in the Skip field. 27. Enter the UNC path to the applicable Azure file share or Windows folder. In the Share field, type a value. Note: You can only use a Windows folder if it has access control with a user and password defined. 28. In the User name field, type a value. 29. Define the password or the password reference to access the Azure file share or Windows folder. Whether the password or password reference applies is defined by the Display secret field in the Connectivity studio parameters. If the Display secret parameter is set to: - Secret, fill in the Password field with the desired password or access key. The password or access key is specific for the current file action. - Secret reference, fill in the Password reference field with the desired secret reference. The password reference refers to a centrally stored password or access key which makes updating secrets easier. - Both, fill in either the Password field or the Password reference field. In the Password field, or in the Password reference field, type a value. Note: To access an Azure file share, the password is the key, or the password reference refers to the key of the applicable Azure Storage Account. 30. In the Working path field, enter or select a value. 31. Close the page. 32. Close the page. Set up file action - Delete Set up file action - Delete You can use the Delete file action to delete a file from the Working folder. Usually, the Delete file action is the last one to be done.If the connector is set up properly with a different folder defined for Working path, Archive path, and Error path, a Delete file action is not required for direction Source.If the direction is Target, after the message is run, the created file is deleted from the Working folder. Procedure 1. Click Connectivity studio Integration Design. 2. Click the Connectors tab. 3. In the list, find and select the desired connector of type Azure file storage. 4. Click Edit. 5. You can export connectivity setup and import it in another D365 FO environment. For example, you first set up and test the connectivity setup in a development environment. When finished, you deploy the setup in your production environment. To prevent messing up your production data, use different file locations for your development or testing environment and for your production environment. To strictly distinguish between different environments, you can define unique file action properties for each of your environment types. So, each file action can have a different set of properties for each applicable environment type. Which file action properties are applicable to the current environment is defined in the Environment type field on the Connectivity studio parameters. Example: If set to Development, the file action properties, as defined for environment type Development are applicable. In the Environment types field, select an option. Note: For each file action, you can repeat the sub-tasks for each of your environment types. To set the environment-specific properties of a file action, only change the environment type, find the file action, and set the properties. So, do not create a new file action for each environment type. 6. Expand the File action section. 7. Sub-task: Set up a Delete file action with direction Target. 8. Click New. 9. In the Name field, type a value. 10. In the File action field, select 'Delete'. 11. Click Save. 12. In the Direction field, select 'Target'. 13. Click Save. 14. Select Yes in the Skip field. 15. Close the page. Set up file action - Zip Set up file action - Zip You can use the Zip file action to zip or unzip a file in the Working folder. You can use this, for example, in combination with the Email file action to send or receive zipped files using email.If the direction is:Source, before the message is run, the file is unzipped to the Working folder. The original ZIP file stays in the Working folder.Target, after the message is run, the created file is zipped to the Working folder. The original file is deleted from the Working folder. Next file actions in the file action sequence are done with the ZIP file. Procedure 1. Click Connectivity studio Integration Design. 2. Click the Connectors tab. 3. In the list, find and select the desired connector of type Azure file storage. 4. Click Edit. 5. You can export connectivity setup and import it in another D365 FO environment. For example, you first set up and test the connectivity setup in a development environment. When finished, you deploy the setup in your production environment. To prevent messing up your production data, use different file locations for your development or testing environment and for your production environment. To strictly distinguish between different environments, you can define unique file action properties for each of your environment types. So, each file action can have a different set of properties for each applicable environment type. Which file action properties are applicable to the current environment is defined in the Environment type field on the Connectivity studio parameters. Example: If set to Development, the file action properties, as defined for environment type Development are applicable. In the Environment types field, select an option. Note: For each file action, you can repeat the sub-tasks for each of your environment types. To set the environment-specific properties of a file action, only change the environment type, find the file action, and set the properties. So, do not create a new file action for each environment type. 6. Expand the File action section. 7. Sub-task: Set up a Zip file action with direction Source. 8. Click New. 9. In the Name field, type a value. 10. In the File action field, select 'Zip'. 11. Click Save. 12. In the File name field, type a value. 13. Select Yes in the Skip field. 14. Sub-task: Set up a Zip file action with direction Target. 15. Click New. 16. In the Name field, type a value. 17. In the File action field, select 'Zip'. 18. Click Save. 19. In the Direction field, select 'Target'. 20. Click Save. 21. Select Yes in the Skip field. 22. Close the page. Set up file action - Email

Set up file action - Email

You can use the Email file action to exchange files with email.
If the direction is:

  • Source, before the message is run, the defined email account inbox is searched for applicable emails. If found, the attached files of these emails are saved to the Working folder.
  • Target, after the message is run, an email is created using the defined email account, the created file in the Working folder is attached to the email, and the email is sent. The original file stays in the Working folder. If you want to zip the file before sending it by email, do a Zip file action previously to the Email file action. In this case the zipped file is attached to the email.
These email options are available:
  • Exchange server: To send or receive files using a Microsoft Exchange server.
  • IMAP server: To receive files using an IMAP server.
  • SMTP server: To send files using an SMTP server.
  • D365FO email: To send files using the email setup as defined in D365FO.

 Set up file action - FTP Set up file action - FTP FTP is no longer supported because of security reasons. Instead, use file actions of type SFTP. Set up file action - SFTP Set up file action - SFTP You can use the SFTP file action to exchange files with an SFTP server. If the direction is: Source, before the message is run, the file is downloaded from the SFTP server to the Working folder. By default, the original file is deleted from the SFTP server. You can disable the delete action of the original file. Target, after the message is run, the file is uploaded from the Working folder to the SFTP server. The original file stays in the Working folder. If you want to zip the file before uploading it to the SFTP server, do a Zip file action previously to the SFTP file action. In this case the zipped file is uploaded to the SFTP server. Procedure 1. Click Connectivity studio Integration Design. 2. Click the Connectors tab. 3. In the list, find and select the desired connector of type Azure file storage. 4. Click Edit. 5. You can export connectivity setup and import it in another D365 FO environment. For example, you first set up and test the connectivity setup in a development environment. When finished, you deploy the setup in your production environment. To prevent messing up your production data, use different file locations for your development or testing environment and for your production environment. To strictly distinguish between different environments, you can define unique file action properties for each of your environment types. So, each file action can have a different set of properties for each applicable environment type. Which file action properties are applicable to the current environment is defined in the Environment type field on the Connectivity studio parameters. Example: If set to Development, the file action properties, as defined for environment type Development are applicable. In the Environment types field, select an option. Note: For each file action, you can repeat the sub-tasks for each of your environment types. To set the environment-specific properties of a file action, only change the environment type, find the file action, and set the properties. So, do not create a new file action for each environment type. 6. Expand the File action section. 7. Sub-task: Set up an SFTP file action with direction Source. 8. Click New. 9. In the Name field, type a value. 10. In the File action field, select 'SFTP'. 11. Click Save. 12. In the File name field, type a value. 13. Select Yes in the Skip field. 14. In the Server field, type a value. 15. In the Port field, enter a number. 16. In the Folder field, type a value. 17. In the User name field, type a value. 18. In the Password field, or in the Password reference field, type a value. 19. Click Upload private key and browse for the file that contains the private key certificate. Or, in the private key reference field, type or select a value. 20. Click OK. 21. In the Passphrase field, or in the Passphrase reference field, type a value. 22. Select Yes in the Disable delete field. 23. Sub-task: Set up an SFTP file action with direction Target. 24. Click New. 25. In the Name field, type a value. 26. In the File action field, select 'SFTP'. 27. Click Save. 28. In the Direction field, select 'Target'. 29. Click Save. 30. Select Yes in the Skip field. 31. In the Server field, type a value. 32. In the Port field, enter a number. 33. In the Folder field, type a value. 34. In the User name field, type a value. 35. In the Password field, or in the Password reference field, type a value. 36. Click Upload private key and browse for the file that contains the private key certificate. Or, in the private key reference field, type or select a value. 37. Click OK. 38. In the Passphrase field, or in the Passphrase reference field, type a value. 39. In the Data type field, select an option. 40. In the Target file name field, type a value. 41. In the File open mode field, select an option. 42. Close the page. Notes File actions of type FTP are no longer supported because of security reasons. Instead, use file actions of type SFTP. Set up file action - Azure Blob storage Set up file action - Azure Blob storage You can use the Azure BLOB storage file action to move a file between an Azure file share and an Azure BLOB container. You can only use an Azure BLOB storage file action if you exchange files using Azure File Storage. The applicable Azure file share is the one as defined for the connector.If the direction is:Source, before the message is run, the file is moved from the defined Azure BLOB container to the Azure file share.Target, after the message is run, the file is moved from the Azure file share to the defined Azure BLOB container. Procedure 1. Click Connectivity studio Integration Design. 2. Click the Connectors tab. 3. In the list, find and select the desired connector of type Azure file storage. 4. Click Edit. 5. You can export connectivity setup and import it in another D365 FO environment. For example, you first set up and test the connectivity setup in a development environment. When finished, you deploy the setup in your production environment. To prevent messing up your production data, use different file locations for your development or testing environment and for your production environment. To strictly distinguish between different environments, you can define unique file action properties for each of your environment types. So, each file action can have a different set of properties for each applicable environment type. Which file action properties are applicable to the current environment is defined in the Environment type field on the Connectivity studio parameters. Example: If set to Development, the file action properties, as defined for environment type Development are applicable. In the Environment types field, select an option. Note: For each file action, you can repeat the sub-tasks for each of your environment types. To set the environment-specific properties of a file action, only change the environment type, find the file action, and set the properties. So, do not create a new file action for each environment type. 6. Expand the File action section. 7. Sub-task: Set up an Azure BLOB Storage file action with direction Source. 8. Click New. 9. In the Name field, type a value. 10. In the File action field, select 'Azure blob storage'. 11. Click Save. 12. In the File name field, type a value. 13. Select Yes in the Skip field. 14. In the Account name field, type a value. 15. In the Account key field, or in the Account key reference field, type a value. 16. In the Container name field, type a value. 17. Sub-task: Set up an Azure BLOB Storage file action with direction Target. 18. Click New. 19. In the Name field, type a value. 20. In the File action field, select 'Azure blob storage'. 21. Click Save. 22. In the Direction field, select 'Target'. 23. Click Save. 24. Select Yes in the Skip field. 25. In the Account name field, type a value. 26. In the Account key field, or in the Account key reference field, type a value. 27. In the Container name field, type a value. 28. Close the page. End End

Activities

Name Responsible Description

Set up file action - Copy

Application Consultant

 		You can use the Copy file action to copy a file to another location.
If the direction is:
  • Source, before the message is run, the file is copied from a defined folder to the Working folder. The original file stays in the defined folder.
  • Target, after the message is run, the created file is copied from the Working folder to the defined folder. The original file stays in the Working folder.

Set up file action - Move

Application Consultant

 		You can use the Move file action to move a file to another location.
If the direction is:
  • Source, before the message is run, the file is moved from a defined folder to the Working folder.
  • Target, after the message is run, the created file is moved from the Working folder to the defined folder.

Set up file action - Delete

Application Consultant

 		You can use the Delete file action to delete a file from the Working folder. Usually, the Delete file action is the last one to be done.
If the connector is set up properly with a different folder defined for Working path, Archive path, and Error path, a Delete file action is not required for direction Source.
If the direction is Target, after the message is run, the created file is deleted from the Working folder.

Set up file action - Zip

Application Consultant

 		You can use the Zip file action to zip or unzip a file in the Working folder. You can use this, for example, in combination with the Email file action to send or receive zipped files using email.
If the direction is:
  • Source, before the message is run, the file is unzipped to the Working folder. The original ZIP file stays in the Working folder.
  • Target, after the message is run, the created file is zipped to the Working folder. The original file is deleted from the Working folder. Next file actions in the file action sequence are done with the ZIP file.

Set up file action - Email

Application Consultant

 		You can use the Email file action to exchange files with email.
If the direction is:
  • Source, before the message is run, the defined email account inbox is searched for applicable emails. If found, the attached files of these emails are saved to the Working folder.
  • Target, after the message is run, an email is created using the defined email account, the created file in the Working folder is attached to the email, and the email is sent. The original file stays in the Working folder. If you want to zip the file before sending it by email, do a Zip file action previously to the Email file action. In this case the zipped file is attached to the email.
These email options are available:
  • Exchange server: To send or receive files using a Microsoft Exchange server.
  • IMAP server: To receive files using an IMAP server.
  • SMTP server: To send files using an SMTP server.
  • D365FO email: To send files using the email setup as defined in D365FO.

Set up file action - FTP

Application Consultant

 		FTP is no longer supported because of security reasons. Instead, use file actions of type SFTP.

Set up file action - SFTP

Application Consultant
You can use the SFTP file action to exchange files with an SFTP server.
If the direction is:
  • Source, before the message is run, the file is downloaded from the SFTP server to the Working folder. By default, the original file is deleted from the SFTP server. You can disable the delete action of the original file.
  • Target, after the message is run, the file is uploaded from the Working folder to the SFTP server. The original file stays in the Working folder. If you want to zip the file before uploading it to the SFTP server, do a Zip file action previously to the SFTP file action. In this case the zipped file is uploaded to the SFTP server.

Set up file action - Azure Blob storage

Application Consultant
You can use the Azure BLOB storage file action to move a file between an Azure file share and an Azure BLOB container. You can only use an Azure BLOB storage file action if you exchange files using Azure File Storage. The applicable Azure file share is the one as defined for the connector.
If the direction is:
  • Source, before the message is run, the file is moved from the defined Azure BLOB container to the Azure file share.
  • Target, after the message is run, the file is moved from the Azure file share to the defined Azure BLOB container.

Activities

Name Responsible Description

Set up file action - Copy

Application Consultant

 		You can use the Copy file action to copy a file to another location.
If the direction is:
  • Source, before the message is run, the file is copied from a defined folder to the Working folder. The original file stays in the defined folder.
  • Target, after the message is run, the created file is copied from the Working folder to the defined folder. The original file stays in the Working folder.

Set up file action - Move

Application Consultant

 		You can use the Move file action to move a file to another location.
If the direction is:
  • Source, before the message is run, the file is moved from a defined folder to the Working folder.
  • Target, after the message is run, the created file is moved from the Working folder to the defined folder.

Set up file action - Delete

Application Consultant

 		You can use the Delete file action to delete a file from the Working folder. Usually, the Delete file action is the last one to be done.
If the connector is set up properly with a different folder defined for Working path, Archive path, and Error path, a Delete file action is not required for direction Source.
If the direction is Target, after the message is run, the created file is deleted from the Working folder.

Set up file action - Zip

Application Consultant

 		You can use the Zip file action to zip or unzip a file in the Working folder. You can use this, for example, in combination with the Email file action to send or receive zipped files using email.
If the direction is:
  • Source, before the message is run, the file is unzipped to the Working folder. The original ZIP file stays in the Working folder.
  • Target, after the message is run, the created file is zipped to the Working folder. The original file is deleted from the Working folder. Next file actions in the file action sequence are done with the ZIP file.

Set up file action - Email

Application Consultant

 		You can use the Email file action to exchange files with email.
If the direction is:
  • Source, before the message is run, the defined email account inbox is searched for applicable emails. If found, the attached files of these emails are saved to the Working folder.
  • Target, after the message is run, an email is created using the defined email account, the created file in the Working folder is attached to the email, and the email is sent. The original file stays in the Working folder. If you want to zip the file before sending it by email, do a Zip file action previously to the Email file action. In this case the zipped file is attached to the email.
These email options are available:
  • Exchange server: To send or receive files using a Microsoft Exchange server.
  • IMAP server: To receive files using an IMAP server.
  • SMTP server: To send files using an SMTP server.
  • D365FO email: To send files using the email setup as defined in D365FO.

Set up file action - FTP

Application Consultant

 		FTP is no longer supported because of security reasons. Instead, use file actions of type SFTP.

Set up file action - SFTP

Application Consultant
You can use the SFTP file action to exchange files with an SFTP server.
If the direction is:
  • Source, before the message is run, the file is downloaded from the SFTP server to the Working folder. By default, the original file is deleted from the SFTP server. You can disable the delete action of the original file.
  • Target, after the message is run, the file is uploaded from the Working folder to the SFTP server. The original file stays in the Working folder. If you want to zip the file before uploading it to the SFTP server, do a Zip file action previously to the SFTP file action. In this case the zipped file is uploaded to the SFTP server.

Set up file action - Azure Blob storage

Application Consultant
You can use the Azure BLOB storage file action to move a file between an Azure file share and an Azure BLOB container. You can only use an Azure BLOB storage file action if you exchange files using Azure File Storage. The applicable Azure file share is the one as defined for the connector.
If the direction is:
  • Source, before the message is run, the file is moved from the defined Azure BLOB container to the Azure file share.
  • Target, after the message is run, the file is moved from the Azure file share to the defined Azure BLOB container.
Related to Notes

Re-run file actions

 		 

Provide feedback