Migrated VB Apps: Binding DataTable Columns still does not work

Feedback Apps
, , , ,
4

Hello again,

I’ve confirmed that the App is able to automatically recognize the fields of the Data Table output of a Process if:

  1. I scratch build a new UiPath VB App and a new Windows Process
  2. Deploy the process and run it just once
  3. Going back to the App and adding the Process to it

Brand new Windows Process (run only once from orchestrator):

A screenshot of a task management interface showing two processes, one Unattended and one Attended, both with a 'Success' state, and the source of the first highlighted as "Manual." (Captioned by AI)
A screenshot of a task management interface showing two processes, one Unattended and one Attended, both with a 'Success' state, and the source of the first highlighted as "Manual." (Captioned by AI)3192×257 68.2 KB

Brand new UiPath VB App (after adding the process)
For some weird reason, a string data type is set to DateTime? ?? :thinking:

The image shows a software interface with defined output arguments "StatusID" and "StatusMessage" under "out_DT_Tracker," and an added green checkmark indicating approval or success. (Captioned by AI)
The image shows a software interface with defined output arguments "StatusID" and "StatusMessage" under "out_DT_Tracker," and an added green checkmark indicating approval or success. (Captioned by AI)2337×545 34.3 KB

I’m able to get the field listings without doing anything else.

If you can reproduce this on your end and confirm that this is the case then I feel this requires some serious attention because migrating legacy Apps could be hampered by this issue.

Manually adding Data table columns in the App is not a workaround for reasons stated in my earlier post above.

thanks