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
- 309 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 Integration, proxy tables, fields ids on the 10,000 range
Tomigs
Member Posts: 86
Hi,
In the context of an integration BC/CRM (BC20), we have used the altpgen tool to generate proxy tables and do the developments based on this. For example we have got the definition of the CRM account extension.
We have been able to work and test deploying using Visual Studio Code. However, when we have tried to deploy the developments as a properly published extensions, we get errors because it doesn't like the fields being on the 10,000 range, seems to allow only on the 50,000 range.
I thought in re-generating the proxy tables using this time the -baseid: 50000 parameter in altpgen, thinking that it would give mthe fields on the 50,000 range but it doesn't: the fields IDs are still on the 10,000 range. Looks like the baseid parameter affects only to the number of the table.
I guess what we'll have to do a manual renaming of all the fields in all of the table extensions and reset the integration that is not great.
Has anyone faced the same situation or know of a better approach?
I think it is exactly the same situation as below:
https://community.dynamics.com/business/f/dynamics-365-business-central-forum/417695/business-central-table-integration-custom-field
Thanks!
Tomas
In the context of an integration BC/CRM (BC20), we have used the altpgen tool to generate proxy tables and do the developments based on this. For example we have got the definition of the CRM account extension.
We have been able to work and test deploying using Visual Studio Code. However, when we have tried to deploy the developments as a properly published extensions, we get errors because it doesn't like the fields being on the 10,000 range, seems to allow only on the 50,000 range.
I thought in re-generating the proxy tables using this time the -baseid: 50000 parameter in altpgen, thinking that it would give mthe fields on the 50,000 range but it doesn't: the fields IDs are still on the 10,000 range. Looks like the baseid parameter affects only to the number of the table.
I guess what we'll have to do a manual renaming of all the fields in all of the table extensions and reset the integration that is not great.
Has anyone faced the same situation or know of a better approach?
I think it is exactly the same situation as below:
https://community.dynamics.com/business/f/dynamics-365-business-central-forum/417695/business-central-table-integration-custom-field
Thanks!
Tomas
0