GP to BC Compare: Salesperson Master Record Tables
There are many differences between Dynamics GP and Dynamics 365 Business Central, but this page highlights the technical differences important to me between the primary master record tables for SALESPERSON for carrying over this information to BC. BC is not GP in the cloud, as you can see by the underlying table structure differences for these master records.
|
Business Central |
|
Dynamics GP |
||||||
|
Table ID |
Page ID |
Page Name |
Table Columns |
|
Table ID |
Table Name |
Form Name |
Table Columns |
|
18 |
21 |
Customer Card |
188 |
|
RM00101 |
Customer Master |
Customer Maintenance |
103 |
|
222 |
300 |
Ship-To Address |
36 |
|
RM00102 |
Customer Address Master |
Customer Address
Maintenance |
33 |
|
13 |
5116 |
Salesperson/Purchaser
Card |
31 |
|
RM00301 |
Salesperson Master |
Salesperson Maintenance |
39 |
This next table shows the best and most important field matches for the salesperson master records between Dynamics GP and Business Central.
|
Business Central |
|
Dynamics GP |
|
The Dynamics Mindset |
||
|
Table 13 |
|
Table RM00301 |
|
GP to BC SALESPERSON
Field Mapping Notes |
||
|
Field |
Field Length |
|
Field |
Field Length |
|
**Filtered and Mapped
Fields |
|
Code |
Code 20 |
|
SLPRSNID |
15 |
|
Also a D365 Sales sync
consideration |
|
Phone No. |
Text 30 |
|
PHONE1 |
20 |
|
BC only allows numbers |
|
Blocked |
Boolean |
|
INACTIVE |
tinyint |
|
BC Blocked/Unblocked; GP
Active/Inactive |
|
Commission % |
3 Decimal |
|
COMPRCNT |
smallint |
|
|
|
Name |
Text 50 |
|
SLPRSNFN |
15 |
|
BC has one name field; GP splits first and last name |
|
|
|
|
SPRSNSLN |
20 |
|
BC has one name field; GP splits first and last name |
This table shows the Dynamics GP salesperson master table fields not included in the matched field mapping above.
Many simply don’t fit, or their purpose is conceptually or fundamentally different or incompatible with a clean, straight mapping of data from GP to Business Central.
|
Dynamics GP |
|
The Dynamics Mindset |
|
Table RM00301 |
|
GP to BC SALESPERSON
Field Mapping Notes |
|
Field |
|
**UN-Mapped Fields |
|
ADDRESS1 |
|
This resides on the
Internet Information window in GP (SY01200) |
|
ADDRESS2 |
|
This resides on the
Internet Information window in GP (SY01200) |
|
ADDRESS3 |
|
BC does not have Address
3 |
|
CITY |
|
|
|
COMAPPTO |
|
GP Config Sales only or
Invoice |
|
COMMCODE |
|
Not used by GP |
|
COMMDEST |
|
|
|
COMSLLYR |
|
System-generated |
|
COMSLTDT |
|
System-generated |
|
COSTTODT |
|
System-generated |
|
COUNTRY |
|
|
|
CREATDDT |
|
System-generated |
|
CSTLSTYR |
|
System-generated |
|
DEX_ROW_ID |
|
System-generated |
|
DEX_ROW_TS |
|
System-generated |
|
EMPLOYID |
|
Associated Employee ID |
|
FAX |
|
|
|
KPCALHST |
|
GP option flag; not
relevant to BC |
|
KPERHIST |
|
GP option flag; not
relevant to BC |
|
MODIFDT |
|
System-generated |
|
NCOMSLTD |
|
System-generated |
|
NCOMSLYR |
|
System-generated |
|
NOTEINDX |
|
System-generated |
|
PHONE2 |
|
|
|
PHONE3 |
|
|
|
SALSTERR |
|
BC picklist for
assigning to Contacts (table 286, page 429) |
|
SPRSNSMN |
|
|
|
STATE |
|
|
|
STDCPRCT |
|
Commission Percent |
|
TTLCOMLY |
|
System-generated |
|
TTLCOMTD |
|
System-generated |
|
VENDORID |
|
Associated Vendor ID |
|
ZIP |
|
|
This table shows the Business Central salesperson master table fields not included in the matched field mapping above.
Many simply don’t fit, or their purpose is conceptually or fundamentally different or incompatible with a clean, straight mapping of data from GP to Business Central.
|
Business Central |
|
The Dynamics Mindset |
|
Table 13 |
|
GP to BC SALESPERSON
Field Mapping Notes |
|
Field |
|
**UN-Mapped Fields |
|
Avg. Estimated Value ($) |
|
BC auto-summary field |
|
Avg.Calcd. Current Value ($) |
|
BC auto-summary field |
|
Calcd. Current Value ($) |
|
BC auto-summary field |
|
Cost ($) |
|
BC auto-summary field |
|
Coupled to Dataverse |
|
For BC sync to D365
Sales (CRM) |
|
Coupled to Dataverse |
|
For BC sync to D365
Sales (CRM) |
|
Created At |
|
System-generated |
|
Created By |
|
System-generated |
|
Customergroup Code |
|
|
|
Department Code |
|
|
|
Duration (Min.) |
|
|
|
Email |
|
This resides on the
Internet Information window in GP (SY01200) |
|
Email 2 |
|
This resides on the
Internet Information window in GP (SY01200) |
|
Estimated Value ($) |
|
BC auto-summary field |
|
Job Title |
|
|
|
Modified At |
|
System-generated |
|
Modified By |
|
System-generated |
|
Next Task Date |
|
|
|
No. of Interactions |
|
BC auto-summary field |
|
No. of Opportunities |
|
BC auto-summary field |
|
Opportunity Entry Exists |
|
BC auto-summary field |
|
Privacy Blocked |
|
BC feature limits access
to the Salesperson |
|
RowVersion |
|
System-generated |
|
Search Email |
|
|
|
System ID |
|
System-generated |
|
Task Entry Exists |
|
BC auto-summary field |
Author’s note and Disclaimer:
Mapping ERP systems is a complex and subjective task for any one person.
Significant differences between GP and BC will require you to learn more deeply about the product to perform a successful implementation.
There is more than one way to map particular fields, but I think you’ll get a lot out of the references provided.
I am not infallible, so let me know if you spot an issue I need to update. I don’t want to present anything factually incorrect here, however how you map your data in real life is up to you.
I needed to know the differences that really matter between the master records in both Dynamics GP and Business Central. I hope you gain value from my analysis and notes.
As I do more BC implementations, and if / when BC changes, I’ll keep this up to date, and make adjustments and add additional notes where needed. I’ll also work on filling in any holes to make this complete because these are MY personal reference pages too.
Some of the tables on the individual pages probably won’t render very well on some mobile devices, but try tipping it horizontally instead!