Archiwum
- Index
- Cooper McKenzie [Menage Amour 161 Club Esotera 03] Minding Mistress (pdf)
- Morgan Sarah PocaćąĂ˘Â€Âšunek ksiÄ™cia
- Edgar Cayce Luc
- Williams Cathy Francuska wróśźka
- Clark Lucy Podwójne szcz晜›cie
- Herries Anne Dom na urwisku
- Jeff Lindsay DzieśÂ‚o Dextera 04
- Adams Douglas 3
- Fleming Ian Pozdrowienia z Rosji
- Bevarly Elizabeth Kiedy Eryk spotkaśÂ‚ Jayne
- zanotowane.pl
- doc.pisz.pl
- pdf.pisz.pl
- lafemka.pev.pl
[ Pobierz całość w formacie PDF ]
entered your Microsoft Dynamics GP sales orders or Microsoft Dynamics CRM orders. To change this
date, click the Edit link next to the Check for data modified after area to open the Check for
data modified after window. Enter the new value and click OK. Start the Connector for Microsoft
Dynamics service again.
8. If there are Microsoft Dynamics GP orders to integrate, select the Sales Order to Order map and
click the Activate button.
9. Repeat steps 6 and 7 for the Sales Order to Order map.
10. Click Save on the top command bar.
In the Status section of the Map page, the Last run status is displayed. While the integration is
running, the Last run status is displayed as Currently running and displays the numbers of
changes found, changes written, deletions found, records deleted, and failures. Wait until the
Currently running status is no longer displayed and the Last run status is displayed to allow the
integration to run and move the Microsoft Dynamics GP sales orders to Microsoft Dynamics CRM
and the Microsoft Dynamics CRM orders to Microsoft Dynamics GP.
11. Verify that all the orders have been fully integrated.
12. Repeat steps 1 through 7 for the Sales Invoice to Invoice map.
Note: Invoices can only be integrated from Microsoft Dynamics GP to Microsoft Dynamics CRM.
13. Click the View log for this map link at the top of the Status section. Review any events that are
displayed and fix any issues before proceeding. For more information about reviewing the log file,
see the Connector for Microsoft Dynamics installation guide.
14. To change the map run schedule for ongoing integration, repeat step 6 and change the map run
schedule to the appropriate settings for this map.
34
CONNECTOR FOR MICROSOFT DYNAMICS CONFIGURATION GUIDE FOR MICROSOFT DYNAMICS® GP
Customization
The following sections contain information about how to configure Connector for Microsoft Dynamics.
For more information, see the Connector for Microsoft Dynamics installation guide.
Customize map settings
After you have created an integration, you must add maps, which are collections of associations
between the fields for an entity in one Microsoft Dynamics system with the fields for an entity in
another Microsoft Dynamics system. For example, to integrate the Microsoft Dynamics CRM account
entity with the Microsoft Dynamics GP customer entity, you must add and activate the Account to
Customer map and the Customer to Account map.
If you created an integration from a template, maps have already been created for you. For more
information about customization, see the Connector for Microsoft Dynamics installation guide.
Maintenance and additional information
Connector for Microsoft Dynamics has several options for maintaining your integrations. For more
information, see the Connector for Microsoft Dynamics installation guide.
For more information about using Connector for Microsoft Dynamics ERP, and for troubleshooting tips
and customization techniques, see the Connector Integrating Dynamics ERP with Dynamics CRM
blog on MSDN (http://blogs.msdn.com/b/dynamicsconnector/).
35
CONNECTOR FOR MICROSOFT DYNAMICS CONFIGURATION GUIDE FOR MICROSOFT DYNAMICS® GP
Appendix
The following sections are provided for your reference.
·ð Integration exceptions
·ð Map dependencies
·ð Microsoft Dynamics CRM to Microsoft Dynamics GP maps
·ð Microsoft Dynamics GP to Microsoft Dynamics CRM maps
·ð Picklist synchronization processing
36
CONNECTOR FOR MICROSOFT DYNAMICS CONFIGURATION GUIDE FOR MICROSOFT DYNAMICS® GP
Integration exceptions
If the integration encounters an exception that is considered a possible retry, such as attempting to
create an order in Microsoft Dynamics GP that would cause the customer balance to exceed the credit
limit, that particular integration instance is placed in a retry queue.
Retry occurrences are based on a progressively time-delayed algorithm that allows up to seven retries
per instance. The default retry wait setting is five tries.
The following table indicates the actual time between each retry attempt based on the configurable
retry wait setting.
Retry Attempt
Retry
1 2 3 4 5 6 7
Wait
Secs Secs Mins Secs Mins Secs Hrs Mins Secs Days Hrs Mins Secs Days Hrs Mins Secs
Setting
7 7 49 5 43 40 1 4 40 7 1 8 40 49 9 12 45 43
6 6 36 3 36 21 36 2 9 36 0 12 57 36 3 5 45 36
5 5 25 2 5 10 25 0 52 5 0 4 20 25 0 21 42 5
4 4 16 1 4 4 16 0 17 4 0 1 8 16 0 4 33 4
3 3 9 0 27 1 21 0 4 3 0 0 12 9 0 0 36 27
2 2 4 0 8 0 16 0 0 32 0 0 1 4 0 0 2 8
1 1 1 0 1 0 1 0 0 1 0 0 0 1 0 0 0 1
37
CONNECTOR FOR MICROSOFT DYNAMICS CONFIGURATION GUIDE FOR MICROSOFT DYNAMICS® GP
Map dependencies
Some maps in Connector for Microsoft Dynamics are dependent on values in other maps. Maps with a
high number of dependencies will not successfully run until dependent values in other maps are
integrated first. Map dependencies are listed below.
Microsoft Dynamics GP to Microsoft Dynamics CRM
The following dependencies exist when mapping entities from Microsoft Dynamics GP to Microsoft
Dynamics CRM.
Map Dependency
Salesperson to ERP System ·ð No dependency
User
UofM Schedule to Unit Group ·ð No dependency
Sales Item to Product ·ð UofM Schedule to Unit Group
·ð Pricing Header to Pricing Header
Flat Fee to Product ·ð UofM Schedule to Unit Group
·ð Pricing Header to Pricing Header
Miscellaneous Charges to ·ð UofM Schedule to Unit Group
Product
·ð Pricing Header to Pricing Header
Service to Product ·ð UofM Schedule to Unit Group
·ð Pricing Header to Pricing Header
Kit to Product ·ð UofM Schedule to Unit Group
·ð Pricing Header to Pricing Header
·ð Sales Item to Product
·ð Flat Fee to Product
·ð Miscellaneous Charges to Product
·ð Service to Product
Customer to Account ·ð Pricing Header to Pricing Header
·ð Price Level to Price List
·ð Salesperson to ERP System User
·ð For a customer that has a parent customer dependency, Customer to
Account might be dependent on the parent customer integrating first
Customer to Contact ·ð Salesperson to ERP System User
·ð Pricing Header to Pricing Header
·ð Price Level to Price List
·ð For a customer that has a parent customer dependency, Customer to
Account might be dependent on the parent customer integrating first
Sales Order to Order ·ð Salesperson to ERP System User
·ð UofM Schedule to Unit Group
·ð Sales Item to Product
·ð Flat Fee to Product
·ð Miscellaneous Charges to Product
·ð Service to Product
·ð Kit to Product
·ð Price Level to Price List
·ð Customer to Account or Customer to Contact
38
CONNECTOR FOR MICROSOFT DYNAMICS CONFIGURATION GUIDE FOR MICROSOFT DYNAMICS® GP
Map Dependency
Sales Invoice to Invoice ·ð Salesperson to ERP System User
·ð UofM Schedule to Unit Group
·ð Sales Item to Product
·ð Flat Fee to Product
[ Pobierz całość w formacie PDF ]