[InfoSet] - LegacyToWindows Migration # Issue - Mapping Set - Fix Tracker

This post is currently in a preview version.
New statuses are checked regularly and trackers are updated

Introduction

In the past, problems have been observed within legacy-to-Windows code conversions. Workarounds have been found for some of these problems. From this, a mapping set could be derived. At a later time fixes were realized and the problems were remedied.

In this part of the [InfoSet] - LegacyToWindows Migration series, the issue, and the related progress are tracked.

Scope

Within the scope:

  • Official UiPath Activities
  • Official UiPath Packages
  • Issues caused by the UiPath Legacy to Windows converter tool

Out of scope:

  • Third-party packages
  • Differences from the code platform such as .NET 6

UiPath Activities

Activtiy Issue Workaround / mapping set Fix Comment
Read / Write / Append to CSV File Custom Enconding Usage is not recognized TroubleShooting 2.11 Docu Effect could be confirmed at least once
Read / Write / Append Line TextFile Custom Enconding Usage is not recognized TroubleShooting 2.11 Docu Effect could not be confirmed so far
Invoke Workflow File Dynamic File Path - Variables within the filepath TroubleShooting 2.5 Announcement n/a

UiPath Packages

Package Status Comment
UiPath.SAP.BAPI.Activities No available compatibility for Windows Missing SAP Connector on Windows compatible base Read more

References

Questions

For questions on your specific case or migration topic open a new topic and get individual support.

3 Likes