Dynamic dispatch VIs cannot be in community scope
- Updated2025-07-30
- 1 minute(s) read
You use a dynamic dispatch VI so that child classes can override that VI and provide different behavior with a VI of the same name. If the dynamic dispatch VI is in Community scope, it is hidden from any child class that is not a friend, creating a situation in which a child may get errors trying to match the connector pane of a VI they do not know their parent has defined. To correct this error, either make the VI static by changing the dynamic input terminal to Required or change the VI access scope to Protected or Public.