How to do logging of transferred data locally

TABLE OF CONTENTS

• Introduction
• How to activate it

Introduction

The actual schedule data being transferred is subject to strict security rules and shall at no point be accessible by anyone during a transfer in the IDE service.
However, when trying to find the cause of a failed transfer, such logs can be invaluable to shed light on exactly what was transferred, and all the API traffic involved, so that the root cause can be uncovered. Therefore, the Desktop client application has an option to turn on local logging, and that they can be made available for support personnel (by attaching the zipped folder to support a ticket).

How to activate it

In the upper right corner of the Desktop Client, you find a “cogwheel” that opens the settings for local file Logging:

You need to tick the box for “Allow logging” and specify a path where logs should reside on your local machine.

Let’s look at a specific example of a generated log file for this transfer (IEAId=1151 and TransferId=680848):

The auto-generated folder name for these log files is:

IEA-1151_680848

In order to attach this folder content (blue frame) to a support ticket, you first need to zip it (red frame):

NOTE: The subfolders for this folder are named according to the host systems used for upload and download as seen below (red frames):