You have the DWG file and the DWF file. Now you have to add the link between the two, which is what AddDesignVisualizationFileAttachment does.
The first parameter is the ID of the parent file, which is the DWG. The second parameter is the association to the child DWF file. For the second parameter, create a new FileAssocParam class and fill in all the fields except for RefId and Source. You can leave those null.
CldFileId is the ID of the DWF file. ExpectedVaultPath is the full path to the DWF in Vault. Typ should be Attachment.
The problem still persists.
1) i check out the dwf file.
2)When its copied to local system, i make some changes.
3)I check in the file to vault
4)Then i execute AddDesignVisualizationFileAttachment with all paramaters you specified, yet there is no connection between dwg and dwf. The associativity is lost between two files.
This works fine if I stick to the naming convention e.i., "part1.ipt" / "part1.ipt.dwf"
But using a custom naming scheme for the designvisualization e.g., "part1_test.ipt.dwf" breaks the link to the preview pane.
Is this the expected behavior or am I missing something?
( Vault Basic 2013 )
I never tested with different naming conventions, till today i tested with the same naming conventions as customer requirement and the behaviour is not known to me.
I will test the same this weekend and reply the same to you.
Thanks for your reply & interest. Did you hit the same limitations? My assumption is, that the preview pane is restricted to the specific namingconvention.
I tested the same and its working fine. As far as the you explicitly attach the dwf/dwfx file to dwg/ipt, it works fine.
Just make sure the extensions are right and you are attaching the dwf to ipt/dwg properly. Even a minor bug does not attach the dwf to dwg/ipt.
With Best Regards
Big thanks for your efforts!
I´m using AddDesignVisualizationFileAttachment as suggested by Doug after both files are checked-in. Everything looks right & no "bugs" as far as I can see. It´s just the preview pane I can´t seem to "syncronize", when I´m using a custom naming scheme?. Guess I´ll need some more try & error to get it right