KB‎ > ‎

Shape Replace error after import from Visio

Ref: 201005050905 
Development Ref: 67
Defect Ref: 2612738
Last Edited: May 10th, 2012
 After an import from Visio has taken place, performing a shape replace on certain shapes will produce the error below, when the map is opened.
 System.NullReferenceException: Object reference not set to an instance of an object.
   at Triaster.ProcessNavigator.Common.ProcessObjects.Relationship.InitSecondaryProperties()
   at Triaster.ProcessNavigator.Common.ProcessObjects.MapPage.Add(Shape& shpArg, Boolean blnEnableUpgrade)
   at Triaster.ProcessNavigator.Common.ProcessObjects.Map.AddMapPage(Page pagObj, Boolean blnEnableUpgrade)
   at Triaster.ProcessNavigator.Common.ProcessObjects.Map..ctor(Document& docObj, Boolean blnEnableUpgrade)
   at Triaster.ProcessNavigator.Common.ProcessObjects.Maps.Add(Document docArg, Boolean blnEnableUpgrades, String strFullPathAndFileName)
   at Triaster.ProcessNavigator.Common.ProcessObjects.Maps.Add(Document docArg, Boolean blnEnableUpgrades)
   at Triaster.ProcessNavigator.Common.ProcessObjects.DocumentsBase.Add(Document docArg)
   at Triaster.ProcessNavigator.MappingEdition.Wrapper.clsAppEventSink.HookDocument(Document docObj)
   at Triaster.ProcessNavigator.MappingEdition.Wrapper.clsAppEventSink.VisEventProc(Int32& eventCode, Object& sourceObj, Int32& eventID, Int32& seqNum, Object& subjectObj, Object& moreInfo)
 There are connection points on a shape that are in unexpected positions, corresponding to those on the original shape that was replaced. Process Navigator doesn't handle these connection points correctly.
 This issue is resolved in Process Navigator 11.
Applies to:
  • PN 9.1 and 10.1
Related articles: