KB‎ > ‎

Import from Excel is Interrupted when Importing a Shape with Guarded Dimensions

Ref: 2633307 (201006211009)
Defect ID: 2633307
Last Edited: June 26th, 2010
 
Fixed in PN 11.2
  
Symptom:
 
A map that has been imported from Excel may show the following symptoms:
  • Property data may be missing.
  • The map layout is poor.
 
Cause:
 
The import mechanism tries to size a shape in accordance with the size set in the Excel file. However, the width and height are 'Guarded' (locked down, in Visio-speak), and an error is thrown.
 
21/06/2010 08:59:43
An exception occurred while generating a file from Catalogue XML
Cell is guarded.
System.Runtime.InteropServices.COMException (0x86DB0528):
Cell is guarded.
   at Microsoft.Office.Interop.Visio.CellClass.set_Formula(String lpbstrRet)
   at Triaster.ProcessNavigator.Common.ProcessObjects.ShapeBase.set_Height(String strNewHeight)
   at Triaster.ProcessNavigator.Common.ProcessObjects.FeedbackEmail.OutputTo(MapPage objGeneratedMapPage)
   at Triaster.ProcessNavigator.Common.ProcessObjects.MapPage.OutputTo(Map objGeneratedMap)
   at Triaster.ProcessNavigator.Common.ProcessObjects.Map.ProcessGenerateFileFromCatalogue(XmlNode xmlNodeGenerateFileFromCatalogue, XmlNode xmlCatalogueRoot)

 
No further processing of the file seems to occur, so shapes aren't positioned correctly, and properties aren't set.
 
 
Workaround:
  1. Identify the type of shape that caused the problem.
    The error message should help (see above).
  2. Open the Excel XML file in Excel.
  3. Identify the rows that correspond to that type of shape.
  4. Delete the values in the 'Height' and 'Width' cells.
    Height and Width are defined in the master on the stencil (main stencil and the template's Document stencil), and these values in Excel are just potential overrides.
  5. Save and close the file.
  6. Re-import from Excel.
 
Applies to:
  • Process Navigator 11.1 and earlier. 
 
Comments