When I upload a zip file containing multiple SolidWorks assemblies and parts, an assembly contains the same name as my rootFile, and my rootFile is sorted later in a alphabetic order. The translator is using the wrong rootFile for the translation.
Could this be a bug in the translation service?
example.zip
├── part1.sldprt
├── part2.sldprt
├── an assy.sldasm <-- This file will be selected by translator
└── assy.sldasm <-- This file is selected as rootFile
Let's say I upload the zip file above, "example.zip"
, and then request a translation with "assy.sldasm"
as rootFile.
After completion, when I request the manifest of the translated file, the "rootFile"is now "an assy.sldasm"
.
My conclusion is that the translator matches filenames without requiring a match on the full filename.
This means, that because assy.sldasm
is sorted after an assy.sldasm
it will match to an assy.sldasm
first.
Files to replicate the issue can be sent upon request.
posting the comment as an answer for more searchable by others: Although I have not dataset of Solidworks, I can reproduce this problem with linked files of Inventor, AutoCAD or Revit. it looks translation job finds the file which contains the string rootFileName, and returns the first one (in sorted) ,instead of matching exact the string of rootFileName. Sorry for the problem. I logged it with our engineer team: DERI-5444