Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
[solved]Use Default Synchronization Setup - Sorry, we just updated this page
Tomigs
Member Posts: 85
Hi all,
I have an issue with the BC-CRM integration through the dataverse.
When I try to set the Default integration settings on the Integration Table Mappings I get the error "Sorry, we just updated this page. Reopen and try again.". Has anyone else got this error?
The version is BC 19.3.34541.34662.
I do have some customizations on the integration, that is precisely what I want to deploy by this action. But if I uninstall my extensions I keep receiving the same error. So, unless I'm doing something wrong I get the impression it is a bug, but I didn't see any reference to this on the list of released hotfixes.
Any suggestion is welcome.
Thanks,
Tomas
I have an issue with the BC-CRM integration through the dataverse.
When I try to set the Default integration settings on the Integration Table Mappings I get the error "Sorry, we just updated this page. Reopen and try again.". Has anyone else got this error?
The version is BC 19.3.34541.34662.
I do have some customizations on the integration, that is precisely what I want to deploy by this action. But if I uninstall my extensions I keep receiving the same error. So, unless I'm doing something wrong I get the impression it is a bug, but I didn't see any reference to this on the list of released hotfixes.
Any suggestion is welcome.
Thanks,
Tomas
0
Answers
I'm not conscious of having made any relevant change but today it is working fine.
My guess is that it was some piece of code on my extension that was incorrect.
And why it didn't work without the extension: no idea, maybe I tested it incorrectly and the extension was still there. Maybe some refreshing issue with my session.
Thanks,
Tomas