Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
CRM Connector (2011).
thjens45
Member Posts: 5
Hi everbody.
I've setup the connector and everything seems to be working. Data is synced both ways. However, there's something I don' get. In the mapping, you setup that "No." (customer no) equals "Account Number".
When you make a new Account in CRM, you have to enter a account number. But what if you enter a account number that already exists in NAV? Sure, you will get an error in the log, but thats not good enough. 50 sales pepole might enter new accounts everyday. They might enter the same account number. How is that handeld?
The user can't choose not to enter anything, the field is mandatory.
So, the question is how can I let NAV take care of granting the new account number? If NAV gets a blank customer no., the normal logiq of the triggers will generate a new number. That means the mandatory attribute of the account number in CRM must be shut of somehow.
I've tried to fiddle around with the new triggers in codeunit 1 (onDatabaseInsert, onDatabaseModify) but renaming primary key only results in errors since NAV is in the middle of and update.
Any ideas?
Thanks.
Best regards,
Thomas Jensen.
Norway.
I've setup the connector and everything seems to be working. Data is synced both ways. However, there's something I don' get. In the mapping, you setup that "No." (customer no) equals "Account Number".
When you make a new Account in CRM, you have to enter a account number. But what if you enter a account number that already exists in NAV? Sure, you will get an error in the log, but thats not good enough. 50 sales pepole might enter new accounts everyday. They might enter the same account number. How is that handeld?
The user can't choose not to enter anything, the field is mandatory.
So, the question is how can I let NAV take care of granting the new account number? If NAV gets a blank customer no., the normal logiq of the triggers will generate a new number. That means the mandatory attribute of the account number in CRM must be shut of somehow.
I've tried to fiddle around with the new triggers in codeunit 1 (onDatabaseInsert, onDatabaseModify) but renaming primary key only results in errors since NAV is in the middle of and update.
Any ideas?
Thanks.
Best regards,
Thomas Jensen.
Norway.
0
Comments
Just answered to you:
https://community.dynamics.com/product/ ... spx#129417
Konstantin