Migrated VB Apps: Binding DataTable Columns still does not work

Feedback Apps
, , , ,
1

I see that this topic to bind the columns of the DataTable type output of an automation is not working under certain conditions.

The solution as described by @Arvind_Kumar1 in this post UiPath Apps binding datatable issue - missing column - #2 by Arvind_Kumar1
should work but, it does not under the following conditions:

  1. If I migrate a legacy App to VB Apps, and then add a completely new process after having run that process multiple times from Orchestrator (and assistant), the newly ported VB App does not recognize the fields no matter how many times the Process has been added and removed from the App
  2. Another factor that I’m not sure fully if it plays a role or not is that my Automation posts the DataTable as in Interim Results update to the App.

I have thus far tried several times to make the migrated App identify the columns of the DataTable output of the process, but to no avail.

I have since added the fields manually, but then if the process is refreshed those manual additions will go away which means that the App will lose binding to the data.

Could this be a bug specific to migrated Apps? At the moment it’s not practical for me to scratch build an entirely new VB App to check if that would fix the problem.

Thanks!

3

And this is something related and therefore posting it in this thread. I have confirmed this
by making deliberate changes to the process arguments.

Just as I migrated the App, I also migrated its related Automation project to Windows.

After the migration, this is what I noticed in the Main.xaml.json file:

Any argument added or renamed in the migrated solution does not have a Widget type:

The image shows a JSON configuration file with key-value pairs defining attributes for three different outputs, each highlighted with a yellow cross mark next to the "Widget" attribute set to null. (Captioned by AI)
The image shows a JSON configuration file with key-value pairs defining attributes for three different outputs, each highlighted with a yellow cross mark next to the "Widget" attribute set to null. (Captioned by AI)850×1665 46.7 KB

And anything that was left untouched after the migration has a valid Widget type:

This image shows a JSON snippet defining arguments with properties such as "Name," "DisplayName," "Widget," "IsRequired," and others, where green checkmarks indicate the "Widget" values set as "Number" or "TextComposer." (Captioned by AI)
This image shows a JSON snippet defining arguments with properties such as "Name," "DisplayName," "Widget," "IsRequired," and others, where green checkmarks indicate the "Widget" values set as "Number" or "TextComposer." (Captioned by AI)862×1570 56.9 KB

I’m hoping this is not going to be a problem with project migrations?

Thanks

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