Revisit with Version Control for AX 2012

Well I hope everyone is doing well! I admit I have been super busy, and realized that I've not posted in two weeks. I typically try and post at least 2-3 entries a week, but my recent schedule both professional and personal has kept me from this passion.

With that, I wanted to get back cranked up posting, with a revisit of sorts around the topic of Version Control for Microsoft Dynamics AX 2012. I wrote about this sometime back, around the options we have, located here.: AX 2012 & TFS 2010, along with other Version Control Options



In that post I cover the major options, as well as other resources around the topic of version control. This revisit, I believe is deserved for two main reasons. One, it's a topic that I still get asked about from a true options perspective. Two, there is a new release from Joris, fellow Dynamics AX MVP and blogging peer for his AX TFS Build Library v0.2.0.0.



Starting with point one, it is true that TFS is not the only valid option to use for Dynamics AX 2012 version control. As picture above, and what the above picture is meant to represent, shared development enabled with MorphX VCS is still a valid option. Typically we see this with shops that don't have the resources for a Full Time Employee (FTE) who can be dedicated to the administration of TFS.

Make no mistake about it, TFS is an investment which requires an FTE who thinks, and lives TFS for an organization. This person can also do development work, but depending on the size of the development team or teams, might have a zero time for anything else but TFS.

When thinking about the options for version control, a great resource that I previously highlights can be found here.: Version Control System [AX 2012]

That resource has a nice table that lays out the options, and value points of what each option can offer you. Going back to MorphX VCS being a valid option, this does mean there are some limits. The biggest is the fact that this only helps control version's of objects that are apart of the AOT. If you think about this, say their are outside services you create as part of your total solution. What about SSIS packages that make up your solution? These will not be apart of a MorrphX VCS instance.

Further other draw backs are how report development for AX 2012, as well as Enterprise Portal Development takes place.

There are still ways to develop for each, but what the TFS option enables is developer instances of AX for each developer. Where as the MorphX VCS enables a single shared development instance of AX 2012.

Finally on to point two, with Joris updated release of the AX TFS Build Library. You can directly download the latest release from Joris, here.: Codeplex: Dynamics AX Build Scripts. And further, his latest post on the topic.: New release of AX TFS Build Library Beta (v0.2.0.0)

Most notable in this release is Joris' focus on fixing several label related issues, allowing for Visual Studio Projects to be imported, and splitting out system classes at the end of a build cycle to help avoid stability issues.

Well that all for this post. Feels good to get back into the swing of things and writing again. Check back soon, as I will post again this week - next up a look at a specific question that came from my post on Understanding & Extending the Organization Model. Till Next Time!
Follow Me @:
    

"Visit the Dynamics AX Community Page today!"

AX 2012 - BI Artifacts & Source Control

I hope everyone is doing well today, and your working on exciting Dynamics AX projects. There is for sure a lot going on within the Ecosystem as a whole. New partner highlights across the board, and interest in Microsoft Dynamics AX has never been Higher!. With that, as you have seen in my past post, I like to talk about value and how value is best derived from investing in AX 2012. With that, one of the hot topics that I see day in, and day out as a well under-served part of the Dynamics Ecosystem is around true Business Intelligence .

Now being that I'm a true solutions architect, one of the focuses around BI, is the management, and processes that help us create such needed artifacts likes cubes, KPI's, AX-SSRS reports, etc. That's what prompted me to write up, for example the post on processing cubes error for standard edt. SQL Server 2012 Analysis Services. Further, you've seen me post about future topics as well, with the BI Semantic Model (BISM) post.



With this post, I wanted to continue my dive into value added topics, around AX 2012 & BI. That brings us to today's topic, around Source Control for BI Artifacts.



When thinking in terms of BI Artifacts that are created, that need version control, we are speaking about: Classes for DataContracts & RDP Framework, Query Elements, VS Report Model Projects, Perspectives, Views & Analysis Services Projects. Thinking in terms of Version Control or better Application Lifecycle Management (ALM), there are some great resources on the web. One for sure you need to book mark, is Joris information on the topic, located here.: DAX Musings: ALF | TFS Resource page.

With that resource in hand, and going back to what we need source control for, lets look at the obvious. Please do note, at this time, the article assumes that you have TFS being used with your AX 2012 instance. To continue, with the obvious, things like Classes, Query Elements, Views and Perspectives, most people are use to understanding how this works. These are added to source control by someone, and then can be checked in and out. This means, that understanding the base BI artifacts, when TFS is used, then it's controlled as such.



What about the other artifacts? For example Perspectives build cubes, and Perspectives are made of views and tables. These then are the basis for the Analysis Services Project which is what builds the cubes for AX 2012. This project can be updated, or configured through the Analysis Services Wizard of Ax 2012. Understanding that, what about this project? Well This project, just like the VS Report Model Projects, or even C# Projects. All of these are controlled with the same rules for Models, Layers and Version Control from the AOT as any other object or element in the AOT.

This is important to keep in mind, when thinking about using Source Control outside of AX 2012, or along side of it. The choice of where the source control is being implemented really, is the focus and point. Meaning, that for anything managed by AX 2012 It's best to allow the AOT / AX to enable source control on any objects it has. Everything else, that truly lives outside of AX, should be managed through Visual Studio.

Well that's all I have time for today, check back soon as more to come including a book review, some spotlight post, more into the real Semantics of BI and what it means for AX 2012, as well as a lot-lot more! Till Next!
Follow Me @:
    

"Visit the Dynamics AX Community Page today!"

The Power of the Dynamics Community

I wanted to kick off this weeks series of post, with a focus around the Microsoft Dynamics Community and the power and value it brings. We have a really awesome example of how all of us involved in the community, work together to drive value that helps us all.



Recently I took a lead, from Palle Agermark with his post that focused on the new ability in AX 2012 X++, in which certain keywords, while coding, can have code snippets added. In that highlight post, in which I exposed the xppSource class and it's use, I built upon what Palle had started in his post.



This, then having a specific topic, had two bloggers and active Dynamics Community members in helping give a combined value that the two articles, by themselves, could not achieve. Well taking this a step further, fellow peer and blogger Joris de Gruyter continued to add to the value of this topic by diving deeper into a great example of using code snippets: Code Snippets in AX 2012



Joris gives us a great example, in his further dive into this topic, with adding real value in creating your own code templates that can speed up your development needs an process. He further, correctly explains, that the concept is not new to AX, but the use of xppSource for enabling this is.

I just thought this was a perfect time to point out, that working together in the Dynamics Ecosystem like this, building upon each others knowledge is what sets us apart from other communities. Being able to work towards a common goal and helping the general Dynamics users, be that Partner or Customer, is just really awesome. Many thanks for Palle and Joris in helping show of we all add, and can work together to build out this Dynamics community that belongs to each of us.

That's all for this post, but check back soon as I have a lot of post ready to be released, covering Conv12, BI, AX 2012 Upgrades and of course looking towards that bright Dynamics future! Till next time!

Follow Me @:
    

"Visit the Dynamics AX Community Page today!"

Spotlight: AX 2012 Developer Resources

With the release of Microsoft Dynamics AX 2012, there is so much to keep up with and learn. So many great features, technology changes, application changes, etc.

Because of this fact, it's ever so important that the community at large, continues to grow and create resources that are helpful and useful. I did a blog spotlight, back in July, for Joris de Gruyter blog Dynamics AX Musings.

Well Joris is still being very active in creating great content, and he has put together an AX 2012 Developer Resource page that is nicely put together, and has some great links to some great resources.

I wanted to thank Joris for putting this together for the community, and I recommend you check it out.

This is the kind of community building that we should encourage, and continue to always strive to build out. These links will help anyone looking to continue to dive deeper into the new area's that come along with AX 2012.

Some of these topics I cover myself, and others I will cover deeper, as well as bringing them together into concepts and higher levels from an Architects point of view.

That's all for now, but check back soon as more to come, including interviews, how-to's, ISV spotlights, and much, much more! Till next time!



"Visit the Dynamics AX Community Page today!"

Spotlight: Dynamics AX Musings

I thought I would start off this week, with a blog spotlight. It's so important for the growth of the Microsoft Dynamics AX Community at large, for those that have been working with the product, and can give in depth knowledge tidbits, to write and share their knowledge.

With that, I would like to highlight: Dynamics Ax Musings

This is the blog by Joris de Gruyter who is a true veteran of the Dynamics AX world.

Joris starting really sharing his knowledge last year, and has spear headed such wonderful projects, like the open-source, codplex project, Dynamics AX Build Scripts (And's it's TFS impacts), as well as sharing with us a great series of post on Microsoft Dynamics AX 2012.

His in-depth cover of very specific, developer and technical engineer related topics, are exactly what is needed, and I hope you would bookmark his blog, and check for regular updates, as well as encourage Joris to continue in his efforts to help spread the good word of the brave new world Microsoft Dynamics AX 2012 represents for all of us!

A great series that Joris just finished up was on AX 2012 Models & Events

• Part 1: Model Architecture
• Part 2: Events
• Part 3: The Power Combo

Joris really helps bring home some of the great new features, that makes Microsoft Dynamics AX 2012, a truly powerfully simple, Generational Shift in ERP!

That's all for now, but check back soon as so much more to come! Till Next time!



"Visit the Dynamics AX Community Page today!"