When I run “IXP.xaml” directly, it works correctly.
However, when I try to call IXP.xaml from DataExtraction.xaml using Invoke Workflow File , I get the following error:
Load Taxonomy: Could not load type ‘UiPath.SmartData.Telemetry.Events.LoadTaxonomy.DocumentConnectionsInfo’ from assembly ‘UiPath.SmartData.Telemetry, Version=7.2.0.0, Culture=neutral, PublicKeyToken=null’.
This looks like a package/version mismatch issue. Since IXP.xaml runs independently but fails when invoked from DataExtraction.xaml, check whether both workflows are using the same versions of Document Understanding/Intelligent Xtraction packages.
Try opening Manage Packages, updating/reinstalling the DU-related packages, and ensuring both workflows are in the same project with matching dependencies. A project dependency repair may also help.
Can you please tell what are present in each xaml..specifically if you have any arguments and if you are not passing those values while calling it would fails
I already checked and aligned the package versions yesterday. Both workflows are located in the same project and share the same dependencies. I also tried restoring/reinstalling the Document Understanding and IntelligentOCR packages.
I also noticed that my child workflow IXP.xaml uses the Extract Document Data activity, which requires UiPath.DocumentUnderstanding.Activities v3.2.0-preview .
In Manage Packages, this package shows: “Package version not found in any feed” .
My parent workflow DataExtraction.xaml still uses classic Document Understanding activities such as Load Taxonomy . So I suspect there may be an incompatibility between the package required by Extract Document Data in IXP.xaml and the DU package dependencies used by DataExtraction.xaml .
Could this package/version incompatibility explain why IXP.xaml works alone but fails when invoked from DataExtraction.xaml ?
Hey, you cannot use both DocumentUnderstanding.Activities as well as IntelligentOCR.Activities within the same project.
If you run windows robots, replace your extract document data with a data extraction scope + du project extractor, it does the same thing…