Notifications
Announcements
No record found.
Hi,
I have two custom model for example, Model "A" and Model "B".
I added reference of model "A" in Model "B" (B <- A), and I extended "ProjJournalTrans" Table from model "B" and added few fields. Now I need to access the fields which is created in Model "B" from Model "A".
Can someone guide me how I can achieve this?
Thanks and Regards,
Rubalingam.S
If model B has a reference to model A, it means that model B can use objects defined in model A, but A knows nothing about B and it can't access objects defined there.
As martin suggested you cannot access Model B objects from Model A.
But there is a new functionality which is added in the latest version. "Friend Packages functionality" - Its showing in the "update model parameters screen". But I cannot find the proper documentation for friend package functionality.
From my understanding I guess it will be used to access the internal method from Model B inside Model A.
Check whether you can be able to access the fields if you select Model B as friend packages in Model A.
Thanks,
Girish S.
It had not come to my attention that we could not use mutual references between the two models(or I don't remember right now).
I think we are solving this issue as a process, there is no need for such a request.
Probably in this case I would also have a C model and I would reference both models and do the development in the C model.
Hi Rubalingam,
First check if you really need two separate models. Or like mentioned above, you can create a model C. If you only need models A and B, there is an option. You can use DictTable, DictField classes and the Common object to interact with the objects from another model; even if there is no model reference. Keep in mind that still model A does not know anything about model B. Also, it could be the case that model B is not installed on a specific environment. Ensure you will first evaluate if model B is installed before trying to create e.g. a common object from the ProjJournalTrans table and get details from the new fields.
I think mutual dependencies is not supported as it might cause circular dependencies issue. For this one I think if possible you need to do it in same A model or at least moving the table extension to A model due to model hierachy.
Regards,
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 584 Most Valuable Professional
André Arnaud de Cal... 499 Super User 2025 Season 2
Sohaib Cheema 254 User Group Leader