I am wondering whether someone has already faced this issue and has shared his/her knowledge on this.
My issue is with GP2016 VS Tools Dictionary Assembly Generator (DAG), where it takes more than 10 mins to complete generating DYNAMICS.DIC assemblies. Not only that, it also doesn’t generate Application.MicrosoftDynamicsGp.dll in the first attempt itself.
Look at the following screenshot:
First two “successful” attempts of running DAG created only the metadata files and not the actual DLL. I’m running the DAG for the third time, as I write this post.
UPDATE: Third time’s the charm. I am baffled, though.
I have no clue, whatsoever, about why this is happening.
My question(s) to all you guys:
Have you faced this issue?
If so, what did you do to resolve it?
If you have not found any solution (other than running DAG till it creates the DLL), have you already reported this to GP dev team?
Please shed some light on this by sharing your thoughts on the comments section.
Apparently, it was my DYNAMICS.SET that was causing this issue. I removed my customisation dictionaries from GP folder, removed all necessary entries from my SET file. However, I totally forgot to reduce the number of dictionaries at the top of my SET file. Silly me!
Once I corrected my SET file, I was able to apply the YE2016 patch. All was well.
One thing I would like to emphasise here: Those who post questions on our GP forum, please mark the response as “answer” without fail. You would help others who search for an answer. You’d also give due credit to the person who shared his/her knowledge.
Another excellent article from Barry Crowell on Dynamics GP and Power BI:
During my last blog post, I walked you through creating a financial dashboard using Power BI with Dynamics GP data. I have created additional analysis and measures now. If you look closely at the bottom left, you will see two additional reports for Sales Summary and Customer Analysis. Sales Summary The data used from Dynamics […]
Back in October of 2015, I posted a blog about how to modify Jared Hall’s awesome Excel Financial Dashboard that you can download here. The problem with his solutions is that most Dynamics GP environments are multi-company setups making these dashboards not very functional without navigating and opening multiple Excel spreadsheets to view each company’s […]
I was trying to install VS Tools for GP2015 R2 on my machine that has already got VS Tools for GP2016 installed. I could not complete the installation and received following error message (and its corresponding Event Log).
Please note, on the event log, it says “GP 2016 SDK” while I was trying to install GP2015 VS Tools SDK.
Has someone faced this error? If so, could you please share with us on how you resolved it? Have you resolved it at all?
It’s been more than couple of weeks since the cumulative update 15 (CU15) for Management Reporter (MR) had been released. With MR CU15, we got some really interesting feature additions and plenty of fixes.
We did not have this feature till CU15. Users had to either use browser’s print option (which would render the report awkwardly) OR they had to download the report to Report Viewer. I had received many requests from customers to help them change the default viewing client from Web Viewer to Report Viewer.
However, sadly, this feature has solved only 1/2 the printing limitation. It does give you an option to print a report, but does not let you print it.
Let me explain. You have an option to only download the report as an XPS file using this new *printing* feature. How about that? To be honest, this has rather created more confusion. I have to download the report as an XPS file, open that XPS file using XPS Viewer and then print the report to a printer/PDF writer.
I’ve been thinking. Even if downloading the report as a PDF file is possible (along with Excel, XPS & Report Viewer), we might not feel the absence of a direct print functionality.
With the tools that we have now and the kind of programming talent available, how difficult is it to achieve this simple yet crucial functionality?