Please read here for more.. http://blogs.msdn.com/b/microsoft_dynamics_danmark_-_partner/archive/2013/03/26/microsoft-invitation-to-free-online-event-dynamics-ax2012-moving-average-costing-in-ax2012.aspx
Dilip's blog on DYNAMICS AX
Greetings! Welcome to my Dynamics AX and related MS Technologies blog.
Tuesday, April 2, 2013
Tip - How to retrieve Security Policy Metadata info stored in ModelSecPolRuntimeEx (Dynamics AX 2012)
Dear Friends,
Thought to share with you about this table in Dynamics AX 2012 which stores the runtime metadata for all the queries involved in Security Policies. I figured out it's a good starting point for debugging your Security Policies.
The resultset retrieved from the below query will tell you about the PrimaryTable, ConstrainedTable, Query Name, and more importantly, the column ModeledQueryDebugInfo which contains the raw sql statement that is used behind the scenes. (Just copy-paste the below SQL and run in your Management Studio to see the results)
SELECT [PRIMARYTABLEAOTNAME], [QUERYOBJECTAOTNAME],
[CONSTRAINEDTABLE], [MODELEDQUERYDEBUGINFO],
[CONTEXTTYPE],[CONTEXTSTRING],
[ISENABLED], [ISMODELED]
FROM [dbo].[ModelSecPolRuntimeEx]
As per msdn, The ModelSecPolRuntimeEx table stores the runtime metadata that is necessary to apply security policies.
Thought to share with you about this table in Dynamics AX 2012 which stores the runtime metadata for all the queries involved in Security Policies. I figured out it's a good starting point for debugging your Security Policies.
The resultset retrieved from the below query will tell you about the PrimaryTable, ConstrainedTable, Query Name, and more importantly, the column ModeledQueryDebugInfo which contains the raw sql statement that is used behind the scenes. (Just copy-paste the below SQL and run in your Management Studio to see the results)
SELECT [PRIMARYTABLEAOTNAME], [QUERYOBJECTAOTNAME],
[CONSTRAINEDTABLE], [MODELEDQUERYDEBUGINFO],
[CONTEXTTYPE],[CONTEXTSTRING],
[ISENABLED], [ISMODELED]
FROM [dbo].[ModelSecPolRuntimeEx]
As per msdn, The ModelSecPolRuntimeEx table stores the runtime metadata that is necessary to apply security policies.
Labels:
Dynamics AX 2012,
Security,
Tips and Tricks,
Troubleshooting
| Reactions: |
Sunday, March 31, 2013
The sun is shining brighter for Dynamics AX Techies!! :)
Dear All,
Wish you a Happy Easter!
As I was tweeting this morning, I happened to stumble upon this news and thought to share it over here!
For Dynamics AX professionals and for the aspiring ones, it's going to be a brighter future. Suddenly, there's a good demand all over the globe for techies experienced in Dynamics ERP (Dynamics AX being the most sought after ERP).
Have a look at this news http://www.networkworld.com/news/2013/032613-microsoft-dynamics-268111.html
Some of the takeaways from the above news are:
a. Full-time technical architects working on Dynamics stand to earn a 14% salary increase
b. Technical architects also pull down some of the largest salaries among Dynamics professionals, with salaries of $148,000 for those versed in Dynamics AX, $115,000 for NAV, $144,000 for CRM and $115,000 for GP, the survey says.
Freelancers can earn up to $1,100 per day.
c. The average freelance wage increase over the next year is 12%, and that is so attractive that 39% of full-timers would leave their current jobs to freelance.
d. A larger percentage (48.1%) describe themselves as satisfied with their jobs and 8.5% describe themselves as very satisfied.
Wish you a Happy Easter!
As I was tweeting this morning, I happened to stumble upon this news and thought to share it over here!
For Dynamics AX professionals and for the aspiring ones, it's going to be a brighter future. Suddenly, there's a good demand all over the globe for techies experienced in Dynamics ERP (Dynamics AX being the most sought after ERP).
Have a look at this news http://www.networkworld.com/news/2013/032613-microsoft-dynamics-268111.html
Some of the takeaways from the above news are:
a. Full-time technical architects working on Dynamics stand to earn a 14% salary increase
b. Technical architects also pull down some of the largest salaries among Dynamics professionals, with salaries of $148,000 for those versed in Dynamics AX, $115,000 for NAV, $144,000 for CRM and $115,000 for GP, the survey says.
Freelancers can earn up to $1,100 per day.
c. The average freelance wage increase over the next year is 12%, and that is so attractive that 39% of full-timers would leave their current jobs to freelance.
d. A larger percentage (48.1%) describe themselves as satisfied with their jobs and 8.5% describe themselves as very satisfied.
e. Nearly half (45%) of those looking to change jobs would consider moving to another country, with the U.S., U.K., Australia, Canada and Germany scoring as the top choices.
f. Most jobs related to Dynamics offer laptops, bonuses, a mobile phone and health plans as standard perks. A significant chunk (20% to 50%) also offer life insurance, dental insurance, life insurance and free Internet access, and they give workers the option to work from home.
So, all looks exciting at the moment for people working on Dynamics AX :), Happy Daxing!!
Labels:
AX General,
Dynamics AX,
Dynamics AX 2012
| Reactions: |
Wednesday, March 27, 2013
SSRS Troubleshooting ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
Dear All,
I realized this post was sitting in my drafts folder for a while now. This is not going to be an AX post but an interesting experience on troubleshooting SSRS Configuration connecting to an external database.
For one of my customer, I have developed a series of SSRS Reports to extract data from a third party provider - Intersystems, http://www.intersystems.com/trakcare/index.html who specializes in HealthCare Information Systems.
To give a bit background, Intersystems uses Oracle database for their healthcare systems and inorder to extract data from their systems, I had to create a Linked Server connection in SQL Server which talks to Intersystems ODBC Driver (DSN). The IT team at my customer end had installed the 3rd party ODBC Driver on the box where SSRS was installed.
I was able to connect to their database using BIDS and the report rendered without any issues. However, when I publish the SSRS report to Report Server and then try to browse the report via report URL, it throws out this error "ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application”
Solution:
Since we are using SSRS reporting we would need both 32-bit and 64-bit ODBC drivers of Intersystems as In SSRS, the Report Manager and Report server are 64-bit components and BIDS Environment (Development Studio of SSRS) is 32-bit.
After few hours of research on this error and by going through the forums and InterSystems website, it seems like they have a 64-bit ODBC Driver available. The 32-bit driver which we are currently using is the version released in 2008.
I downloaded the 64-bit Cache 2008.2.6 from their FTP site and installed it on our SSRS box ftp://ftp.intersystems.com/pub/cache/odbc/ and this fixed the error
I realized this post was sitting in my drafts folder for a while now. This is not going to be an AX post but an interesting experience on troubleshooting SSRS Configuration connecting to an external database.
For one of my customer, I have developed a series of SSRS Reports to extract data from a third party provider - Intersystems, http://www.intersystems.com/trakcare/index.html who specializes in HealthCare Information Systems.
To give a bit background, Intersystems uses Oracle database for their healthcare systems and inorder to extract data from their systems, I had to create a Linked Server connection in SQL Server which talks to Intersystems ODBC Driver (DSN). The IT team at my customer end had installed the 3rd party ODBC Driver on the box where SSRS was installed.
I was able to connect to their database using BIDS and the report rendered without any issues. However, when I publish the SSRS report to Report Server and then try to browse the report via report URL, it throws out this error "ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application”
Solution:
Since we are using SSRS reporting we would need both 32-bit and 64-bit ODBC drivers of Intersystems as In SSRS, the Report Manager and Report server are 64-bit components and BIDS Environment (Development Studio of SSRS) is 32-bit.
After few hours of research on this error and by going through the forums and InterSystems website, it seems like they have a 64-bit ODBC Driver available. The 32-bit driver which we are currently using is the version released in 2008.
I downloaded the 64-bit Cache 2008.2.6 from their FTP site and installed it on our SSRS box ftp://ftp.intersystems.com/pub/cache/odbc/ and this fixed the error
Labels:
SSRS,
Tips and Tricks,
Troubleshooting
| Reactions: |
Wednesday, March 20, 2013
Applying Custom filters to Dynamics AX Enterprise Portal Grid
Dear All,
There was a small hiccup while referencing FilterCondition and Typ as I didn't knew the namespace, so before we use the filterObject and conditionType objects, dont forget to declare the below highlighted namespace.
using Microsoft.Dynamics.Framework.Data.Ax;
Microsoft.Dynamics.Framework.Data.Ax.filterObject
Microsoft.Dynamics.Framework.Data.Ax.conditionType
Hope you are doing well.
Recently, I did an Enterprise Portal code upgrade for one of my customers. They are on Dynamics AX 2009 and as I was investigating, I found that the web forms of Dynamics AX 4.0 were not upgraded by their previous vendor, so I undertook the task of upgrading their 20+ web forms (Dynamics AX 4.0) to Dynamics AX 2009 web controls.
I had to replace the existing standard filters which comes with EP AxGridView to custom textbox filters. And, for this reason I had to apply the filters via code. I got a good idea by seeing this useful blog on how to achieve it http://blogs.msdn.com/b/epblog/archive/2008/11/17/filtering-a-dataset-from-code-behind.aspx
There was a small hiccup while referencing FilterCondition and Typ as I didn't knew the namespace, so before we use the filterObject and conditionType objects, dont forget to declare the below highlighted namespace.
using Microsoft.Dynamics.Framework.Data.Ax;
Microsoft.Dynamics.Framework.Data.Ax.filterObject
Microsoft.Dynamics.Framework.Data.Ax.conditionType
| Reactions: |
Subscribe to:
Posts (Atom)