Dynamics AX
  RSS Feed  LinkedIn  Twitter
Want to turn you're data into a true asset? Ready to break free from the report factory?
Ready to gain true insights that are action focused for truly data informed decisions?
Want to do all of this across mutliple companies, instances of Dynamics and your other investments?
Hillstar Business Intelligence is the answer then! (www.HillstarBI.com)

Hillstar Business Intelligence for Microsoft Dynamics AX and NAV on Mobile, Desktop, Tablet

Let us prove to you how we can take the complexity out of the schema and truly enable users to answer the needed questions to run your business! Visit Hillstar Business Solutions at: www.HillstarBI.com

Thursday, November 23, 2006

Happy Thanksgiving!

Well to everyone that celebrates Thanksgiving, have a blessed and wonderful thanksgiving.

I know that YHWH God has blessed me and my house with more than we ever deserve. Most of all I am most thankful for the salvation that comes from the blood of the lamb! Jesus / Yeshua Christ, our Lord!

The verse I stand on: Romans 8:38-39
"For I am convinced... ....Nothing that seperate us from the love of God, through our Lord Jesus Christ [Yeshua]"

Peace be with all! <*>

Find a job at: www.DynamicsAXJobs.com

Wednesday, November 15, 2006

Chrome Hearts chooses Sunrise to Implement Microsoft Dynamics AX

Below is the latest new customer press release from the wonderful Microsoft VAR I work for: Sunrise Technologies!


(Winston-Salem, NC) Sunrise Technologies, Inc. announces today that Chrome Hearts LLC has chosen Microsoft Dynamics AX as their ERP solution. Sunrise Technologies will deploy the Microsoft Dynamics AX ERP solution for the Hollywood, CA based company.

Chrome Hearts was founded in 1989 by Richard Stark and has retail locations in Los Angeles, Las Vegas, Malibu, New York, Hong Kong, Japan and Paris. Chrome Hearts is known for their beautifully crafted jewelry, leather apparel goods, accessories and furniture. Chrome Hearts is one of the chosen brands of many of the entertainment industry's leading trend setters such as the Rolling Stones and Cher.

"The Sunrise Technologies team did an excellent job of demonstrating their knowledge of Dynamics AX V4.0 and their vast experience in the Apparel industry to the Chrome Hearts project team as well as their value proposition to the Executive Management team. This in addition to presenting Chrome Hearts with a significant number of Dynamics customer references and a well qualified team of implementation consultants resulted in a clear choice for Chrome Hearts," stated Bill Gerrish, Microsoft SMS&P Strategic Engagement Manager.

"We are extremely happy to add Chrome Hearts to our rapidly growing list of Dynamics AX customers. Dynamics AX's combination of flexibility, cost effectiveness, and proven track record in apparel and consumer goods makes it the perfect fit for Chrome Hearts," states John Pence, President and Founder of Sunrise Technologies. Pence adds that "we are looking forward to a very successful partnership with Chrome Hearts, and we expect to continue to invest and grow in the California market."

Find a job at: www.DynamicsAXJobs.com

Tuesday, November 14, 2006

Dynamics AX and Enterprise 2.0 (AKA: Web 2.0)

"both composite apps and mashups are intended to reduce the overall effort of development, improve functionality, promote data consistency, and increase the net output of useful software."

As I move forward in my discussion's on Web or Enterprise 2.0 and the future of Dynamics AX, I wanted to dive further into the concept of Mashups or Composite Applications. As you read the tag line I posted above from the blog entry you see, it talks about the goal behind IT depts. bringing in these composite / mashup / SOA type architecture in, and what is gained in doing so.

So what is gained with this new technology? The end results is a customer self service based approach to technology and software. It's to give more power and control to the information worker, that in turn takes certain task off the shoulders of the IT dept. allowing the IT dept to focus more on improvements, and therefore
completing the circle of life! LOL :-)

Now the last part I added on, because well, we all need to laugh! Speaking in real terms, what I should said means that the given user or information worker will be given more flexibility to get and work with the information they need, and not have to depend on the IT dept. to do so. Reporting data, and gettin data, will not need a full time report writing staff. Doing so will be much easier, and controlled, while at the same time decentralized. I know that sounds like an oxymoron, but this oxymoron is becoming the future of what IT, software, and the end user relationship will be like. It will become decentralized, while at the same time more controlled, and flexible. Things will be more intertwined, while runnable decoupled, disconnected, and sometimes not even knowing of each other.

So now we have the concept right? If not, that's ok, because no one has the full concept... the reason why that is, is because the full concept is still just a concept. So where is the meat 'n potatoes for this? How can this benefit me now? How do I prepare and start to move towards this? Well in the next year you will see technology that will start to allow some of these mashups to become useful and
used within the Dynamics AX scope. The next release of SharePoint and Office system will allow for interaction to where a given user can have a SharePoint Portal (ie: DAX Enterprise Portal) and on that portal page have Excel and Business Score Card web parts. Through the use of the Snap In program, a consultant firm could then develop a Snap In that allow for data to be pulled into the Business Score Card web part and Excel Web Part for Inventory Counting, or Project Time Sharing and Time Reporting, etc. etc.
This is next year folks!! Not two years, not 3, but next year, within months even.

So our Dynamics AX mashup's can be done even now, without this technology. It takes more custom programming, but with the current release you can create SharePoint web parts that interact in such ways and allow for mashups of different, disconnected applications to feed a infomration workers process, so they can do their job in a quicker way, that depends less and less on the IT dept., which means that IT dept, DOES NOT GET REPLACED but rather is freed up to preform more IT related task, to continue the improvements and not have the burdens associated with the past lifes.

As this technology progresses and matures, then the processes will come out of the box, and less custom code will be needed to achieve these mashups or composite applications. Well I have rambled on enough about this for now. My next step is to take what we have been talking about and actually apply it! Check back soon as I start to discuss what we will tackle with this, and what is will allow for our end users, and how we will achieve it with current, and future technologies!

Find a job at: www.DynamicsAXJobs.com

Friday, November 03, 2006

CCADO Classes in Dynamics AX 4.0

I wanted to take a quick break from my series on the future of Dynamics AX and Web 2.0, and talk a little bit about the CCADO classes. These classes represent a new way to access external data through code within DAX, which allows for the use of ADO vs. ODBC classes.

For me this is a wonderful step in the right direction, in which to be honest I missed. I missed the ability of creating object that represent table's through the use of ADO Recordsets. Now this is wonderful! The classes that are avaliable for this are:


The above classes can be made use to create an ADO connection to a given database, and then create multiple ADO RecordSets to work with.

Now let look at using these classes. When creating new code to make use of ADO Connection and recordset's, you always have to start with a connection. So the first class that you want to make use of would be the CCADOConnection object. With this object you can create your recordset through the use of a connection string. Once you have your connection, then you can build a recordset by creating a new CCADORecordSet object and call the .open() method with passing it the CCADOConnection open along with the T-SQL statement to retrieve the dataset with. The other two classes metioned above can be made use of for working with the Fields and a single Field within the RecordSet. Now there are other objects like the Command object which can be made use to execute updates and deletes, etc.

I want to mention here that all code should be design and developed in an OO way. Meaning that instead of working with raw Connections and RecordSets, you want to create objects that represent the data you are wanting to work with that handles the underlying updating, viewing, etc. With this you can then move forward in the right direction. To speak by example, if you have a table that contained: SID, UserName, Password, FirstName, LastName and you wanted to work with that table through ADO, then you would start out with creating an X++ class that represent the data as an object. So you would create a class that extended from the CCADORecordSet class that would have SID, UserName, Password, FirstName, and LastName as Parms of that class. The new would create the needed connection, and then you could choose to fill the who table and work with it as such, or supply a certian where clause to the end of the given T-SQL statement used to created and fill the object.

Well Check back soon as I continue on my path talking about the future for Dynamics AX and Web 2.0. The above though I wanted to get out here as it is Very useful, and very handy, and I am glad to see it replacing the use of the Older ODBCConnection classes.

Find a job at: www.DynamicsAXJobs.com

Copyright 2005-2011, J. Brandon George - All rights Reserved