Finance | Project Operations, Human Resources, ...

Application models planning for two developer teams

(1) Share

Report

Posted on by Eddie No

Hi guys,

I have dilemma, how to manage x++ devlopment of two developer teams in D365.

We have one partner devlopers team which is now using one model to develop modification.

There is also customer developers team which is joining development process.

I want to find best way how those teams could work together because definitely both teams will want to access/modify each others objects.

Right now I have two ideas how we can manage this.

1. Use the same model but different object naming (prefixes, endings etc.) as both teams are using different naming conventions. Looks like the easiest variant, but I am not sure if the best from BP perspective.

2. Create separate model for customer developers team, but create it as a part of existing partner developers model (A model that is a part of an existing package option when creating new model). From my tests it looks like in this case models can access each others objects. This solution looks better for me because we can distinguish who made what easier and naming convention used by two teams will not be messed together in one model. Only thing what bothers me here is that documentation says that this option is considered legacy and should be used only temporarily, but on the other hand I can see the same approach in standard ApplicationSuite model. Models and packages - Finance & Operations | Dynamics 365 | Microsoft Learn

What are your thoughts on this guys? Maybe you see other options here?

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Anthony Blake 2,926 Super User 2025 Season 2 on at

Like (0)

Report

Create 2 models for sure, keep your naming based on your model names. I wouldn't have them in the same package personally, add a complication you don't need.

What you can't have is circular references, Model 1 referencing Model 2 AND Model 2 referencing Model 1, so if you ever need a shared dependency, code or elements both models need to use, you would need a 3rd model which would be shared elements.

Was this reply helpful? Yes No
Martin Dráb 237,795 Most Valuable Professional on at

Like (0)

Report

You seem to have conflicting requirements. You say that each team has its own naming conventions, but also that each team will modify code of the other team. The former suggests separation, but the latter says there will be no separation and all objects can contain code from both teams, following different naming conventions, which will be a mess.

You should decide whether you want the separation or not. If you do, you must either strictly separate work of those teams, or you must say that each part of the application (not each team) will follow different conventions.

In my opinion, mixing different conventions in the same application isn't a good idea and I'd try to eliminate that.

In general, packages (models) are about a structure of the application, not about development teams.

Was this reply helpful? Yes No
Eddie No 9 on at

Like (1)

Report

Thanks guys for your answers, appreciate that.

Let imagine that we have this kind of scenario:

1. Team A have developed some integration/report let's say Sales orders some time ago.

2. Meanwhile Team B develops some other stuff related to Sales order.

3. After some time new requirement comes for Team A "Hey can you add to your integration field which Team B has created"

What would You suggest in that situation? if Team A and Team B uses different naming?
Creating separate models and then 3rd one to connect two modifications? Doesn't it makes things more complicated?

Was this reply helpful? Yes No

Join the conversation

Community site session details

Application models planning for two developer teams

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

Application models planning for two developer teams

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