GP2010 SP3 Enhanced Intrastats VAT number format wrong IE (Ireland) and others…

07/11/2013 UPDATE: Partner has referred the matter to GP Fargo…

17/04/2015 UPDATE: New post with a fix

Tax registration numbers change

The Tax Registration number validation implementation looks to be flawed. Every EC country has VAT number formats they use, and regular expressions can be derived for most of them. Be aware that they are dynamic formats, regularly (well relatively) validation changes. As Microsoft Dynamics GP users this catches us out when it happens between releases as we need to wait for a hot fix.

At my company we have a SQL table of regular expressions against ISO country code, that we maintain for our website to validate the tax registration number formats entered by users. It is surprising how often we end up tweaking them, for new ISO country codes, a country changing a format, a country joining the EC etc. However when we get to GP this is very painful. I understand that in Dynamics AX, there is a user setup form where you can play with the the validator format for each country code. In GP we don’t seem to have this. From what I can tell whatever validation is occurring, the rules do not even reside in a table. It looks like it is complied into the app code!

I remember the same issue with valid Belgium VAT numbers not being accepted a while back, a hot fix followed to fix it that time.

Irish IE VAT number – Invalid Format

So today a customer presented, a newly created Irish company that uses the new Irish VAT number that now permits two letters at the end (e.g. 123456SH), this is a new format we’d not seen before and GP baulked at it with the familiar “Invalid Format” validation error on trying to enter it. First the sales staff checked with the VIES online checker see my GP implementation of this here, Dynamics GP real time EU tax registration number validation using VIESit validated fine.

Checking with the VAT number format on the  “.gov” website EU country codes, VAT numbers and VAT in other languages, it seems it is indeed valid. So we updated our website table, checked for any other country changes and then were left with no way to make GP take the number (other than direct to SQL). Time to raise a support ticket with our partner.

Valid Formats


(8 or 9 characters)





I guess I’m saying that the country code setup window should have the ability to enter a regex (for advanced users), to allow us to intervene when these formats change, without the serious expense and time of having to test and deploy hot fixes. Obviously I’d expect the regex to come out in a table in SQL somewhere in that scenario.

Dynamics GP Add in “Cannot load file or assembly Microsoft.Lync.Utilities”

GP Add in raised exception

After applying GP2010 SP3 my GP add in started raising an exception on windows forms that used Entity Framework (EF). The error reported was

System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.Lync.Utilities, Version=…"

…but I don’t use Lync…

But I know Dynamics GP does have integration with Lync. It had me puzzled for a while as I wondered why my form was causing this assembly to be required and attempting to load it. Eventually the penny dropped after studying the stack trace. The stack trace was mentioning about System.Reflection and System.Data.Metadata.Edm.DefaultAssemblyResolver.GetAllDiscoverableAssemblies().  I guessed there was some dynamic loading going on and got mislead reading up on MEF, thinking perhaps GP implemented it under the covers. I then hit lucky on Google with Craig Suntz’s blog that explained my issue. It is down to Entity Framework connection strings.

Entity Framework Connection Strings

In my EF connection string I was building my connection string like this from the SQL connection string.

Dim entityBuilder As New EntityClient.EntityConnectionStringBuilder()
entityBuilder.Provider = "System.Data.SqlClient"
entityBuilder.ProviderConnectionString = sqlBuilder.ToString
entityBuilder.Metadata = _
Return entityBuilder.ToString()

Notice the “res://*” bit, the Metadata reference. The files are embedded into the assembly as resources and this Metadata property is the pointer to them. Specifying * instructs a reflective search through all assemblies (even if not yet loaded)  that are referenced by the application, looking for the resources.

I guess that as Lync SDK was referenced by GP 2010 my attempt to create the connection was causing the Lync assembly to be loaded in order to check it for the meta file resource. The consequence of this is that we got an application exception as that assembly does not exist on the machines in our organisation.


The solution is to explicitly specify the assembly name that holds the resource as shown in the next code snippet. Making this exact reference is more efficient by it preventing unnecessary loading of assemblies and thus preventing the error . This is interesting as I’d experienced a performance hit on these windows vs ones not using EF. I assume some of that was down to this attempt to load all the assemblies.

Dim entityBuilder As New EntityClient.EntityConnectionStringBuilder()
entityBuilder.Provider = "System.Data.SqlClient"
entityBuilder.ProviderConnectionString = sqlBuilder.ToString
entityBuilder.Metadata = "res://GP AddIn GUI Library/Inventory.DAL.InventoryModel.csdl|res://GP AddIn GUI Library/Inventory.DAL.InventoryModel.ssdl|res://GP AddIn GUI Library/Inventory.DAL.InventoryModel.msl"
Return entityBuilder.ToString()


After recompiling and then deploying to the GP add in folder, my problem went away. I suspect if I spent some more time on this that the Lync assemblies are stuffed into the Global Assembly Cache by the SP3 installer, as we do copy deployments to the client machines we will be missing those assemblies. Hence not everyone may suffer this issue when using add ins if you run the full installer. However this guesswork needs researching and I’ve not got time right now to investigate.

About MEF (Microsoft Extensibility Framework)

In my Google search of the issue, it looks like you can get issues around MEF with dynamically loading assemblies, so for those of you finding this post through Google and not using Dynamics GP, then that might be a term to try on Google for a solution in your scenario.

Below is the original error

Raised by by Add-in for those still with an interest…


Formatting notes using GP econnect

Note to self:

My solution is to run in a stored procedure after econnect,

-- fix formatting of the notes field that gets screwed up by econnect loosing line breaks     
UPDATE  sy03900
    SET txtfield = replace(CAST (txtfield AS VARCHAR (MAX)), CHAR(10), char(13))
                    FROM   rm00101
                    WHERE  custnmbr = @CUSTNMBR);
UPDATE  sy03900
    SET txtfield = replace(CAST (txtfield AS VARCHAR (MAX)), CHAR(10), char(13))
                    FROM   sop10100
                    WHERE  soptype = @SOPTYPE
                           AND sopnumbe = @SOPNUMBE);

Solution to Excel Automation VB.NET/C# error running as a service 0x800A03EC - Microsoft.Office.Interop.Excel.Workbooks.Open

Overview of issue

When automating excel using a non-interactive session as a service or windows task scheduler it failed with an exception System.Runtime.InteropServices.COMException (0x800A03EC).

This did not happen when the same task was ran from the command prompt as the same user. The stack trace showed it was when we tried to open the excel sheet Microsoft.Office.Interop.Excel.Workbooks.Open

Automating Excel like this is strictly warned against by Microsoft as it is a pain. There are so many possible issues you have to work through.

Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behaviour and/or deadlock when Office is run in this environment.

Microsoft strongly recommends that developers find alternatives to Automation of Office if they need to develop server-side solutions. Because of the limitations to Office's design, changes to Office configuration are not enough to resolve all issues. Microsoft strongly recommends a number of alternatives that do not require Office to be installed server-side, and that can perform most common tasks more efficiently and more quickly than Automation. Before you involve Office as a server-side component in your project, consider alternatives.
Considerations for server-side Automation of Office

However you may manage despite all these strong words to not do it. In our case we had some complex excel documents with complicated formatting that was populated through a datasource that was latterly removed before saving. I didn’t fancy trying that in OpenXML, also we were required to produce old xls type files for output.