2

This question already has an answer here:

I want to build a package to find out metadata dependencies and determine which classes, triggers, pages, components, lightning components and applications, flexi pages, layouts, objects, custom settings, custom metadata objects and records depend on each other.

So far I have found a brilliant way to determine external dependencies for classes, triggers, pages and components described in this question using MetadataContainer and creating related ApexClassMember, ApexTriggerMember, ApexPageMember, ApexComponentMember records.

However, it is not clear how can I find that, for example, Lightning component is depending on ApexClass and which one or depending on another Lightning component, which custom objects depend on another custom objects or even custom managed objects. How can I find that FlexiPage depends on Lightning component or Layout depends on a Visualforce page?

There are no "AuraDefinitionBundleMember" which I can use for MetadataContainer and there are not "CustomObjectMember" or something like that.

Is this possible to implement or should I parse Lightning components, custom object definitions on my own? Can metadata container contain AuraDefinitionBundle or custom object or layout or flexi page?

My question is more generic than Symbol table for Lightning components to find Dependencies/References since in my case I am looking for Symbol Table not only for Lightning components, but also for Layout, FlexiPage, Object and other metadata to find dependencies\references.

marked as duplicate by Jayant Das, glls, Pranay Jaiswal, battery.cord, Gortonington Dec 5 '18 at 14:12

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • My question is more generic than Symbol table for Lightning components to find Dependencies/References since in my case I am looking for Symbol Table not only for Lightning components, but also for Layout, FlexiPage, Object and other metadata to find dependencies\references. – Patlatus Dec 5 '18 at 10:20
  • You can get the list of available objects with Tooling API as mentioned in the documentation. So if you have the components listed there, you can fetch those entities, but anything not documented there is considered not to be available. – Jayant Das Dec 5 '18 at 13:34