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

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Build # suggestion

(0) ShareShare
ReportReport
Posted on by 4,131

Hi,

What would be your suggestion to define a custom model deployable package build #?

Thanks,

I have the same question (0)
  • Verified answer
    Joris dG Profile Picture
    17,775 on at
    RE: Build # suggestion

    What you can do is use Nikolaos' suggestion, and make the fourth number the build "ID". Not the AZDO build number (although you could just make that one the build ID as well), but the ID which is unique i think across all definitions in your project. There are several variables you can use. See docs.microsoft.com/.../variables

    It's important to have the model version have a link back to the build it came from if you value the whole process of build automation.

  • Verified answer
    nmaenpaa Profile Picture
    101,160 Moderator on at
    RE: Build # suggestion

    Because of the extensions and backwards compatibility, your package would normally be compatible with many MS versions. For example, if you build your package with 10.0.8, it will work also with 10.0.9 and 10.0.10.

    But yes, one option is to include the MS version that you used in the build process. If you ship many versions that are built on 10.0.8, you can call them 10.0.8.1, 10.0.8.2 and so on. Or 108.#.#.#. It's completely up to you.

  • Yuji Profile Picture
    4,131 on at
    RE: Build # suggestion

    So basically my question is for model version number. But we would like to keep the Microsoft base version information in our version #. For example, if we build our model on 10.0.8, it could be 108.#.#.#? Just want to ask if there is any guidance in terms of model version #.

  • nmaenpaa Profile Picture
    101,160 Moderator on at
    RE: Build # suggestion

    Yes, but what kind of information are you asking for? Build number is something that is normally internal to your ADO and not visible to your customer in any way. On the other hand, your customer sees model version numbers. So is your question related to build number or model version number or something else?

  • Yuji Profile Picture
    4,131 on at
    RE: Build # suggestion

    We create a custom model/package for our custom solution.

  • nmaenpaa Profile Picture
    101,160 Moderator on at
    RE: Build # suggestion

    What do you mean by "custom model deployable package build #"?

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

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

#1
CA Neeraj Kumar Profile Picture

CA Neeraj Kumar 2,352

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 830 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 634 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans