Internal errors in case of updating some AssemblyInstance elements' shared parameters

[xdantex00008]

I have different Assembly Instances, which contain elements.

Usually, when I try to update shared parameters, for its elements everything works fine, but on the other hand, as I found out,in  some Revit models, parameters updating can throw exceptions in the transaction commit process (The same element types in the same model are updating successfully)

In Revit Journal I see a message about ApplicationException in the function AssemblyInstance::removeMemberIdsInternal with the message "Recent Dynamic Added but not to Dynamics, this means that this element is not dynamic anymore with RDYs removed"

Is there any possible limitation in Revit which doesn't let me update these parameters or is there any possible way to debug/solve this issue? Because Revit doesn't give any information about this exception.

[TripleM-Dev.net]

Hi @xdantex00008 ,

I haven't used "AssemblyInstance" elements in Revit / API, but a good test would be, if the editing done in the API is possible in the UI manually.

If it is then it could be possible in the API.

If it's something that can't be done manually in the UI then it most likely will not be possible in the API

[jeremy_tammik]

Oh dear, sorry to hear that. Thanks to @TripleM-Dev.net  for their good suggestion. In additional, I also asked the development team for advice for you.

[jeremy_tammik · Accepted solution]

The development team reply:  yes, we have received similar issues before. Most likely, there is an inconsistency in the model such that elements think they are in an assembly, but the assembly does not think it has those elements as members, or vice versa. We don’t know how such inconsistencies happen in practice and have not been able to reproduce recreating them, but we have written an internal tool to make the data consistent again. If you like, you can send us the model for analysis and potentially a data fix.

[xdantex00008]

I see, thank you for your concern and useful suggestions.

I will probably stick to the AssemblyInstance recreation in cases like that