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
NAV 2015 Schema Synchronisation
ta5
Member Posts: 1,164
Hi
Before NAV 2015 it was possible to import a FOB file with potentially destroying data (delete, shorten, change data type of fields) IF (and only then) no data were affected. This means, deleting a field with no data in all companies of that given db was perfectly possible, and if data were affected, the FOB import was cancelled. So the import of the object was a perfect last test/validation, for example if a migration tool did forget to delete/move data.
As we know in NAV 2015 the synchronisation paradigma has changed.
Importing a FOB on customer side is now different, the user has to decide between 3 options. If the user choses the option "Now - with validation" and for example a field was deleted, the table remains unsynced, even if no data would be affected because that field is already empty and not necessary anymore.
Is there a kind of test whether data is affected or not? Of course importing a FOB is not a trial end error thing, but as written above, a warning in the appropriate case (and not always) would be nice, wouldnt it? Defacto it were a 4. option, Force - with warning in case of real data loss..
Any ideas? Maybe with PowerShell?
Thx in advance
Thomas
Before NAV 2015 it was possible to import a FOB file with potentially destroying data (delete, shorten, change data type of fields) IF (and only then) no data were affected. This means, deleting a field with no data in all companies of that given db was perfectly possible, and if data were affected, the FOB import was cancelled. So the import of the object was a perfect last test/validation, for example if a migration tool did forget to delete/move data.
As we know in NAV 2015 the synchronisation paradigma has changed.
Importing a FOB on customer side is now different, the user has to decide between 3 options. If the user choses the option "Now - with validation" and for example a field was deleted, the table remains unsynced, even if no data would be affected because that field is already empty and not necessary anymore.
Is there a kind of test whether data is affected or not? Of course importing a FOB is not a trial end error thing, but as written above, a warning in the appropriate case (and not always) would be nice, wouldnt it? Defacto it were a 4. option, Force - with warning in case of real data loss..
Any ideas? Maybe with PowerShell?
Thx in advance
Thomas
0
Comments
Any comments will be appreciated!
Regards
Thomas