INSTANCE_ELEVATION_PARAM change is not firing Updater

[PhillipM]

I'm wanting to monitor any change of value to the built in parameter "INSTANCE_ELEVATION_PARAM".

For some reason the below code is not firing my updater when using the "GetChangeTypeParameter(ParmID)" overload.  It does fire when I use the "GetChangeTypeAny" overload but this is not desiarable as that fire with any change to any familiy instance.

My code is below.  Any suggestions what i'm doing wrong here?

regards

Phillip

 Dim updater As New ERParmUpdater
 updaterId = updater.GetUpdaterId()
  If UpdaterRegistry.IsUpdaterRegistered(updaterId) = False Then
                UpdaterRegistry.RegisterUpdater(updater, True)
                UpdaterRegistry.SetIsUpdaterOptional(updaterId, True)
                Dim filter As ElementFilter = New ElementIsElementTypeFilter(True)
                Dim ParmID As ElementId = New ElementId(BuiltInParameter.INSTANCE_ELEVATION_PARAM)
                UpdaterRegistry.AddTrigger(updaterId, filter, Element.GetChangeTypeParameter(ParmID)) ' I want the updater to fire only when "INSTANCE_ELEVATION_PARAM" Chnages
                ' UpdaterRegistry.AddTrigger(updaterId, filter, Element.GetChangeTypeAny)  //This does fire the updater but on any change to a family Instance
 End If

[Anonymous]

Sorry, no help here.

I've used this successfully on several built-in parameters, but I also cannot get it to work on INSTANCE_ELEVATION_PARAM. I also failed with INSTANCE_FREE_HOST_OFFSET_PARAM.

I don't even want to imagine the hoops you would have to jump through to get "GetChangeTypeAny" to work for just an elevation change.

[PhillipM]

Thanks Peter for confirming what I had hoped was just an oversight by me.  As you have mentioned I have also been sucessfull monitering BIP's before but not this one.  I wonder what is so different about this?  Autodesk.....  Any comments on this?

Regards

Phillip

[arnostlobel · Accepted solution]

I can comment, but, unfortunately, all I have to offer is my sincere apology. We are aware of cases with parameters as the ones reported in this thread. Technically, there is nothing special about them (to answer the question above). It is simply a technical oversight that those parameters (and others too) do not report themselves correctly when they get modified. (it’s a human error, really; on the side of us, Revit programmers.) Our in-house programmers who “own” some parameters are supposed to implement proper reporting mechanism not just for the change a parameter drives, but also for the parameter itself. Unfortunately the second part can be easily overlooked and forgotten. For a long time we have wanted to create some sort of a self-testing mechanism which would reveal unreported parameters, but to no avail so far. Alas, our API customers reporting such cases to us is pretty much what we are left with (aside with some random testing we do sometimes.)

I am going to report these two new cases and hopefully they will be dealt with soon.

Thank you

[PhillipM]

I really appreciate your feedback on this issue.  Bummer it is a Revit API Issue and not mine :(.  Never mind.  I will work around this limitation.  It just means that the solution I'm working on will not be as efficient as I had hoped.

Regards

Phillip Miller

Kiwi Codes Solutions ltd

[PhillipM]

Yet again this issue has came back to bite me in the **** big time.

This time looking for any change to the BIP  "BuiltInParameter.KEYNOTE_PARAM"

Once again I have had to open it up to monitor any change which is hugely inefficient.

Please can this be FIXED ASAP.

Regards

Phillip