GP2016 DAG Issue


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:

Screen Shot 2017-04-28 at 01.29.38 pm.png

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:

  1. Have you faced this issue?
  2. If so, what did you do to resolve it?
  3. 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.

Vaidy

GP2016 Upgrade – Missing Security Roles & Tasks


When upgrading to GP2016 RTM, it looks like upgrade process would skip creating new security roles and tasks, to ensure that the old ones are not messed up.

According to Dynamics GP Support & Services blog, this is intentional and we have been provided with an INSERT script that would create the new GP2016 roles and tasks. It’s more like on-demand insert.

A fresh GP2016 installation would hence be different from an upgrade.

VAIDY

Dynamics GP On-Demand Learning: Word Template Tips


Excellent post on Dynamics GP Support & Services blog that walks us through GP Word Templates.

This was the last post in the series named Microsoft Dynamics GP On Demand Learning Series.

Sincere thanks to GP Support Team, for posting these articles. Highly informative.

VAIDY

GP2016 Upgrade – Modified Dictionary Upgrade & Upgrade Troubleshooting


Over at Dynamics GP Support & Services blog, couple of posts discussing about following are available:

Both posts discuss in detail about how to upgrade modified dictionary and how to troubleshoot upgrade issues. In particular, the upgrade troubleshooting post is crucial for obvious reasons.

Just about 10 days to get my hands on Microsoft Dynamics GP 2016. It’s gonna be fun.

VAIDY

GP2016 – Version Checks & Upgrades


Informative post up on Dynamics GP Support & Services blog about Version Checks & Upgrades. It discusses about various version check issues while upgrading GP.

I have had an interesting experience with one upgrade recently. While upgrading this customer’s GP to GP2015 R2, version check failed for one particular product. After going through the tables and SET file, I learned that the product in question was not part of DYNAMICS.SET and was not physically present in GP application folder. However, the SQL objects were very much present and DU tables had records for this product with quite an old version.

Customer informed that the previous implementer had installed this product, however in due course they realised that it was not required at all. Product was removed from the application environment, so there won’t be any necessary interference, however SQL objects and records remained.

It was a pain to clean up the records and continue with the upgrade process.

Beware of all possible scenarios and plan the upgrades well.

VAIDY

#MSDYNGP Extender View Involving Extender Window/Form – Strange “Add Link” Issue & Reason.


Firstly, I am not sure whether I should categorise this as an issue. Let me explain this with an example.

For illustrative purpose, my requirement is to assign an additional information to customers. In addition to Country Code, I would like to assign from which continent a customer is from.

First step; to create an Extender Form named Continent Maintenance in which I will maintain list of continents. I do not need anything information other than an ID (Continent ID) and a name (Name); as shown below:

Snip20140114_1

Note that there are no fields apart from ID and Description.

Second step; I am going to create an Extender Window for Customer Maintenance (Cards -> Sales -> Customer -> Additional -> Continent) to assign a continent to a customer. Extender Window definition is as follows:

Snip20140114_2

Third step; is to check whether things are properly done and confirm. Let me open Customer Maintenance and see if I can access this new Extender information:

Snip20140114_3

Perfect. Let’s now get into the actual issue.

I would like to create a view to retrieve customer continent information. To achieve this, I would like to link Assign Continent (Extender Window) with Continent Maintenance (Extender Form) to get the continent name. Ideally, my view should retrieve following:

Customer ID, Continent ID, Continent Name

Now, when I try to create an Extender View linking my Extender Window and Form, I end up facing below issue:

Snip20140114_4

Snip20140114_6

Did you see that? I do not have my Extender Form fields shown here. I have two fields; Continent ID and Name. Where are they? Why are they not shown here? Shouldn’t it be available for me to link with my Extender Window’s Continent ID?

REASON: If your Extender Form DOES NOT have any other field than an ID and a Description (in my case, Continent ID and Name), ADD LINK To Field will not list out the ID and Description fields.

Is that the actual reason? Let’s confirm by adding another field to Extender Form as follows:

Snip20140114_7

After adding above field, Additional Info., look at my Extender View Add Link now:

Snip20140114_8

Did you see that? They are available now. AFTER adding a field in addition to default ID and Description fields.

And I am not sure how many have ever noticed this. I am noticing it for the first time now. I haven’t created any form with only ID and Description till now. I had to spend 4 hours to identify this reason, honestly. Had no idea whatsoever.

Those who are going to deal with Extender views with form(s) having ONLY ID and Description fields, save your 4 hours. 🙂

VAIDY

Delete a Company in Microsoft Dynamics GP – Compatible With GP 2013


We have a SQL script named ClearCompanies.sql, which is available on Customer Source or Partner Source. This script removes all references to those companies that are not available in SQL Server, but pretty much exist in GP records.

It’s an all important script for all implementers, developers and consultants. Now this script has been updated to cater for also GP 2013. I had not used this script for a long time, so never realised it till today. This is particularly important as GP 2013 now support multi-tenant architecture (multiple GP System DB on same SQL instance).

You can download this script from here (provided you have a Customer Source / Partner Source account): ClearCompanies.sql.

VAIDY