April 24, 2019
Dear Solid Edge Customer:
Solid Edge ST10 Maintenance Pack 13 is now available for download.
The Solid Edge Team
Maintenance Pack Version:
Solid Edge ST10 MP13
Solid Edge ST10 Maintenance Packs can be downloaded from:
To receive direct e-mail notifications for new Solid Edge Maintenance Packs, subscribe to the SFBmail notification.
For details on initiating your email subscription navigate to:
This Maintenance Pack addresses the following PRs:
PR 9316364: Cannot change length and suppression variable together
PR 9329260: Crash when reordering multiple group items into another group
PR 9370521: Assembly relationships are broken in top level when editing sub with assembly features
PR 9318362: Dimension radius not displaying correctly
PR 9382515: Drawing View Wizard Option Crashes session
PR 9265668: The specified template cannot be accessed. Please specify another template.
PR 9173544: Problem with optimized geometry, that causes problems after optimize
PR 9395289: Crashlog abort resolved in the Select tool
PR 9119041: Engineering reference – Gear Tooth thickness of compensation gear should be thicker than general gear
PR 9261665: Engineering reference – Updating a Spur gear, the pinion and gear components are getting interchanged
PR 8329150: DWG dimension lines are not trimmed when imported
PR 9290085: Multibody does not show up in Parasolid conversion
PR 9354990: Unable to save as DWG
===Teamcenter Integration for Solid Edge===
PR 9308247: SESE aborts when clicked on revise selected
PR 9315592: Project assign is cleared when uploading without displaying the CPD.
PR 9315778: Switching "Show View" to "Parts List" in SESE aborts
PR 9339858: Use SE MP12 still not support dynamic list of values
PR 9383281: Solid edge is getting crash randomly
PR 9387708: ATTI does not start the import of the file if manifest file exists in the directory
PR 9406962: SaveAs fails if target ASM contains PAR which different rev is C/O to the cache.
PR 9394831: Project removed when revising via structure editor
PR 9384656: Clear attributes on SaveAs (Do not map NULL) does not work for Inter Parts Link data
PR 9402248: User Settings does not work like RAC and requires the command to run 2x to complete
PR 9323959: Preference SEEC_Enable_MultipleRevision=1 breaking Solid Edge links.
PR 9309476: Tc Project Update On Other User Data Is Displaying Error Message In SE
PR 9342992: Assembly JT creation is very slow when a harness is present
PR 9240326: BOM line error with adjustable assembly
PR 9428205: Solid Edge crashed while doing Multi - body Publish
Hi @JFred ,
I can't find any more about PR 9323959 (Preference SEEC_Enable_MultipleRevision=1 breaking Solid Edge links) on GTAC, from the headline it sounds like it might fix an issue we've been having.
Could you direct me to where I can see more information please?
@Alex_H from the PR notes...
Description: The preference SEEC_Enable_MultipleRevision with value 1 enables opening multiple revisions of the same part number in Solid Edge. But in some cases, our customer has identified that the links of a Solid Edge assembly or draft can break due to the renaming of the files downloaded to the SEEC cache. We have been able to reproduce the issue in our own setup and we have recorded a short video to show you a possible (likely not the only one) workflow that leads to the breaking of links between Solid Edge assemblies and parts.
Steps To Reproduce:
1. Set SEEC_Enable_MultipleRevisions to 1
2. Create an assembly and add the first revision of a part to it
3. Open the assembly as Precise (or Latest Working) in Solid Edge
4. Open the second revision of the part in Solid Edge
5. With the second revision still opened, replace the part in the assembly for its second revision
6. Save, check in and close the Solid Edge opened files.
7. Clear the cache
8. Reopen the assembly as Precise, it will report missing files.
As I mentioned earlier, we do not think this is the only way to reproduce the issue, but it is the easiest way I have found to do so. The 7th step is critical, because if the cache is not cleared, the renamed file still lays there and the assembly will open normally. Our customer first noticed the issue when another user (different from the original designer) tried to open an affected assembly, the original designer could open it normally, but any other user got the missing files dialog shown on screen.