What is most reliable chart or group identifier in workbook

Dear Aspose.
Would like to ask about recommendation for most reliable chart / group identifier (once set for chart or group, stays the same all its life-cycle).

In our scenario - we want to store such identifier externally to retrieve particular chart later.
Unfortunately for example Chart.Name (visible in selection pane) can be duplicit even at the very same sheet.

Thanks for reply.

Kind Regards
P.

@ottap
The “createId” property in the file is not visible and unique in excel. And opening and saving does not change its value.

        	    <xdr:cNvPr id="5" name="Chart 4">
            					<a:extLst>
            						<a:ext uri="{FF2B5EF4-FFF2-40B4-BE49-F238E27FC236}">
            							<a16:creationId xmlns:a16="http://schemas.microsoft.com/office/drawing/2014/main" xmlns="" id="{A378FA00-4A13-50D7-0534-96EB1C93424D}"/>
            						</a:ext>
            					</a:extLst>
            				</xdr:cNvPr>

If this property supports your need, we plan to support this property. We will automatically add one if this attribute is not present in the file,

Hi Simon,
thanks for answer.

Can you provide us the name of mentioned property in Aspose (with usage example) and also the version of Aspose.Cells since we can use one, please?

Thank you very much

@ottap,

Thanks for your confirmation.

We have logged a ticket with an id “CELLSNET-51226” to add/support relevant identifier attribute (as we proposed in our previous reply) for chart/group in Excel spreadsheet for your requirements. We will implement it first and then share the details about property name with usage example. This might be supported in upcoming version (e.g. Aspose.Cells for .NET v22.6) or hot fixes.

Once we have an update on it, we will let you know here.

@ottap
xls doesn’t support createid attribute, so this attribute only works on xlsx, xlsm, xlsb.

@ottap
Please try the latest version.
We have added Shape.CreateId property.

The issues you have found earlier (filed as CELLSNET-51226) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi