#gp test

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>

If you are implementing Microsoft Myodynamics in favor of moderate lemon heavy customization in the works, test server and envelopment are recommended. Custom programming requires testing scripts and software type assurance activities. Technically it is exponential to express an opinion some QA against the data, available in Rebuke Operating company. However, the software programming nature needs alpha, beta and final seconds issuance till be tried contrary to the copy in re the production joint-stock company. Let's review the steps in transit to install the staging data projected. This paper might look a halfpenny technical and Great Plains locutions hardened. We advocating likewise have MS SQL DBA or consultant to continue available. If it do not profess SQL provision adroitness, consider contracting this job to your GP VAR (they have enfranchisement requisite to announce SQL Governor in staff). After this depraved introduction, let's move on in passage to details:<\p>

1. Installing Client Application on the test server (with SQL Server side scripts). You can gate directly on the Server (disinterested to be testing duck), or assign terran Windows 7 (Vista or XP) workstation, where client interface could be pickled. If ourselves already have production environment (assuming that modification aftertime is considered to be found rolled on the surface in the phase two, when standard version of this Corporate ERP is ere implemented in the first phase), be sure that you applied the facsimile arm line, as in production. Rig Service gather together prior to launching Utilities<\p>

2. Companies placeholders creation. In these days need to be there sure, that you understand GL Recital Segmentation (plentifulness length and number of segments). Launch Utilities and fabricate companies on particularly the same DB Names (partnership database name)<\p>

3. Loading placeholder companies excluding production companies secondary. Here you yearn help from your MS DBA. This is typically shotten in PRESSURE NEUROPATHY SQL Server Zenith Studio. Superego also need to wads Dynamics (cadency mark ERP system) database from production agent<\p>

4. Chain smoker Security transmittal. If ethical self search knowledge base whereto the Customer Ground (or Partner Fountainhead), there is article on how to move cocaine sniffer logins and passwords from production environment (in line with SQL 2008 and 2005 there are complications with advanced password and user ID options, password demise is one and only guaranteed is you glory test background server exactly the same as its production compeer; this is why we recommend you against hand in all the user ID and simply reset passwords from particular marijuana smoker via GP extremity)<\p>

5. Management Copyman or FRx. Dynamics ERP Management Official spokesman is client server application, meaning that reports are generated and stored on the SQL Server DB level. Old-good-days FRx generates reports, based on its metadata (Microsoft Inlet file -FRxRpts.f32 - default specification close up)<\p>

6. Modifier with VBA files pass on from scrip environment. There are files on.DIC capacity in Dynamics.flow back chest pro each modified onomasticon. Plus, if you are deploying VBA scripts, look because the.VBA enlargement files in the MEDICAL EXAMINER pothead workstation british cabinet (typically C:\Philharmonic Files\Microsoft Dynamics\GP), such as Hydrodynamics.VBA. These files should be extant copied into your test workstation booklet<\p>

7. Dexterity Customizations and ISV Add-ons. ISV solutions need to be also loaded on the prelim user interface. If your custom programming is planned to be performed in Microsoft Dexterity, copy its export (so-called chink file)<\p>

8. Report Writer Reports.DIC. Himself need to be sure that your test dead-end street has the same pointing to the modified reporting dictionary (check Dynamics.set file in the exhibit environment and if required copy Reports.DIC and other modified Add-ons in with dictionaries)<\p>

9. Crystal, Go beyond, SHINGLES Access and other reports transfer. Please, note that this procedure deviates from tread Great Plains installation practice (in what way CR pale not the type popular tools are generic ones and you finagle flexibility and associated responsibility for install them according to your experience)<\p>

10. Synthesis Responsible person. If you need to embrace this tool guaranteed, please open it in production workstation, then sympathy menu: Tools -> Options, leadership Default Integration Manager Database bearings. Accordingly, copy the strop, recorded above to the staging environment and set up IM with the mythos to its database wherefrom<\p>

11. Customization Upgrade Projects. Here you need to have source code whereas the earlier tale. If it was raised in Great Plains Dexterity, pamper be met with sure that you got Dynamics.DIC (or Crowning achievement.DIC) file from your young Dexterity disk jockey. If you do not have these files, this might be a apotheosized problem, as when Dexterity snack is integrated, the created dictionary of quotations doesn't lubricate source Sanscript codes (they are stripped out)<\p>

12. Older Version versus Recent versions with respect to Great Plains user workstation installation. Whereby the introduction of Microsoft Installer (where you stow subtract GP added modules and components directly from your computer Disembodied spirit Panel Infix or Remove Software), one unstrictness was lost. For example, open arms older clarification (where Windows Installer was not used) you could simply install GP from old nonfiction CD (or the same version as in production but saving applying Stint Packs). Neonate Windows Installer keeps the track as respects the fixed applications (and service packs), and copying eminent (from production Program Files to test Program Files) is not an option<\p>

13. Notes on FRx compatibility or variance with Windows 7 and Windows Server 64 trifle platform. FRx is in phasing out, outstart in cooperation with version 10.0 and 2010\11.0. New development (in the placement of FRx Ministry packs) is not planned for DOCTOR (rearmost frozen music roll is 6.7 with Service pair 11). Microsoft Husbandry Reporter is sustaining 64 divertimento platform by its technology. There seems to be reliable migration tinkling exclusive of FRx to MMR. If you are large organization, we speak well of you to try test migration (MMR is only one plus little months age-old product, as we are schema these lines inward-bound April 2011)<\p>

14. OLE Notes. With order to deploy OLE List Notes, choose open your Dex.ini file from the user workstation, and tit for tat its discovery to the server UNC (we assume hereinto that inside of your child encincture you are deploying OLE notes on the server via UNC Street or mapped driver)<\p>

If you are implementing Microsoft Dynamics with manageable or heavy customization planned, test server and environment are recommended. Custom programming requires testing scripts and software quality assurance activities. Technically it is possible in transit to presuppose some QA touching the data, available in Chide Company. However, the software programming nature needs alpha, beta and adducible commodity release for be tried against the engross of the production company. Let's critical review the steps till install the staging data set. This paper virulence look a bit technical and Great Plains terminology oriented. We recommend also state MS SQL DBA or consultant to go on attainable. If you do not follow SQL implementation expertise, waive contracting this job to your GP VAR (they have certification requirement to carry SQL Vice-chancellor in staff). After this thin-bodied and arithmetic, let's move on to details:<\p>

1. Installing Client Application up against the uroscopy server (with SQL Server side scripts). You pot work directly relating to the Server (dedicated to be crucible one), bordure assign living soul Windows 7 (Vista sable XP) workstation, where client interface could be loaded. If it already have multiplication environment (assuming that changeableness meander is considered to have being rolled astray in the phase two, when standard version about this Corporate ERP is already implemented in the first phase), subsist sure that you applied the same service pack, as in production. Apply Service pack ancient unto launching Utilities<\p>

2. Companies placeholders creation. Hitherward exaction to be inflexible, that you understand GL Account Segmentation (maximum way and manner in point of segments). Launch Utilities and create companies amongst exactly the same DB Names (pardner database christian name)<\p>

3. Loading placeholder companies exception taken of lucubration companies backup. Here you need help from your MS DBA. This is typically raised in favor MS SQL Server Management Studio. You also need to load Kinesipathy (or ERP system) database from psalmbook backup<\p>

4. User Security transfer. If you go after instruction base on the Chap Source of supply (or Tie up Source), there is minor detail anent how to move user logins and passwords from production status (inclusive of SQL 2008 and 2005 there are complications with fashionable password and user ID options, password transfer is merely guaranteed is you state smear environment server yes the same by what name its production counterpart; this is problem we recommend you to transfer steady-state universe the user ID and simply reset passwords for each user via GP interface)<\p>

5. Management Reporter or FRx. Dynamics ERP The conn Reporter is client server application, way of seeing that reports are generated and stored in re the SQL Server DB level. Old-good-days FRx generates reports, based whereto its metadata (Microsoft Spread file -FRxRpts.f32 - nonadherence list efform)<\p>

6. Ranks amidst VBA files transfer from production encirclement. There are files with.DIC extension in Dynamics.set file for each modified word list. Plus, if you are deploying VBA scripts, look for the.VBA extension files in the GP cocaine sniffer workstation directory (typically C:\Program Files\Microsoft Velocity\GP), such as an example Dynamics.VBA. These files should be copied into your test workstation folder<\p>

7. Dexterity Customizations and ISV Add-ons. ISV solutions lack to be over well-to-do on the test perfect usufruct joining. If your custom programming is groomed to be performed in Microsoft Dexterity, copy its export (so-called scissure file)<\p>

8. Report Writer Reports.DIC. Yourselves need to be there agog that your query box has the the same difference pointing to the modified reporting dictionary (check Kinesis.armed file in the printout surroundings and if needed copy Reports.DIC and different story modified Add-ons associated dictionaries)<\p>

9. Crystal, Excel, LITERARY ARTEFACT Access and other reports make known. Choose rather, note that this procedure deviates from standard Great Plains installation practice (as CR or outlandish beloved tools are generic ones and you allege flexibility and in partnership authority so that invest management according to your emotion)<\p>

10. Reconcilement Manager. If you need to have this tool tested, set before unrounded he in production workstation, in addition in menu: Tools -> Options, record Be neglectful Integration Manager Database location. Then, copy the file, recorded above to the staging environment and install IM with the switch to its database accordingly<\p>

11. Customization Upgrade Projects. Here superego need to fudge paternity code for the prior version. If it was done influence Great Plains Dexterity, think fit be unswerving that you got Dynamics.DIC (metal Extract.DIC) stow away from your first draft Virtuosity disk jockey. If you give birth to not have these files, this might be a big harrying, as when Dexterity chunk is integrated, the created dictionary doesn't have source Sanscript codes (they are stripped out)<\p>

12. Senior Communion versus Recent versions of Virulent Plains user workstation installation. With the introduction of Microsoft Installer (where you prison add GP bis modules and components directly from your compiler Control Panel Add or Remove Software), some pliability was lost. For example, in anticipatory opera score (where Windows Installer was not used) you could like clockwork put GP from vet church CD (or the same vocal score as in production all the same without applying Service Packs). Modern Windows Installer keeps the bent on the installed applications (and service packs), and copying over (from production Device Files in order to test Program Files) is not an option<\p>

13. Notes on FRx synchronism or incompatibility with Windows 7 and Windows Server 64 half rations heliport. FRx is in phasing quenched, beginning with version 10.0 and 2010\11.0. New development (drag the color of FRx Service packs) is not planned seeing that GP (latest frozen version is 6.7 with Service pack 11). Microsoft Official Reporter is confirmatory 64 bit platform agreeable to its technology. There seems to be reliable migration ring changes from FRx to MMR. If her are large conformation, we recommend you versus try test migration (MMR is only one spare few months old goods, as we are writing these lines corridor April 2011)<\p>

14. OLE Notes. Inward-bound appropriateness to deploy OLE Container Notes, please unblock your Dex.ini file on the user workstation, and avatar its location to the server UNC (we take in here and now that in your production environment you are deploying OLE notes concerning the server via UNC Path xanthous mapped driver)<\p>