Delete/Unassigned bulk items from Sites or Assign bulk Items to Sites
July 28, 2015
Â· Sandip Jadhav Â· No Comments
Tags: chrome, dynamics, helvetica, integration, Inventory, management, manufacturing, mbs-credentials, microsoft Â· Posted in: Blogs I Follow Total Views: 5
This issue has already been reported and itâs also been addressed. I would like to post this still. To act more like a pointer. Itâs quite crucial in nature.
I have been testing GP2015 R2 upgrade on my test environment when I faced the following error message:
Quite evidently, upgrade didnât go through after. I remembered this being posted on our GP Support & Services blog. Dug the post and got the solution.
Hereâs the post: Known Upgrade Issues When Upgrading To Microsoft Dynamics GP 2015 R2
Please note that this has been fixed already and is available with June 2015 Update.
July 27, 2015
Â· Vaidyanathan Mohan Â· No Comments
Tags: books, documentation, dynamics, fixed-assets, philosophy, programming, Sales Order Processing, sql reporting services, sql server, utilities, windows Â· Posted in: Blogs I Follow Total Views: 8
I have created a few Telegram Messenger groups for various Microsoft Dynamics technologies for increasing efficient collaboration among the community folks. This was createdÂ as I was thinking of anÂ different kind of platform apart from communities to interact with the community members.
With the growing demand and social media insight, I decided to use one of the social media networking tool to create a community for Microsoft Dynamics. The reason for choosing Telegram (as against Whatsapp) is that people can join with the help of a link and it does not require an administrator to add people to the network. Also, we can chat from mobiles/laptops/desktops/tablets etc across different platforms and completely free, on the cloud and better encryption of the dataâŠ
Please join these communities and benefit by closely interacting with community members and experts in a much closer and faster environment.
You can join Telegram by clicking the link below. https://telegram.org/dl
Once you join, send me an email to firstname.lastname@example.orgÂ and I will send you the link to join the group.This is to tighten the security of who joins the group and to avoid spam messages flowing in. Hence the group registrations are a little controlled at this time.
Looking forward for your participation in these groups and increased collaboration in the communitiesâŠ
In this article, I will take you through the errors you could get and how to resolve them. Some of these you might know from previous versions, others are new to GP 2015.
For this article I am using Microsoft Dynamics GP 2015 R2 and Dexterity 14.00.0084 which comes on the DVD image. I have copied a cleanÂ Dynamics.dic from the application folder into a subfolder in the Dexterity folder. I opened the dictionary with Dexterity and selected Debug >> Test Mode (Ctrl-T).
The first error I get is âYou need to run Dynamics.dic Utilities before you can run Dynamics.dic. Do you want to launch Dynamics.dic Utilities now?â.
Note: The name of theÂ dictionary (in this case Dynamics.dic) will be whatever your development dictionary file is called.
This issue isÂ has been around since the beginning and is because the Dynamics code is looking at the Dex.ini file for the settings INITIAL and SYNCHRONIZE and unless it can find those set toÂ FALSE, it will think that it is the first time Dynamics GP is being launched and ask to go to the Utilities to set up the databases andÂ synchronize theÂ dictionary to the account framework.
Solution:Â The easiest solution is to copy the Dex.ini file from the Applicationâs Data subfolder to the Dexterityâs Data subfolder. However,Â be sure to makeÂ the couple of changes below:
- ChangeÂ DexHelpPath to point to the Dexterity folder.
- Add ShowResids=TRUE (for pre GP 2015, GP 2015 nowÂ shows Resource IDsÂ as default)
Launching into Test Mode again and I get âUnhandled script exception: SCRIPTS â data area EXCEPTION_CLASS_SCRIPT_MEMORY SCRIPT_CMD_EXTERNâ
Â Clicking OK and the Login window opens, but it is not fully drawn.
The problem here is that script that reads the ODBC Data Sources for the Server drop down list is trying to call an external library. This library is part of Dynamics GP, but not actually part of Dexterity and so is not installed.
Solution: Copy the GPDWIN32.dll from the Application folder to the Dexterity folder. This issue started from Microsoft Dynamics GP 2010 onwards.
Launching Test Mode again and I can login, but get another error just after login. The error is âCould not load file or assembly âMicrosoft.Dynamics.GP.BusinessIntelligence.Homepageâ or one of its dependencies. The system cannot find the file specified.â.
This issue was introduced with Microsoft Dynamics GP 2013 when the homepage was changed.
Solution: Copy the following files from the Application folder to the Dexterity folder:
However, the error will still occur as GP 2015 now also requires the following file to be copied:
Finally,Â you will also need to copy the following file toÂ the folder where your development dictionary resides to avoid warnings when compiling:
Depending on your scripts you might also need the following files copied to the development dictionary folder to allow compilation without errors:
Now you should be good to go. Good luck.
For more information, see these previous articles from my old blog:
- Could not load external âDexIsODBCsqlDriver@GPDWIN32.dllâ
- Could not load file or assembly âMicrosoft.Dynamics.GP.BusinessIntelligence.Homepage.dllâ
Hope this article helps make your life easier.
This article was originally posted on http://www.winthropdc.com/blog.
Originally posted here:
Developing using Dexterity for Microsoft Dynamics GP 2015
July 24, 2015
Â· WinthropDC Â· No Comments
Tags: 2015, 2015 r2, databases, Dex.ini, facebook, gp 2015, integration, microsoft, news, support debugging tool Â· Posted in: Blogs I Follow Total Views: 16
Dynamics GP – Cashbook Bank Management (CBM) vs. Electronic Bank Management (EBM) vs. Bank Reconciliation (BR)
I have been doing a fair bit of explanation around Cashbook Management and Bank Reconciliation modules in GP over the past few weeks. I found the explanation from Brian Wick below was pretty good. To add on to his excellent explanation â here are a few additional items –
Cashbook Management –
- Cashbook has support for more Multicurrency transactions. They can do bank transfers in as many as four currencies at the same time for instance whereas Bank Rec allows just two
- Easier to track Tax with Bank Transactions (However, you should typically be using AR/AP modules in GP and let tax flow from there) . Iâve heard the argument from some customers that they have been told that this is the only way to track tax when accounting for GST or VAT. That is NOT correct!Â
- Support for more transaction types such as GL Checks and RM Checks with don’t really have a counterpart in the Ban Rec product
- No eConnect Import Interface
- More commonly Used, better and easier to supportÂ
- Works well and meets most requirements other than the 4 currency bank transfer requirement discussed above.
- Has eConnect Import Interface
Cashbook Bank Management (CBM) vs. Electronic Bank Management (EBM) vs. Bank Reconciliation (BR)
(Bank Management (BM) refers to both CBM and EBM)
The major difference between Bank Management and the Bank Reconciliation is that the Bank Reconciliation receives most of it transactions from other modules. Debtors and creditors cash transactions are captured in RM and PM and Bank Reconciliation is updated accordingly.
You can capture all your cash transactions in Bank Management and RM, PM and GL will be updated accordingly. The windows updated in Great Plains are RM Cash Receipts, RM Transaction Entry (payments to debtors), PM Manual Payments, PM Transaction Entry (receipts from creditors) and GL General Entry.
However in the CBM transactions captured in PM transaction entry, RM transaction entry, SOP, invoicing and PM computer cheques also update CBM in the same way that Bank Reconciliation is updated.
The reconcile functions in CBM and Bank Reconciliation are very similar so the major difference between CBM and Bank Reconciliation is that Bank Reconciliation receives transactions from other modules and Bank Management is a single point of entry for all cash transactions. All other differences are in functionality: Batch processing, full multicurrency, Electronic Reconcile Management (Auto Bank Recon), Intercompany Payments and Deposits, Intercompany many to many Bank Transfers, Payments to Debtors and Receipts to Creditors ext.
The difference between the CBM/Bank Reconcile and EBM is due to the fact that in EBM you do not have any source documents (Cheque counterfoils, Deposit slips ext.) as 90% of the transactions are done via electronic transfer. So the first time we find out about a transaction is when it appears on the bank statement.
In CBM and Bank Reconciliation we capture our transactions from source documents (Cheque counterfoils and deposit slips) and then reconcile the transactions that are on the bank statement to the transactions that we have already captured.
In EBM we capture our transactions from the bank statement and then post the transactions to RM, PM and GL. As the source document is the bank statement there is no need to do a separate reconcile so the post and the reconcile is one process.
In EBM we do however allow for transaction that originate form counterfoils and deposit slips. When this happens the user will capture these transactions in RM and PM but instead of posting to the Bank Account the transactions will post to a Holding account. When the transactions appear on the Bank Statement they will be captured as normal and then matched to the original transactions in the Holding Account. Regardless of the type of the transaction (GL, AP or AR) EBM will create GL transactions moving the money from the Holding account to the Bank Account. Thus the Bank Account will only be affected by transactions that have appeared on a bank statement. By doing this the Bank Account will always have a true balance.
So the difference between CBM/Bank Reconcile and EBM is that CBM/Bank Reconcile are driven by source documents and EBM is driven by the Bank Statement.
Partner Online Technical Community
July 23, 2015
Â· Jivtesh Singh Â· No Comments
Tags: amazon, bank reconciliation, business, cash, Customizations, extender, funny, great plains, security, transactions, windows Â· Posted in: Blogs I Follow Total Views: 11
Deploy The Sample Company Â· Create A … of a Dynamics GP Consultant on the Microsoft Dynamics GP Community Site Visit coralcurve | A Consultants Dabblings In Dynamics CRM Perfect Image Email azurecurve View Ian Grieve’s about.me View Ian Grieve’s profile on LinkedIn View azurecurve’s Feed on Twitter MVP Profile View azurecurve’s facebook page View azurecurve’s Google+ View azurecurve’s Summary RSS Feed View azurecurve’s Detailed RSS FeedÂ …
As mentioned in recent posts, GP Power Tools is almost ready for release. The user guide manual documentation is nowÂ completedâŠ all 256 pages of it. If you want to get the code now, you can alreadyÂ install the public beta and upgrade to the final release later.
This is the first articleÂ in a series of Whatâs New posts for GP Power Tools. The aim of this series is to highlight some of the new features of the tool and flesh out more details than the 21 reasons to upgrade article.
When creating GP Power Tools, one of the first changes (other than rebranding) was to change the data storage from a Debugger.xml setup file toÂ tables in the system database on SQL Server.
A bit of history âŠ. The Debugger.xml file was originally used to avoid the creation of any SQL objects toÂ allow easy installation and removal of the Support Debugging Tool for its role as a troubleshooting tool. As the functionality of the tool grew andÂ more data was stored in the Debugger.xml, performance slowed asÂ the data wasÂ written to and read fromÂ the Debugger.xml file. To help with the read performance, ctree tables were used to cache the contents of the Debugger.xml.Â Also, the additional features addedÂ to the tool meant that the Debugger.xml needed to be stored in a shared network location. Finally, because the tool has lots more functionalityÂ than the original troubleshooting tool,Â it was being left installedÂ on systemsÂ and the ease of removal was no longer important.
When creating GP Power Tools, one of the first changes (other than rebranding) was to change the data storage to use SQL Server tables. You would think that this would be a simple change, but it took about two weeks to complete. To make the Debugger.xml setup file work as a storage system required a large amount of custom code. The windows would read the Debugger.xml contents into temporary tables and then read and write from the temporary tables. When saving or applying, the data was written back the Debugger.xml file and the cache tables. All this code needed to be removed and replaced with more conventional code to use the SQL tables. To complicate the conversion, on some windows, data needed to be stored temporarily and only saved to the physical tables when applied. This meant that additional code was needed to store data in temporary tables until applied.
The end result is that when saving data, there is no longer a noticeable pause as the data is written. Also there is no requirement for a shared location to store the Debugger.xml file, however a shared location is still useful to centralize storage of log and export files. Finally, having the data stored in SQL Server is more secure than a shared location in the file system.
One of the areas of feedback received about the Support Debugging Tool was that it was difficult to find the options / windows. Part of the cause of this is that when new features were added, their navigation optionsÂ were just added to the bottom of the Standard Mode or Advanced Mode features.
So GP Power Tools resolves this by providing multiple options for navigation as well as grouping the features. You can still find the main GP Power Tools Logging Control window on the Tools menus of the application and individual windows (both menu or ribbon style). The Ctrl-D keyboard shortcut is also still available.
You can also find the options on the Standard Toolbar and Quick links on the home page.
From the main GP Power Tools window, you can use the Options button drop list or the GP Power Tools window menu to access other features. Both of these menus are now broken down with sub menus into functional areas:
- Resources and Security
- Export and Import
Also, GP Power Tools has been added to the application level menus as a sub menu underÂ Transactions, Inquiry, Reports, Cards, Setup,Â Utilities and Routines.
The AreaÂ Page means that navigation on theÂ Microsoft Dynamics GP Web Client is now simpler.
Access to the windows is controlled by application level security and the four automatically created security roles:
- GP POWER TOOLS USER â For Standard Mode (User)Â features
- GP POWER TOOLS ADMIN â For Advanced Mode (Administrator) features
- GP POWER TOOLS PASSWORD â For Administrator Password Setup window only
- GP POWER TOOLS SERVICES â For GP 2015 (or later) Service Enabled Procedures
Note: Access to Advanced Mode features also requires sysadmin or dbo access at the SQL Server level and the System Password or Administrator Password (ifÂ enabled). The option to hide Advanced Mode features using a Dex.ini setting is no longer used.
So nowÂ you should have no trouble navigating the various windows of GP Power Tools by whatever method you decide.
This article was originally posted on http://www.winthropdc.com/blog.
Originally posted here:
#GPPT Whatâs New: GP Power Tools is faster and easier to navigate