Bug in Revit 2013 - RevisionNumberingSequence

[hzamani]

Just reporting an issue I came across today with seems to be a bug.

In Revit 2023 getting the RevisionNumberSeuquenceId of a Revision that's set to None will return -1.

I was using this code in previous versions with no issues but in 2023 the casting will be null in the case mentioned.

var revSeqId = revision.RevisionNumberingSequenceId;
var revSeqEl = doc.GetElement(revSeqId) as RevisionNumberingSequence;

I haven't tested this in Revit 2024.

Thanks.

Hoss

[jeremy_tammik]

Yes. -1 is an invalid element id:

• https://www.revitapidocs.com/2024/08ae8886-6ab3-3ef5-d2e0-0da2ffa7bd2c.htm

This sounds like expected behaviour to me. 

Please check the element id you receive and compare it with InvalidElementId before trying to retrieve a corresponding database element.

[hzamani]

Hi Jeremy,

It doesn't look normal to me for two reasons. Firstly, if that's expected how come in previous Revit version it behaves differently? 

Secondly, that specific element is needed to set the RevisionNumberingSequence of a Revision. 

Which means if a Revision is originally set to None, you won't be able to programmatically set it to Numeric or Alphanumeric, since you can't retrieve it's RevisionNumberingSequence element.

Anyways. Hope it makes sense.

Cheers.

Hoss