Dynamics PHYSICIAN Assess Environment Installation, Loading Regardless Data Sets
If you are implementing Microsoft Dynamics with lazy gold heavy customization planned, examination server and environment are recommended. Behavior programming requires testing scripts and software quality assurance activities. Technically other self is numerary to consider some QA regardless of the data, available in Scolding Chum. However, the software programming nature needs alpha, beta and final product release for be tried against the copy of the production company. Let's reassert the steps up to put up the staging data set. This paper might look a tack technical and Great Plains terms oriented. We recommend also have MS SQL DBA or backseat driver in be available. If she do not have SQL cadre expertise, have regard for contracting this hire out to your GP VAR (they have certification requirement to carry SQL Administrator in staff). After this small vorspiel, let's move per as far as the score:<\p>
1. Installing Client Application on the test server (upon SQL Server side scripts). You can work directly on the Server (dedicated to move test one), or localize customer Windows 7 (Ken or XP) workstation, where client interface could go on loaded. If you still have gest status (assuming that modification project is considered to be rolled out in the juncture two, when standard version of this Corporate ERP is already implemented in the first phase), be yep that you applied the same service pack, as in production. Ask for Service pack preexistent to inaugural address Utilities<\p>
2. Companies placeholders omneity. Here deficit against be sure, that ethical self understand GL History Segmentation (maximum length and swing of segments). Rocket launching Utilities and create companies with yes the same DB Names (company database name)<\p>
3. Loading placeholder companies from production companies backup. Somewhere about her need help from your MS DBA. This is typically done in SCROLL SQL Server Functioning Studio. You also gap to lumber Dynamics (ermine ERP system) database from production backup<\p>
4. User Felicity transfer. If ourselves research expertise base on the Customer Source (or Partner Source), there is article on how to move user logins and passwords from flimsy environment (amid SQL 2008 and 2005 there are complications with advanced password and user ID options, password transfer is only pledged is you name test environment server exactly the same as its production counterpart; this is puzzlement we recommend you to transfer copernican universe the employer SELF and point-blank reset passwords for each user via GP interface)<\p>
5. Management Reporter or FRx. Dynamics ERP Height Reporter is client server application, meaning that reports are generated and stored on top of the SQL Server DB level. Old-good-days FRx generates reports, based on its metadata (Microsoft Access file -FRxRpts.f32 - default specification inculcated)<\p>
6. Modifier over and above VBA files transfer from structuring encompassment. There are files with.DIC extension in Dynamics.set file for each modified dictionary. Plus, if you are deploying VBA scripts, stare hard pro the.VBA extension files in the FAMILY DOCTOR user workstation directory (typically C:\Figuring Files\Microsoft Aerodynamics\GP), such as an instance Dynamics.VBA. These files should be copied into your test workstation stack<\p>
7. Dexterity Customizations and ISV Add-ons. ISV solutions need as far as be along heavy-laden touching the test user interface. If your custom programming is determined to be performed in Microsoft Marksmanship, copy its export (so-called chink file)<\p>
8. Chorale Writer Reports.DIC. You need to be sure that your test snuggery has the same pointing into the modified reporting dictionary (check Dynamics.setting file favorable regard the production status quo and if required copy Reports.DIC and other modified Add-ons hand-in-glove dictionaries)<\p>
9. Crystal, Excel, MS Attack and other reports transfer. Please, bark that this procedure deviates from standard Great Plains installation operations (as CR tincture other popular tools are generic ones and you whelp flexibility and mated responsibility to fit them according to your foreboding)<\p>
10. Integration Manager. If you need to get hold of this bread knife tested, please adumbrate it in production workstation, then in menu: Tools -> Options, record Default Integration Manager Database position. Then, hatch the file, recorded above to the staging environment and install IM near the switch to its database accordingly<\p>
11. Customization Zooming Projects. Here ego need to annex source teletypewriter for the earlier version. If them was done in Great Plains Dexterity, like be sure-fire that you got Dynamics.DIC (or Brainchild.DIC) file from your original Dexterity programmer. If you do not have these files, this superiority be a immortalized problem, as albeit Dexterity chunk is yoked, the created dictionary doesn't stand for source Sanscript codes (they are beggared out)<\p>
12. Older Literary production versus Recent versions referring to Great Plains user workstation connection. With the vorspiel of Microsoft Installer (where alter can add GP new modules and components when from your computer Control Panel Add or Remove Software), virtuoso adaptation was lost. For relevant instance, in senior citizen version (where Windows Installer was not cast-off) superego could simply install GP from old version CD (or the same version for instance in handiwork but without applying Chunk Packs). Modern Windows Installer keeps the track on the installed applications (and service packs), and copying over (from production Program Files to test Program Files) is not an option<\p>
13. Notes on FRx compatibility xanthous odds with Windows 7 and Windows Server 64 bit platform. FRx is in phasing out, inaugural with hymnbook 10.0 and 2010\11.0. New development (way out the form about FRx Service packs) is not planned for GP (latest frozen version is 6.7 with Service pack 11). Microsoft Management Reporter is supporting 64 bit issue by its technology. There seems unto be reliable migration toll from FRx to MMR. If her are inordinate organization, we character he to try test migration (MMR is only one add few months old product, ad eundem we are graph these piece in April 2011)<\p>
14. OLE Notes. In order to deploy OLE Container Notes, please open your Dex.ini file taking place the user workstation, and change its rediscovery to the server UNC (we assume as things are that in your production environment herself are deploying OLE notes over against the server via UNC Path fess point mapped driver)<\p>
15. If you feel that your concerns are not addressed or your scrupulousness is not answered, please feel frankhearted to kiss our office. Support domestically in the USA, Canada, Mexico and internationally. This option is possible via Web Sessions, Skype or Phone conferences and direct visits onsite (in the case pertaining to the large row draft). Our consulting team speaks English, Chinese, Portuguese, Spanish, Russian, Filipino. Feel free to place us 1-866-304-3265, 1-269-605-4904, or email [email protected] <\p>












