I’ve been absent from blogging for an obscene amount of time. Have been MIA on forums, my blog, pretty from every public medium. Except Twitter, of course.
A lot happened in the last 2 years.
The Good: My primary job now revolves around an incredible mining solution named PLODtrack. For those who are interested in knowing about that, follow the link.
The Bad: It has got absolutely no affiliation with Dynamics GP, which means I’ve not been working on GP projects for the last 2 years.
The Ugly: Several. I don’t even know from where to start.
Silverlining: I’ve gained precious experience in the last 2 years. Both professionally and personally. That’s going to drive me from now, until god knows when.
Assurance: I’ve not stopped pursuing Dynamics GP. I’m very much a Dynamics GP consultant at heart and mind. I’ve got that going for me outside of my work hours. And I have absolutely no intention of drifting away.
So, long story short, I shall try to keep this blog alive with some really nice posts. Hopefully won’t take much time from this post till the next.
I’d like to thank those who still visit some of my posts and keep this blog going.
I’m slowly moving away from Windows. However, being a Microsoft Dynamics GP consultant, that’s not entirely possible. I’ve been working hard to overcome every single roadblock since the last couple of years.
One major gripe, among several others, was the inability to connect the SQL Server instance on my Windows 10 virtual machine, mounted using Parallels. Until now.
Microsoft released SQL Server Operations Studio, which is still under preview, for us to connect to a SQL Server from Windows, Mac OS or Linux. I now have the choice to work from either my Mac OS or my Windows 10 VM.
However, there are some steps we must follow to successfully connect to a SQL Server instance on a virtual machine. This post, from Anton Sizikov, is probably the easiest one to follow. Following the steps explained on this post, Connecting SQL Operations Studio to SQL Express Server in Parallels VM, I was able to successfully use my SQL Server Operations Studio to connect to my VM SQL Server. Below is the SQL Ops Studio in all its “dark theme” glory:
I couldn’t use my Mac more than pretty much for just browsing, emailing and other daily digital chores. This is one huge step forward to start utilising it well.
System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://Server:4712/InformationService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.123.40:4712
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
— End of inner exception stack trace —
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
— End of inner exception stack trace —
Server stack trace:
at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object ins, Object outs, TimeSpan timeout) at…
With Dynamics GP 2016, some of the conventional features are going away. One such major feature is OLE Notes. From Dynamics GP 2013 R2, Microsoft made it clear that they wanted to do away with OLE Notes. We got Document Attachment feature.
With GP2015 R2, Documents Attachment cemented its position firmly. We also got a utility namely “OLE Note Migration Utility” that would help us migrate OLE Notes to Document Attachment.
Power BI Reports on Home Page – I would rather like to see Dynamics GP being added to the Power BI Connector Services. Don’t get me wrong. I love this feature, it’s great to have Power BI report widgets on GP home page. However, the ideal integration would be to see Dynamics GP Connector Service. I think that would possibly happen soon, considering the next feature.
Dynamics GP OData Service – This is going to be another important feature (HTML5 Web Client being the first one) that I have been waiting for. This will enable us to have an excellent Power BI integration. I am happy to see Power BI reports on GP Home Page, no doubt, but I am super excited about OData Service.
Named Self Serve User: With GP2015 R2, we got a new user license namely “Self Service User”. With GP2016, named self service user license is introduced. In all honesty, I have to wait and see how this differentiate itself from the previous license model.
Automatically Batch Deposit Cash Receipts: This feature reduces one step and saves lot of time. Posting a cash receipt batch would automatically create a cash deposit (either by batch or by transaction, depending on the setup). Awesome.
Manage/Edit Attachment Flows: Allows us to edit the information that flows from master to transaction and more. Enhancements are always great.