Error updating replicated tables

thetallbloke
Member Posts: 66
Hi Guys,
I have a Dynamics NAV 2009 installation using a SQL Server 2008 database. I have a number of tables in this database being replicated out to another database and then from there replicated out to other mobile databases using HTTPS, etc...
This all works great.. change the data in Nav using the classic or RTC, and the data flows out to all the replicated databases.
My problem arises when I try to modify a table throught classic client. I tried adding a new field to one of my tables that is being replicated using the table designer.. When I try to save and compile, I get the following error message:
I did a test to see if I could modify a repliated table using the SQL Management Studio and SQL Server is more than happy for me to modify a replicated table. It only seems to be Nav that spits about it.
Has anyone seen this before and know how to get around it...????
I'm happy to consider any of the following options:
1) Modify my publication to get around it
2) Beat Nav into submission so that it doesn't have this issue
I can't get rid of the replication.
This is quite a major issue for us as when we upgrade our client's sites and try to import objects that touch replicated tables, we get the error.
Any suggestions would be greatly appreciated..
Thanks
I have a Dynamics NAV 2009 installation using a SQL Server 2008 database. I have a number of tables in this database being replicated out to another database and then from there replicated out to other mobile databases using HTTPS, etc...
This all works great.. change the data in Nav using the classic or RTC, and the data flows out to all the replicated databases.
My problem arises when I try to modify a table throught classic client. I tried adding a new field to one of my tables that is being replicated using the table designer.. When I try to save and compile, I get the following error message:
I did a test to see if I could modify a repliated table using the SQL Management Studio and SQL Server is more than happy for me to modify a replicated table. It only seems to be Nav that spits about it.
Has anyone seen this before and know how to get around it...????
I'm happy to consider any of the following options:
1) Modify my publication to get around it
2) Beat Nav into submission so that it doesn't have this issue
I can't get rid of the replication.
This is quite a major issue for us as when we upgrade our client's sites and try to import objects that touch replicated tables, we get the error.
Any suggestions would be greatly appreciated..
Thanks
.
I'm not crazy !!! Just ask my toaster...
.
I'm not crazy !!! Just ask my toaster...
.
0
Comments
-
I've seen this post a few times over the past month or so, although I can't remember if it's on here or DynamicsUser. Search both and you should find the answer.0
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions