web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Selecting existing Pac...
Microsoft Dynamics AX (Archived)

Selecting existing Package option in D365FO

(0) ShareShare
ReportReport
Posted on by @rp@n 56

Dear All,

Can you please let me know I have created a Package "Training" and add element "PurchTable.extension".

T7.jpg

If i wants to add more elements on the same Package "Training" then ONLY i need to select "Selecting existing Package" while creating a new Model/Package :

 

T6.jpg

Is't correct?

Please give me more shed on this.

Thanks!

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Sohaib Cheema Profile Picture
    Sohaib Cheema 49,664 Super User 2026 Season 1 on at

    You don't want to create multiple packages to add things into your existing package named training.

    A package is a like Model store. Why you want to create a new one, if you can add elements in existing packages with just creation of a new project. Each project has a package/model associated with it, which can be seen/changed by having a look at properties of the project. Say you added PurchTable.Extension in your package training in first development. Now in 2nd development you may want to create an extension for SalesTable. At this point if you want your SalesTable extsion to reside in same package named training, you do not need to create a new package. You can simply create a new project and after project is created, make sure that package/model selected in its properties, is the correct one; the Training in your case. Also you can add multiple elements in same project which can belong to same package. you don't have to necessarily create a new package every time, when you need to extend any element.

    Coming back on the picture that you have attached in your question; it is not looking great. I would not like to see this being done by someone in my development team. Basically you are choosing an option to do customization, whereas Customization is not recommended. You should avoid this 2nd option. Always try to do extensions; if you cannot, contact to Microsoft. This means always go for 1st option.

    PS:

    Personally I would not like to have 100 of packages for a client, in general. If I am the only ISV or VAR working for a client, I would try my best to keep all my extensions under one package and I will avoid creating any additional packages throughout project. I would do so for simplicity. If I will have a single package, it would be easy for me to import export it and manage it ultimately. If I need to add solution for another partner on same client, I would expect that to be coming into a different package. I would create multiple packages if i am working for a VAR or ISV. Lets say I am working with an ISV and we have multiple solutions, then it makes sense to create a separate package for every solution. Even then I would not choose that 2nd option which represents customization.

     

    Now let’s forget all talk and please answer me one question.

    Why you want to create a new package..? Let's forget if you are choosing 1st option or 2nd option (as shown in your image). Question is why you want to create a New Package..?

  • @rp@n Profile Picture
    @rp@n 56 on at

    Thanks Cheema

    Actually I have confusion when to use " Select existing package " option. So, I thought i can use in this way...

    So,now I understand the 1st option is always recommend not 2nd option.

    Thanks!

  • Verified answer
    Sohaib Cheema Profile Picture
    Sohaib Cheema 49,664 Super User 2026 Season 1 on at

    I suspect you are using an old version of MSDyn365FO.

    Or else, you would not get a chance to do this mistake, which you are trying to do. I would not force you to use a new version, because there can be reasons as if someone might had decided to go-live with a client for a specific version of MSDyn365FO. The old versions of MSDyn365FO, allow you to do, what you are doing. Given that, if you are doing all of this for learning purpose only, get a new version ASAP and never use 2nd option in normal situations. Also stop habit of creating a new package every-time for every small modification. 

    nvmsv01.png

  • @rp@n Profile Picture
    @rp@n 56 on at

    Thanks Sukrut

    So, I have to forget the 2nd option permanently. Is't correct?

    Because asper your comments and Cheema comments there is NO use of the 2nd option as I understand.

    Please give me more shed on this.

    Thanks!

  • @rp@n Profile Picture
    @rp@n 56 on at

    example for option 2nd:

    Package 1

         Model 1

         Model 2

         Model 3

         N....

    Is't correct?

    Thanks!

  • @rp@n Profile Picture
    @rp@n 56 on at

    But Sukrut, can you please explain me how I will achieve the above example.

    If I run the wizard 2 times then what I need to fill in Add parameters and what to select under selecting existing package? So, that I can achieve the above example.

    Please give me more shed on this.

    Thanks!

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.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 24

#2
Michel ROY Profile Picture

Michel ROY 14

#3
Jagadabi Profile Picture

Jagadabi 6

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans