Creating a new model pros and cons

(0) Share

Report

Posted on by DELDYN

462

Hi,

If let's say, I have model B which references model A

Model A is for another company.

Which means i can see what model A have and call it but model A can't do so.

If let's say i'm now in a situation where i want to add something that i want model A to see it (but A can't reference B due to circular reference)

Which is better?

To create a new model, let's say model c. That both A and B can reference? And add the logic to model C. OR ask the other company to do the development on model A instead? ( The change is related to model B, but i thought i can do it with extensions without asking the other company to do it)

Are there any disdvantages of having many models?

I have the same question (0)

All responses (3)

Answers (0)

André Arnaud de Cal... 300,731 Super User 2025 Season 2 on at

Like (0)

Report

Hi Deldyn,

The disadvantage of more and more models would be adding complexity when it comes to implementing new requirements and fixing bugs. Can you explain what you mean with "Model A is for another company"? Is it one feature for one of the companies in your environment? Is it a customization done by a partner, is it an ISV solution?

Was this reply helpful? Yes No
DELDYN 462 on at

Like (0)

Report

Why would it be complex? Can u please explain more?

Originally there's an ISV model for company A

And company A also have model A (cus layer) which references the ISV model (most of the developments for them are done here and they go to the ISV when needed)

Now I have model B, which references A and the ISV model.

As i said i want to add some new fields that i want model A to be able to see and use if a case in the future might pop up that they need it. But i can't do that due to circular reference.

So I have two options:

- create new model C -- which references the ISV.

Model A and Model B will be referencing Model C

This option will save cost mainly

- let company A do the development in model A

So i wanted to know the disadvantages of going with option 1?

Note: The new fields and logic are related to the ISV model and some related to model A but can be implemented with extensions in model C that i want to create

Was this reply helpful? Yes No
André Arnaud de Cal... 300,731 Super User 2025 Season 2 on at

Like (0)

Report

Hi Deldyn,

I have seen some scenarios where per customization topic a new model was created, ending up with a lot of different models. In case you then need to reference two or more models, again, you would need to create a new model and use CoC methods. Sometimes, people mix up models and branching and create spaghetti...

In your scenario your option to create model C would be a viable option as model A is managed by a third party. In case you need high performance, you might do some tests to check the differences between different approaches (less models). When model A is a customization for your company, why can't you use this to create new customizations yourself?

Was this reply helpful? Yes No

Join the conversation

Community site session details

Creating a new model pros and cons

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

Creating a new model pros and cons

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates