Working with dynamic types is easy so long as you follow the steps correctly.
- Implement your namespaces
- Implement your finder methods
- Add your type to XaaS
- Add an XaaS blueprint
- It must output a provisioned resource of your DT
- It must have lifecycle workflows configured for Update/Destroy
The most common mistakes people make with managed DT items is not including lifecycle workflows for all states or setting up their finder methods incorrectly; particularly findById and attempting to use DynamicTypesManager.makeObject() instead of DynamicTypesManager.getObject().
See this thread for more info: Proper way to map XaaS Type on vRA 7.X Catalog
Or this blog post https://www.vcoteam.info/articles/learn-vco/323-how-to-create-a-microsoft-dns-dynamic-types-plug-in.html by the vCO team for a massive in-depth dive on DT that covers everything.
I've been using DT to create few internal plugins -everything work and all but I have a question: Why do we have the finder findAll() since vRo inventories always call the other finders? I didn't saw a case that its being called at all. Is there any specific usage for this finder?