Revit API documentation and roadmap

Yes, welcome to this Forge direction.

Personally I hate these ForgeTypeId’s, broke a lot of my code and some functionality is totally gone or no actual (good) replacement for it.

I hard coded most common used types along with the old Enums, and translated to my own enums so I could keep R2017-R2024 the same source code.

I get what Autodesk is doing, but the many steps in between from Enums to ForgeId’s is terrible.

They should have better changed it all in one go and kept the 2 versions for 2 or 3 years in the API with clear documentation of the transition.

Now each version between 2021-2024 had major breaks with a huge impact, specially for parameters.

Some explanation of the difference

Element and Parameter and not derived from each other so no real relation expected between them for GetTypeId result.

Also in context a Type of a Element can be various types or even none.

The type of a Parameter is predefined internally, the previously Enums, easy to recognise but now become a ForgeId which is a type on it’s own, like “autodesk.revit.parameter:hostAreaComputed-1.0.0”, and can no longer be easy compared like before with the enums.

For official documentation, nope those links you gave the sample files of the API SDK and this forum.

And there are several other sites with info, like thebuildingcoder.typepad.com/

– Michel