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

Monitor file history
Activity Flow

You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history.
Registered file actions are the:
  • Standard file actions related to the Working, Archive, Error, and Split folders. For example, on import, a file is read from the Working folder and when successfully processed, it is moved to the Archive folder. Both the 'read' and the 'move' action are registered.
  • Additional file actions as set up for the Azure file storage connector.
You can monitor the file history from the Connectivity studio Integration operations workspace.

Application Consultant Application Consultant Start Start View file history View file history You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history. Registered file actions are the: Standard file actions related to the Working, Archive, Error, and Split folders. For example, on import, a file is read from the Working folder and when successfully processed, it is moved to the Archive folder. Both the 'read' and the 'move' action are registered. Additional file actions as set up for the Azure file storage connector. Procedure 1. Click Connectivity studio Integration operations. 2. On the History errors tab, in the list, find and select the desired message run. 3. Click File history. Note: You can also open the File history from several other places. For example, from the Message page and the History management page. 4. Close the page. Do you want to  review the file? Do you want to  review the file? Use file explorer Use file explorer You can use the File explorer to quickly access and view the share as defined for the applicable Azure file storage connector. The File explorer offers limited functionality. You can only view, copy, move, or delete files. Procedure 1. Click Connectivity studio Integration operations. 2. On the History errors tab, in the list, find and select the desired message run. 3. Click File history. 4. On the Action pane, on the File history tab, click File explorer. Note: You can also open the File explorer from several other places. For example, from the Connector page and from the Message page. 5. Close the page. Errors occurred  on file actions? Errors occurred  on file actions? Solve errors Solve errors Solve the file action errors that occurred during the message run. Re-run file actions Re-run file actions On a message, you can use a connector of type Azure file storage. For a Azure file storage connector, you can set up several file actions. These file actions are run in the defined sequence. If one of the file actions fails, the next file actions are not run. After you have solved the errors that caused the file action to fail, you can re-run the file actions of the message. Procedure 1. Click Connectivity studio Integration operations. 2. On the History errors tab, in the list, find and select the desired message run. 3. Click File history. 4. On the Action Pane, click File history. 5. Click Rerun flow actions. 6. On the dialog, fill in the fields as desired and click OK. 7. Close the page. End End Yes No Yes No

Activities

Name Responsible Description

View file history

Application Consultant
You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history.
Registered file actions are the:
  • Standard file actions related to the Working, Archive, Error, and Split folders. For example, on import, a file is read from the Working folder and when successfully processed, it is moved to the Archive folder. Both the 'read' and the 'move' action are registered.
  • Additional file actions as set up for the Azure file storage connector.

Use file explorer

Application Consultant

You can use the File explorer to quickly access and view the share as defined for the applicable Azure file storage connector. The File explorer offers limited functionality. You can only view, copy, move, or delete files.

Solve errors - File actions

Application Consultant

Solve the file action errors that occurred during the message run.

Re-run file actions

Application Consultant

On a message, you can use a connector of type Azure file storage. For a Azure file storage connector, you can set up several file actions. These file actions are run in the defined sequence. If one of the file actions fails, the next file actions are not run.

After you have solved the errors that caused the file action to fail, you can re-run the file actions of the message.

Activities

Name Responsible Description

View file history

Application Consultant
You can review and analyze the file history of message runs for messages with an Azure file storage connector. All actions that are done to the related file, are registered in the file history.
Registered file actions are the:
  • Standard file actions related to the Working, Archive, Error, and Split folders. For example, on import, a file is read from the Working folder and when successfully processed, it is moved to the Archive folder. Both the 'read' and the 'move' action are registered.
  • Additional file actions as set up for the Azure file storage connector.

Use file explorer

Application Consultant

You can use the File explorer to quickly access and view the share as defined for the applicable Azure file storage connector. The File explorer offers limited functionality. You can only view, copy, move, or delete files.

Solve errors - File actions

Application Consultant

Solve the file action errors that occurred during the message run.

Re-run file actions

Application Consultant

On a message, you can use a connector of type Azure file storage. For a Azure file storage connector, you can set up several file actions. These file actions are run in the defined sequence. If one of the file actions fails, the next file actions are not run.

After you have solved the errors that caused the file action to fail, you can re-run the file actions of the message.

Provide feedback